TeleFlow icon

TeleFlow

Interact with TeleFlow API

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 as filters to specify which email templates to fetch. You can add multiple fields to refine the query. Each field consists of:
- Name: The name of the field to filter by (e.g., "name").
- Value: The value to match for that field.

Output

The output is an array of JSON objects representing the email templates retrieved from the TeleFlow API. Each object contains the properties of an email template as returned by the API, filtered according to the specified fields if any were provided.

No binary data output is produced by this operation.

Example output structure (simplified):

[
  {
    "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 that the API key and base URL are correctly set in the node's credentials.
  • Empty or no results returned: Verify that the field filters are correct and correspond to existing email template properties.
  • Error messages about missing ID: This does not apply to the "Get Many" operation but may appear if mistakenly using "get" or "update" operations without specifying an ID.
  • HTTP request failures: Check network connectivity and API endpoint availability.

Links and References

Discussion