Actions145
- User Actions
- Voice Actions
- File Actions
- Flow Actions
- Reseller Actions
- SIP Trunk Actions
- Transcription Actions
- Voice Mail Message Actions
- 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
- Flow Template Actions
- LCR Actions
- Mobile SIM Actions
- Number Port Actions
- Phone Number Actions
- Provision Actions
- Report Actions
- Tariff Actions
- Tariff Code Actions
- Tariff Profile Actions
- Tenant Actions
- Tenant Audit Actions
Overview
This node interacts with the TeleFlow API to perform various operations on different resources, including reports. Specifically, the "Get Many" operation for the "Report" resource retrieves multiple report records from the TeleFlow system. It allows users to specify filtering fields to narrow down the results.
Common scenarios where this node is beneficial include:
- Fetching a list of reports based on specific criteria such as date ranges, report types, or statuses.
- Automating report retrieval for further processing or analysis within an n8n workflow.
- Integrating TeleFlow reporting data into other systems or dashboards.
For example, a user might want to retrieve all reports generated in the last month that match certain parameters by specifying those as fields in the request.
Properties
| Name | Meaning |
|---|---|
| Fields | A collection of field-value pairs used to filter the reports returned by the API request. You can add multiple fields to refine your query. Each field consists of: - 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 reports retrieved from the TeleFlow API. Each object corresponds to a single report and contains the properties as returned by the API, which may include report metadata and content depending on the API's response structure.
No binary data output is produced by 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 configuration of the base URL and authentication token is necessary for successful API calls.
Troubleshooting
- Missing ID error: Although not applicable for "Get Many," other operations require an ID parameter. Ensure IDs are provided when needed.
- API request failures: Errors may occur due to invalid credentials, network issues, or incorrect field filters. Verify API keys and network connectivity.
- Empty results: If no reports are returned, check that the field filters are correct and that matching reports exist.
- Continue on Fail: If enabled, errors will be captured in the output JSON under an
errorproperty instead of stopping execution.
Links and References
- TeleFlow API Documentation (Replace with actual URL)
- n8n HTTP Request Node Documentation
- n8n Custom Node Development Guide