Actions82
- Account Actions
- Account Audit Actions
- Billing Entry Actions
- Call Detail Record Actions
- Carrier Actions
- Device Actions
- Device Template Actions
- Email Template Actions
- Feature Code Actions
- File Actions
- Flow Actions
- Flow Template Actions
- LCR Actions
- Mobile SIM Actions
- Number Port Actions
- Phone Number Actions
- Provision Actions
Overview
This node interacts with the TeleFlow API to perform various operations on different resources, including Call Detail Records (CDRs). Specifically, the "Get Many" operation for the Call Detail Record resource retrieves multiple CDR entries from the TeleFlow system. This is useful for scenarios where you want to fetch call logs or records in bulk, possibly filtered by specific criteria.
Practical examples include:
- Retrieving all call detail records within a certain date range.
- Filtering call records by caller ID, destination number, or call status.
- Aggregating call data for reporting or analysis purposes.
Properties
| Name | Meaning |
|---|---|
| Fields | A collection of field-value pairs used to filter or specify which fields to include in the request. You can add multiple pairs to refine your query. For example, you might specify callerNumber as a field name and a phone number as its value to filter calls from that number. |
The "Fields" property supports multiple entries, each consisting of:
- Name: The field name to filter or include.
- Value: The corresponding value for that field.
Output
The output is an array of JSON objects representing the retrieved Call Detail Records matching the specified filters. Each object corresponds to a single call record with its associated data fields as returned by the TeleFlow API.
No binary data output is produced by this operation.
Dependencies
- Requires an API key credential for authenticating with the TeleFlow API.
- The base URL for the TeleFlow API must be configured in the node credentials.
- The node sends HTTP GET requests to the TeleFlow API endpoints.
Troubleshooting
- Missing or invalid API credentials: Ensure that the API key and base URL are correctly set in the node's credentials.
- Empty results: If no records are returned, verify that the filter fields are correct and match existing data.
- Invalid field names or values: Using unsupported or misspelled field names in the "Fields" property may cause the API to return errors or empty results.
- API errors: Network issues or API downtime can cause request failures. Check connectivity and TeleFlow service status.
- Error message "ID is required for get/update/delete operations": This does not apply to "Get Many" but indicates that other operations require an ID parameter.
Links and References
- TeleFlow API Documentation (Replace with actual URL)
- n8n HTTP Request Node documentation for understanding how HTTP requests are made within n8n workflows.