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 files. Specifically, for the "File" resource and the "Get Many" operation, it retrieves multiple file records from the TeleFlow system. This operation supports filtering by specifying fields and their values to narrow down the query results.
This node is beneficial when you need to programmatically fetch lists of files stored or managed within TeleFlow, such as retrieving all files matching certain criteria for further processing, reporting, or integration workflows.
Example use case:
You want to get all files where the "type" field equals "pdf" or files created after a certain date. By specifying these fields in the input properties, you can retrieve only relevant files without fetching the entire dataset.
Properties
| Name | Meaning |
|---|---|
| Fields | A collection of field-value pairs used to filter the request. You can specify multiple fields to refine the query. For example, you might specify name = "report.pdf" or type = "pdf". |
The "Fields" property is a fixed collection allowing multiple entries, each with:
- Name: The name of the field to filter by (string).
- Value: The value to match for that field (string).
Output
The output is an array of JSON objects representing the files retrieved from the TeleFlow API. Each item corresponds to one file record and contains all data fields returned by the API for that file.
Since this operation fetches multiple files, the output JSON will be an array of file objects matching the specified filters.
No binary data output is indicated for 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 requests to communicate with the TeleFlow REST API endpoints.
Troubleshooting
- Missing or invalid API credentials: Ensure the API key and base URL are correctly set in the node credentials.
- Invalid field names or values: If the fields specified for filtering do not exist or have incorrect values, the API may return empty results or errors.
- Network issues: Connectivity problems to the TeleFlow API endpoint will cause request failures.
- Error messages about missing IDs: These apply to other operations like "get", "update", or "delete" but not "getAll". Make sure to provide required parameters for those operations if used.
- To handle errors gracefully, enable the "Continue On Fail" option in the node settings to allow workflow execution to proceed even if some requests fail.
Links and References
- TeleFlow API Documentation (replace with actual URL)
- n8n HTTP Request Node documentation for understanding underlying request mechanics: https://docs.n8n.io/nodes/n8n-nodes-base.httpRequest/