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 integrates with the TeleFlow API to perform various operations on multiple resources, including reports. Specifically, for the "Report" resource and the "Get" operation, it retrieves a single report by its unique ID. Users can specify additional query fields to filter or customize the data returned.
Common scenarios include:
- Fetching detailed information about a specific report in TeleFlow by its ID.
- Retrieving customized report data by specifying particular fields to include in the response.
Practical example:
- A user wants to get a report with ID "12345" and only retrieve certain fields such as "status" or "createdDate" to process or display in their workflow.
Properties
| Name | Meaning |
|---|---|
| ID | The unique identifier of the report to retrieve. This is required for the Get operation. |
| Fields | Optional key-value pairs specifying additional fields to include in the request query. Each pair consists of a field name and its corresponding value. |
Output
The node outputs an array of items where each item contains a json object representing the retrieved report data from the TeleFlow API. The structure of this JSON depends on the API response but generally includes all requested report details.
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 API must be set in the credentials.
- The node uses HTTP requests to interact with the TeleFlow REST API endpoints.
Troubleshooting
- Missing ID error: If the "ID" property is not provided for the Get operation, the node will throw an error stating that the ID is required. Ensure you provide a valid report ID.
- API connection issues: Errors related to network connectivity or invalid credentials may occur. Verify that the API key/token and base URL are correctly configured.
- Invalid field names: Specifying incorrect or unsupported field names in the "Fields" property may result in incomplete or empty responses. Confirm field names against the TeleFlow API documentation.
Links and References
- TeleFlow API Documentation (Replace with actual URL if available)
- n8n HTTP Request Node documentation for understanding how HTTP calls are made within n8n workflows.