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
This node integrates with the TeleFlow API to perform various operations on different resources, including files. Specifically, for the File resource and the Update operation, it allows updating an existing file's metadata or attributes by specifying its unique ID and the fields to update.
Common scenarios where this node is beneficial include:
- Automating updates to file records in TeleFlow without manual intervention.
- Integrating file metadata updates into larger workflows, such as after processing or validation steps.
- Keeping file information synchronized between TeleFlow and other systems.
For example, you might use this node to update the name or other attributes of a file record identified by its ID after renaming or categorizing it in your workflow.
Properties
| Name | Meaning |
|---|---|
| ID | The unique identifier of the file resource to update. Required to specify which file to update. |
| Fields | A collection of field-value pairs representing the specific attributes of the file to update. You can add multiple fields, each with a name and corresponding value. |
Note: The "Fields" property allows flexible specification of any number of fields to update on the file resource.
Output
The node outputs an array of JSON objects, each representing the response from the TeleFlow API for the update request. The JSON structure corresponds to the updated file resource data returned by the API, typically including the updated fields and metadata.
If the update is successful, the output JSON will contain the current state of the file resource after modification.
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 node uses HTTP requests to communicate with the TeleFlow API endpoint specified in the credentials.
- Proper API base URL and authentication must be set up in the node credentials for successful operation.
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 you provide a valid file ID.
- API Request Failures: Network issues, invalid credentials, or incorrect API URLs can cause HTTP request failures. Verify your API key and base URL configuration.
- Field Validation Errors: Providing invalid or unsupported field names/values may result in API errors. Confirm the fields you want to update are valid for the File resource in TeleFlow.
- 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 Documentation on HTTP Request Node
- General n8n Node Development Guide