TeleFlow icon

TeleFlow

Interact with TeleFlow API
Join our community

Actions145

Overview

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

Practical examples include:

  • Retrieving call logs for auditing or billing purposes.
  • Fetching detailed call data to analyze call quality or usage patterns.
  • Integrating call detail data into CRM or reporting systems.

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 output is a JSON object representing the retrieved Call Detail Record. It contains all the properties returned by the TeleFlow API for that specific call record, which may include call metadata such as timestamps, caller/callee info, duration, status, and other relevant details.

No binary data output is produced by this operation.

Example output structure (simplified):

{
  "id": "12345",
  "caller": "+1234567890",
  "callee": "+0987654321",
  "startTime": "2024-01-01T12:00:00Z",
  "duration": 300,
  "status": "completed",
  ...
}

Dependencies

  • Requires an active connection to the TeleFlow API.
  • Needs an API authentication credential configured in n8n (an API key or token).
  • The base URL for the TeleFlow API must be set in the node credentials.

Troubleshooting

  • Missing ID error: If the "ID" property is not provided for the Get operation, the node will throw an error stating that the ID is required. Ensure you provide a valid Call Detail 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 incorrect or unsupported field names in the "Fields" property may result in incomplete or empty responses. Double-check field names against TeleFlow API documentation.
  • Handling errors gracefully: If "Continue On Fail" is enabled, the node will output error messages in the JSON under an error key instead of stopping execution.

Links and References

Discussion