TeleFlow icon

TeleFlow

Interact with TeleFlow API

Actions82

Overview

This node interacts with the TeleFlow API to perform various operations on different resources, including Email Templates. Specifically, the "Get Many" operation for the Email Template resource retrieves multiple email templates from the TeleFlow system based on optional filtering criteria.

Common scenarios where this node is beneficial include:

  • Fetching a list of email templates to display or process in bulk.
  • Filtering email templates by specific fields to narrow down results.
  • Integrating TeleFlow email template data into workflows for automation or reporting.

For example, you might use this node to retrieve all email templates that match certain names or other attributes, then use the data downstream to send customized emails or audit template usage.

Properties

Name Meaning
Fields A collection of field-value pairs used to filter the request. You can specify multiple fields to refine the query. For each field, provide:
- Name: The field name to filter by (string).
- Value: The value to match for that field (string).

Output

The output is an array of JSON objects representing the retrieved email templates. Each object contains the properties of an email template as returned by the TeleFlow API. The exact structure depends on the API response but typically includes identifiers and template details.

No binary data is output by this operation.

Example output snippet (conceptual):

[
  {
    "id": "template1",
    "name": "Welcome Email",
    "subject": "Welcome to Our Service",
    "body": "<html>...</html>",
    ...
  },
  {
    "id": "template2",
    "name": "Password Reset",
    "subject": "Reset Your Password",
    "body": "<html>...</html>",
    ...
  }
]

Dependencies

  • Requires an API key credential for authenticating with the TeleFlow API.
  • The base URL for the TeleFlow API must be configured in the node credentials.
  • The node uses HTTP requests to communicate with the TeleFlow REST API endpoints.

Troubleshooting

  • Missing or invalid API credentials: Ensure the API key and base URL are correctly set in the node credentials.
  • Invalid field names or values: If filtering fields do not match the API's expected parameters, the request may return no results or errors.
  • ID required errors: Although not applicable for "Get Many," other operations require an ID parameter; ensure it is provided when needed.
  • API connectivity issues: Network problems or incorrect base URLs will cause HTTP request failures.
  • Error handling: If an error occurs during execution, the node logs the error message. If "Continue On Fail" is enabled, the node outputs the error message in the JSON output instead of stopping the workflow.

Links and References

Discussion