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
This node interacts with the TeleFlow API to perform various operations on different resources, including reports. Specifically, for the "Report" resource and the "Get Many" operation, it retrieves multiple report records from the TeleFlow system. Users can specify filtering criteria by providing field-value pairs to narrow down the results.
This node is beneficial when you need to programmatically fetch bulk data about reports for analysis, monitoring, or integration with other systems. For example, you might use it to retrieve all reports matching certain criteria such as date ranges, status, or specific report types.
Properties
| Name | Meaning |
|---|---|
| Fields | A collection of field-value pairs used to filter the request. You can add multiple pairs to specify which fields and values to include in the query. |
The "Fields" property allows users to define one or more filters by specifying the field name and the corresponding value to refine the data fetched from the API.
Output
The output is an array of JSON objects representing the retrieved reports. Each object corresponds to a report record returned by the TeleFlow API based on the specified filters.
- The
jsonfield contains the full response data for each report. - There is no binary data output for this operation.
Dependencies
- Requires an API key credential for authenticating with the TeleFlow API.
- The base URL for the API must be configured in the node credentials.
- The node uses HTTP requests with JSON content type to communicate with the TeleFlow API.
Troubleshooting
- Missing ID error: Although not applicable for "Get Many," other operations require an ID parameter. Ensure IDs are provided where necessary.
- API authentication errors: Verify that the API key credential is correctly set up and has sufficient permissions.
- Invalid field names or values: If filters do not match expected API parameters, the request may return empty results or errors. Double-check field names and values.
- Network or connectivity issues: Ensure the base URL is reachable and there are no firewall restrictions blocking access.
Links and References
- TeleFlow API Documentation (replace with actual URL)
- n8n HTTP Request Node documentation for understanding request options: https://docs.n8n.io/nodes/n8n-nodes-base.httpRequest/