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 CRUD (Create, Read, Update, Delete) operations on various resources. Specifically for the File resource and the Update operation, it updates an existing file record identified by its unique ID with new field values provided by the user.
This node is beneficial in scenarios where you need to programmatically update metadata or attributes of files stored or managed within the TeleFlow system. For example, updating a file's name or other custom fields without manual intervention.
Practical example: You have a workflow that processes incoming data and based on certain conditions, updates the properties of a file in TeleFlow to reflect new status or categorization.
Properties
| Name | Meaning |
|---|---|
| ID | The unique identifier of the file resource to update. This is required to specify which file to modify. |
| Fields | A collection of field-value pairs representing the properties to update on the file. Each pair consists of: - Name: The field name to update. - Value: The new value for that field. |
Output
- The output is a JSON object representing the updated file resource as returned by the TeleFlow API.
- The structure of this JSON depends on the API response but typically includes the updated fields and their new values.
- No binary data output is indicated for this operation.
Dependencies
- Requires an active connection to the TeleFlow API via an API key credential configured in n8n.
- The base URL for the API is taken from the credential configuration.
- The node uses HTTP methods (PUT) to communicate with the TeleFlow REST endpoints.
Troubleshooting
- Missing ID Error: If the "ID" property is not provided, the node will throw an error stating that the ID is required for the update operation. Ensure the ID is correctly set.
- API Request Failures: Network issues, invalid credentials, or incorrect field names can cause the API request to fail. Check the API key validity, network connectivity, and field names.
- Field Validation: Providing invalid or unsupported field names/values may result in API errors. Verify the fields against TeleFlow API documentation.
- Continue On Fail: If enabled, the node will continue processing subsequent items even if one fails, returning error details in the output JSON.
Links and References
- TeleFlow API Documentation (Replace with actual URL)
- n8n HTTP Request Node Documentation
- n8n Custom Node Development Guide