TeleFlow icon

TeleFlow

Interact with TeleFlow API
Join our community

Actions145

Overview

The node interacts with the TeleFlow API to perform various operations on multiple resources, including "Voice". Specifically, for the Voice - Get operation, it retrieves detailed information about a single Voice resource identified by its unique ID. This is useful when you need to fetch specific voice-related data from TeleFlow, such as call recordings, voice configurations, or metadata associated with a particular voice entity.

Practical examples:

  • Fetching details of a recorded voice call by its ID.
  • Retrieving configuration or status information of a voice resource.
  • Using the retrieved data to trigger further workflows or analytics based on voice resource attributes.

Properties

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

Output

The output is an array of JSON objects where each object corresponds to the retrieved Voice resource data. The structure of the JSON depends on the TeleFlow API response for the Voice resource but generally includes all requested fields and their values.

Example output snippet (conceptual):

{
  "id": "voice123",
  "name": "Sample Voice Resource",
  "status": "active",
  "createdAt": "2024-01-01T12:00:00Z",
  ...
}

No binary data output is indicated for this operation.

Dependencies

  • Requires an API authentication token credential configured in n8n to access the TeleFlow API.
  • The base URL for the TeleFlow API must be set in the node credentials.
  • The node uses HTTP requests to communicate with the TeleFlow REST API endpoints.

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 the ID input is correctly set.
  • API connection issues: Errors related to network connectivity or invalid credentials may occur. Verify the API key/token and base URL are correct and have sufficient permissions.
  • 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.
  • Continue on Fail: If enabled, the node will continue processing subsequent items even if one fails, returning error details in the output JSON.

Links and References

Discussion