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 provides integration with the TeleFlow API, allowing users to perform various operations on multiple resource types managed by TeleFlow. Specifically for the File resource and the Delete operation, this node enables users to delete a file identified by its unique ID from the TeleFlow system.
This is useful in scenarios where files need to be programmatically removed as part of an automated workflow, such as cleaning up outdated or unnecessary files, managing storage, or enforcing retention policies.
Example use case:
A workflow that processes files and then deletes them once processing is complete to free up space or maintain compliance.
Properties
| Name | Meaning |
|---|---|
| ID | The unique identifier of the file resource to delete. This is required to specify which file to remove. |
| Fields | Optional key-value pairs to include additional fields in the request (not typically used for delete). |
Output
- The output JSON contains the response from the TeleFlow API after attempting to delete the specified file.
- Typically, this will be a confirmation object indicating success or details about the deletion.
- No binary data output is produced by this operation.
Dependencies
- Requires an API authentication credential configured in n8n to connect to the TeleFlow API.
- The base URL for the TeleFlow API must be set in the credentials.
- The node uses HTTP requests 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 delete operation. Ensure the ID is correctly set.
- API errors: Errors returned from the TeleFlow API (e.g., file not found, permission denied) will be surfaced. Check the API response message for details.
- Network issues: Connectivity problems or incorrect base URL configuration can cause failures. Verify network access and credential settings.
- 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 Credential Configuration