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 "Tariff Profile". Specifically, the "Get Many" operation for the "Tariff Profile" resource retrieves multiple tariff profiles 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 tariff profiles to display or process in workflows.
- Filtering tariff profiles based on specific criteria such as name or other attributes.
- Integrating TeleFlow tariff data into other systems or automations.
For example, a user might want to retrieve all tariff profiles that match certain field values to update pricing rules or generate reports.
Properties
| Name | Meaning |
|---|---|
| Fields | A collection of field-value pairs used to filter the request. Each pair specifies a field name and its corresponding value to include in the query parameters. |
The "Fields" property supports multiple entries, allowing users to add several filters to refine the query.
Output
The output is an array of JSON objects representing the retrieved tariff profiles matching the specified filters. Each item corresponds to one tariff profile as returned by the TeleFlow API.
The structure of each JSON object depends on the API response but generally includes details about the tariff profiles.
No binary data output is produced by this operation.
Dependencies
- Requires an API key credential for authenticating with the TeleFlow API.
- The node expects the base URL of the TeleFlow API to be configured in the credentials.
- Network access to the TeleFlow API endpoint is necessary.
Troubleshooting
- Missing or invalid API credentials: Ensure that the API key and base URL are correctly set up in the node's credentials.
- Invalid field names or values: If the API returns errors related to query parameters, verify that the field names and values used in the "Fields" property are valid according to the TeleFlow API documentation.
- Empty or no results: This may occur if the filters do not match any tariff profiles. Try broadening or removing filters.
- ID required errors: Not applicable for "Get Many" operation, but other operations require an ID parameter; ensure it is provided when needed.
- HTTP request failures: Check network connectivity and API availability.
If the node encounters an error during execution and "Continue On Fail" is enabled, it will output an error message in the JSON output instead of stopping the workflow.
Links and References
- TeleFlow API Documentation (Replace with actual URL)
- n8n Documentation on Creating Custom Nodes
- General info on REST API Query Parameters