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
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 specific fields of an LCR record.
This node is beneficial in scenarios where you need to automate management of telephony configurations, such as updating routing rules or cost parameters dynamically based on external data or workflows. For example, a telecom operator could use this node to programmatically update LCR entries when new pricing information becomes available.
Properties
| Name | Meaning |
|---|---|
| ID | The unique identifier of the LCR resource to update. Required to specify which record to modify. |
| Fields | A collection of field-value pairs representing the properties of the LCR to update. You can add multiple fields, each with a name and corresponding value, to specify exactly what should be changed in the LCR record. |
Output
- The output is an array of JSON objects, each representing the response from the TeleFlow API after attempting to update an LCR record.
- Each JSON object contains the updated LCR resource data as returned by the API.
- 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 API must be configured 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 update operation, the node will throw 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 carefully.
- Field Validation: The API might reject updates if field values are invalid or missing required fields. Verify the correctness of all field names and values before sending the request.
- Continue On Fail: If enabled, the node will continue processing subsequent items even if one update fails, returning error details in the output JSON.
Links and References
- TeleFlow API Documentation (Replace with actual URL)
- n8n Documentation on Creating Custom Nodes