TeleFlow icon

TeleFlow

Interact with TeleFlow API

Actions82

Overview

This node interacts with the TeleFlow API to perform various operations on different resources, including Call Detail Records (CDRs). Specifically, for the Call Detail Record - Get operation, it retrieves detailed information about a single call record by its unique identifier. This is useful in scenarios where you need to fetch call metadata such as duration, participants, timestamps, and other call-related details for auditing, reporting, or troubleshooting telephony systems.

Practical examples include:

  • Fetching a specific call's details after receiving a call ID from another system.
  • Integrating call data into CRM or analytics platforms.
  • Automating workflows that require validation or processing of individual call records.

Properties

Name Meaning
ID The unique identifier of the Call Detail Record to retrieve. This is required.
Fields Optional key-value pairs specifying additional fields to include in the request query string. You can add multiple field name and value pairs to filter or customize the returned data.

Output

The node outputs an array with one item per input. Each item's json property contains the retrieved Call Detail Record object as returned by the TeleFlow API. The structure of this JSON depends on the API response but typically includes call metadata such as:

  • Call identifiers
  • Timestamps (start, end)
  • Caller and callee information
  • Call duration
  • Status and disposition
  • Other custom or extended call attributes

No binary data output is produced by this operation.

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 node credentials.
  • The node uses HTTP requests with JSON content type and expects JSON responses.

Troubleshooting

  • Missing ID error: If the "ID" property is not provided, the node throws an error stating that the ID is required. Ensure you supply a valid call record ID.
  • API connectivity issues: Network errors or invalid credentials will cause HTTP request failures. Verify your API key and base URL configuration.
  • Invalid field names: Providing unsupported or incorrect field names in the "Fields" collection may result in incomplete or empty responses.
  • Handling errors gracefully: If "Continue On Fail" is enabled, errors will be returned as JSON objects with an error property instead of stopping execution.

Links and References

Discussion