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, 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 programmatically modify flow templates in TeleFlow, such as updating workflow definitions or configurations without manual intervention.
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. Required to specify which template to modify. |
| Fields | A collection of field-value pairs representing the properties to update on the flow template. You can add multiple fields, each with a name and corresponding value. |
Output
The node outputs an array of JSON objects, each representing the response from the TeleFlow API for the update request. The json output contains the updated flow template data as returned by the API, reflecting the new state after the update.
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 throws an error stating that the ID is required for the update operation. Ensure the ID of the flow template to update is correctly set.
- API Request Failures: Network issues, invalid credentials, or incorrect field names/values may cause the API request to fail. Check the API key validity, endpoint URL, and field correctness.
- 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 HTTP Request Node documentation for understanding API calls: https://docs.n8n.io/nodes/n8n-nodes-base.httpRequest/