TeleFlow icon

TeleFlow

Interact with TeleFlow API

Overview

This node integrates with the TeleFlow API to perform various operations on different resources, including phone numbers. Specifically, for the Phone Number - Get operation, it retrieves detailed information about a single phone number resource by its unique identifier. This is useful when you need to fetch specific phone number details such as its number, type, or any other associated metadata stored in TeleFlow.

Practical examples include:

  • Retrieving phone number details to display in a dashboard.
  • Fetching phone number info before performing updates or validations.
  • Integrating phone number data into workflows that require up-to-date contact information.

Properties

Name Meaning
ID The unique identifier of the phone number resource to retrieve. This is required.
Fields Optional key-value pairs specifying additional fields to include in the request query. Each pair consists of a field name and its corresponding value to filter or specify the request further.

Output

The output is a JSON object representing the phone number resource retrieved from the TeleFlow API. It contains all the properties of the phone number as returned by the API, which typically includes identifiers, number string, type, and potentially other metadata depending on the API's response.

No binary data output is produced by this operation.

Example output structure (simplified):

{
  "id": "string",
  "number": "string",
  "type": "string",
  "...": "other phone number related fields"
}

Dependencies

  • Requires an active connection to the TeleFlow API via an API key credential configured in n8n.
  • The base URL for the API must be set in the credentials.
  • The node uses HTTP requests with JSON content-type headers to communicate with the TeleFlow API.

Troubleshooting

  • Missing ID error: If the "ID" property is not provided, the node will throw an error stating that the ID is required for the get operation. Ensure the ID is correctly set.
  • API connectivity issues: Errors may occur if the API base URL or authentication credentials are incorrect or missing. Verify the API key and base URL configuration.
  • Field filtering errors: Incorrect field names or values in the "Fields" property might cause the API to return errors or empty results. Double-check field names against the TeleFlow API documentation.
  • Continue on Fail: If enabled, the node will continue processing subsequent items even if one fails, returning error messages in the output JSON.

Links and References

Discussion