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 "TeleFlow" allows interaction with the TeleFlow API to manage various telephony-related resources. Specifically, for the Flow resource and the Update operation, this node updates an existing Flow entity by its unique ID with new field values.
This node is beneficial in scenarios where you need to programmatically modify telephony flows, such as updating call routing logic or flow metadata without manual intervention. For example, you might update a flow's name or configuration fields dynamically based on external triggers or workflows.
Properties
| Name | Meaning |
|---|---|
| ID | The unique identifier of the Flow resource to update. This is required. |
| Fields | A collection of field-value pairs specifying which properties of the Flow to update. Each pair includes: - Name: The field name to update. - Value: The new value for that field. |
Output
- The output JSON contains the updated Flow object returned from the TeleFlow API after the update operation.
- The structure of the JSON corresponds to the Flow resource schema as defined 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 API must be configured in the node credentials.
- The node uses HTTP requests (POST, GET, PUT, DELETE) to interact 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 "ID is required for update operation". Ensure the ID is set correctly.
- API request failures: Network issues, invalid credentials, or incorrect field names can cause HTTP errors. Verify API credentials and field names.
- Field validation errors: The API may reject updates if field values are invalid or missing required fields. Check the API documentation for valid field names and formats.
- To continue processing other items even if one fails, enable the "Continue On Fail" option in the node settings.
Links and References
- TeleFlow API Documentation (replace with actual URL)
- n8n HTTP Request Node documentation: https://docs.n8n.io/nodes/n8n-nodes-base.httpRequest/