TeleFlow icon

TeleFlow

Interact with TeleFlow API

Actions82

Overview

This node integrates with the TeleFlow API to perform various operations on different resources, including Call Detail Records (CDRs). Specifically, for the Call Detail Record resource and the Create operation, the node allows users to create new call detail records by sending specified fields to the TeleFlow system.

Typical use cases include:

  • Automatically logging call details into TeleFlow from other systems.
  • Creating custom call records based on external data inputs.
  • Integrating call data creation as part of a larger workflow automation.

For example, you might use this node to create a new call record with specific attributes such as caller ID, call duration, or call status, which can then be used for billing, reporting, or analytics within TeleFlow.

Properties

Name Meaning
Fields A collection of field-value pairs to include in the request. Add multiple fields to specify detailed attributes of the call detail record being created. Each field consists of:
- Name: The name of the field to set.
- Value: The value to assign to that field.

Output

The node outputs an array of JSON objects, each representing the response from the TeleFlow API after creating a call detail record. The structure of the JSON output corresponds directly to the API's response for the created record, typically including identifiers, timestamps, and any other relevant metadata returned by TeleFlow.

No binary data output is produced by this node.

Dependencies

  • Requires an active connection to the TeleFlow API.
  • Needs an API authentication token or key configured in n8n credentials to authorize requests.
  • The base URL for the TeleFlow API must be set in the credentials configuration.

Troubleshooting

  • Missing Required Fields: If required fields for creating a call detail record are not provided, the API may return errors. Ensure all mandatory fields expected by TeleFlow are included in the "Fields" property.
  • Authentication Errors: If the API key or token is invalid or missing, requests will fail. Verify that the credential is correctly configured and has sufficient permissions.
  • Invalid Field Names or Values: Providing incorrect field names or incompatible values may cause the API to reject the request. Double-check field names against TeleFlow API documentation.
  • Network Issues: Connectivity problems between n8n and TeleFlow API endpoints can cause timeouts or failures. Confirm network access and correct base URL settings.
  • Error Messages: The node throws errors with messages from the TeleFlow API. When using "Continue On Fail," errors are returned in the output JSON under an error key for easier handling.

Links and References

Discussion