Actions145
- User Actions
- Voice Actions
- File Actions
- Flow Actions
- Reseller Actions
- SIP Trunk Actions
- Transcription Actions
- Voice Mail Message Actions
- 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
- Flow Template Actions
- LCR Actions
- Mobile SIM Actions
- Number Port Actions
- Phone Number Actions
- Provision Actions
- Report Actions
- Tariff Actions
- Tariff Code Actions
- Tariff Profile Actions
- Tenant Actions
- Tenant Audit Actions
Overview
The node interacts with the TeleFlow API to perform various operations on different resources. Specifically, for the Call Detail Record resource and the Update operation, it updates an existing call detail record by its unique ID. This is useful in scenarios where you need to modify details of a call record after it has been created, such as correcting metadata or adding additional information.
Practical examples include:
- Updating call duration or status after call processing.
- Correcting caller or callee information.
- Adding tags or notes to a call record for reporting purposes.
Properties
| Name | Meaning |
|---|---|
| ID | The unique identifier of the Call Detail Record to update. This is required. |
| Fields | A collection of field-value pairs specifying which fields of the Call Detail Record to update and their new values. You can add multiple fields to update simultaneously. |
Note: The "Fields" property allows flexible specification of any number of fields to be updated by providing their names and corresponding new values.
Output
The output is an array of JSON objects, each representing the response from the TeleFlow API after updating a Call Detail Record. The structure of the JSON corresponds to the updated Call Detail Record data returned by the 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 methods (PUT) to communicate with the TeleFlow REST API endpoints.
Troubleshooting
- Missing ID Error: If the "ID" property is not provided, the node will throw an error stating that the ID is required for the update operation. Ensure the ID of the Call Detail Record to update is specified.
- API Request Failures: Network issues, invalid credentials, or incorrect field names may cause the API request to fail. Check your API key validity, network connectivity, and ensure the field names match those accepted by the TeleFlow API.
- Partial Updates: If some fields are not updated as expected, verify that the field names and values are correctly set in the "Fields" property.
- Continue On Fail: If enabled, the node will continue processing subsequent items even if one update fails, returning the error message in the output JSON for the failed item.
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/