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, including Flow Templates. Specifically, for the Flow Template - Update operation, it updates an existing flow template by its unique ID with specified fields. This is useful in scenarios where you need to modify or correct details of a flow template programmatically within an automation workflow.
Practical examples include:
- Updating the name or configuration of a flow template after changes in business logic.
- Automating bulk updates to multiple flow templates based on external triggers or data sources.
Properties
| Name | Meaning |
|---|---|
| ID | The unique identifier of the flow template to update. This is required to specify which template to modify. |
| Fields | A collection of field-value pairs representing the properties of the flow template to update. You can add multiple fields to update specific attributes of the flow template. |
The "Fields" property allows flexible specification of any number of fields to be updated by providing their names and new values.
Output
The output is an array of JSON objects, each representing the response from the TeleFlow API for the update request. The JSON structure corresponds directly to the updated flow template object returned by the API, containing all relevant properties after the update.
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 will throw an error stating that the ID is required. Ensure the ID of the flow template to update is correctly set.
- API errors: Errors returned from the TeleFlow API (e.g., invalid field names, unauthorized access) will be logged and can cause the node to fail unless "Continue On Fail" is enabled.
- Field validation: Incorrect or unsupported field names in the "Fields" collection may result in API errors. Verify field names against the TeleFlow API documentation.
- Network issues: Connectivity problems or incorrect base URL settings can cause request failures.
Links and References
- TeleFlow API Documentation (Replace with actual URL if available)
- n8n HTTP Request Node documentation: https://docs.n8n.io/nodes/n8n-nodes-base.httpRequest/