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 multiple resource types, including files. Specifically, for the File - Get operation, it retrieves detailed information about a specific file resource by its unique identifier. This is useful when you need to fetch metadata or details of a particular file stored or managed within the TeleFlow system.
Common scenarios include:
- Retrieving file details before processing or transferring.
- Verifying file existence and attributes in workflows.
- Fetching additional fields or metadata associated with a file.
Example: You have a workflow that processes call recordings stored as files in TeleFlow. Before downloading or analyzing a recording, you use this node to get the file's metadata such as name, size, or custom fields.
Properties
| Name | Meaning |
|---|---|
| ID | The unique identifier of the file resource to retrieve. Required for the Get operation. |
| Fields | Optional key-value pairs specifying additional fields to include in the request query. |
The Fields property allows adding multiple field filters or parameters to customize the data returned by the API. For example, you might specify "status": "active" or other relevant query parameters supported by the TeleFlow API.
Output
The node outputs an array of JSON objects, each representing the retrieved file resource data from the TeleFlow API. The structure corresponds directly to the API response for the file resource, typically including properties like:
- File ID
- File name
- Metadata fields (depending on what the API returns)
- Any additional requested fields specified via the Fields property
If the API supports binary data for files, this node does not explicitly handle binary output in the provided code; it only returns JSON metadata.
Dependencies
- Requires an API authentication credential configured in n8n to connect to the TeleFlow API.
- The base URL for the API is taken from the credential configuration.
- The node uses HTTP requests with JSON content type headers.
Troubleshooting
- Missing ID error: If the ID property is empty or missing for the Get operation, the node will throw an error stating "ID is required for get operation." Ensure you provide a valid file ID.
- API connection issues: Errors related to network connectivity or invalid credentials will cause the node to fail. Verify your API key and base URL settings.
- Invalid field parameters: Providing unsupported or incorrect field names in the Fields property may result in API errors or incomplete data. Check the TeleFlow API documentation for valid query parameters.
- Continue on Fail: If enabled, the node will continue processing subsequent items even if one fails, returning error messages in the output JSON.
Links and References
- TeleFlow API Documentation (Replace with actual URL)
- n8n HTTP Request Node Documentation
- n8n Custom Node Development Guide