Actions145
- 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
- Report Actions
- Reseller Actions
- SIP Trunk Actions
- Tariff Actions
- Tariff Code Actions
- Tariff Profile Actions
- Tenant Actions
- Tenant Audit Actions
- Transcription Actions
- User Actions
- Voice Actions
- Voice Mail Message 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. Each pair consists of: - Name: The field name to filter by. - Value: The value to match 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 properties 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 uses HTTP requests to communicate with the TeleFlow REST API endpoints.
Troubleshooting
- Missing or invalid API credentials: Ensure that the API key and base URL are correctly set in the node's credentials.
- Invalid field names or values: If filtering fields do not match the API's expected parameters, the request may return no results or errors.
- Network issues or API downtime: HTTP request failures may occur if the TeleFlow service is unreachable.
- Error messages about missing IDs: These apply to other operations but not "Get Many". For "Get Many", ensure filters are correctly formatted.
If the node throws an error, check the error message logged and verify the input parameters and credentials.
Links and References
- TeleFlow API Documentation (Replace with actual URL)
- n8n HTTP Request Node documentation for understanding API calls: https://docs.n8n.io/nodes/n8n-nodes-base.httpRequest/