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
The node interacts with the TeleFlow API to perform various operations on different resources. Specifically, for the LCR (Least Cost Routing) resource, it supports updating an existing LCR entry by its unique ID. This update operation allows users to modify fields of an LCR record in TeleFlow.
This node is beneficial when automating telephony infrastructure management, such as dynamically updating routing rules or cost parameters in a telephony system without manual intervention. For example, a user might update an LCR entry to change routing preferences based on new carrier rates or network conditions.
Properties
| Name | Meaning |
|---|---|
| ID | The unique identifier of the LCR resource to update. Required to specify which LCR to modify. |
| Fields | A collection of field-value pairs representing the properties to update on the LCR. Users can add multiple fields to customize the update request. |
The "Fields" property allows specifying any number of fields by name and their corresponding new values to be sent in the update request.
Output
The node outputs an array of JSON objects, each representing the response from the TeleFlow API after attempting to update an LCR resource. The JSON structure corresponds directly to the updated LCR object returned by the API.
If the update is successful, the output JSON contains the updated LCR details. If an error occurs and the node is configured to continue on failure, the output JSON will contain an error field with the error message.
No binary data output is produced by this node.
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 for the update operation, the node throws an error stating that the ID is required. Ensure you provide a valid LCR ID.
- API Request Failures: Network issues, invalid credentials, or incorrect field names may cause the API request to fail. Check your API key, base URL, and field names.
- Continue On Fail Behavior: If enabled, errors during execution will be captured in the output JSON instead of stopping the workflow. This helps in debugging but may require additional handling downstream.
Links and References
- TeleFlow API Documentation (Replace with actual URL if available)
- n8n Documentation on HTTP Request Node (for understanding underlying HTTP calls)
- General information on Least Cost Routing concepts: Wikipedia - Least Cost Routing