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 Tariffs. Specifically, the "Get Many" operation for the Tariff resource retrieves multiple tariff 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 tariffs available in the TeleFlow system for reporting or synchronization.
- Retrieving tariffs that match specific criteria by specifying field-value filters.
- Integrating tariff data into workflows for billing, provisioning, or analytics.
For example, a user might want to get all tariffs with a certain name or attribute by adding corresponding field filters, then use the retrieved data downstream in their automation.
Properties
| Name | Meaning |
|---|---|
| Fields | A collection of field-value pairs used as filters to refine the query when retrieving tariffs. Each pair consists of: - Name: The field name to filter by (string). - Value: The value to match for that field (string). Multiple such pairs can be added to build more specific queries. |
Output
The output is an array of JSON objects representing the tariffs retrieved from the TeleFlow API. Each object corresponds to a tariff record and contains its properties as returned by the API.
No binary data output is produced by this operation.
Example output structure (simplified):
[
{
"id": "123",
"name": "Standard Tariff",
"description": "Basic tariff plan",
"rate": "0.05",
...
},
{
"id": "124",
"name": "Premium Tariff",
"description": "Premium tariff plan",
"rate": "0.10",
...
}
]
Dependencies
- Requires an API key credential for authenticating with the TeleFlow API.
- The base URL for the TeleFlow API must be configured in the node credentials.
- The node uses HTTP requests to communicate with the TeleFlow REST API endpoints.
Troubleshooting
- Missing ID for Get/Update/Delete operations: If you attempt to perform operations that require an ID without providing one, the node will throw an error stating "ID is required for get operation" (or update/delete accordingly). Ensure the ID parameter is set.
- Invalid field names or values: When specifying fields for filtering, using incorrect field names or unsupported values may result in empty responses or API errors. Verify field names against TeleFlow API documentation.
- API authentication errors: If the API key or base URL is misconfigured, the node will fail to connect. Check credentials and network connectivity.
- Continue On Fail behavior: If enabled, the node will continue processing subsequent items even if some fail, returning error messages in the output JSON under an
errorproperty.
Links and References
- TeleFlow API Documentation (replace with actual URL)
- n8n HTTP Request Node documentation: https://docs.n8n.io/nodes/n8n-nodes-base.httpRequest/
- n8n Custom Node Development Guide: https://docs.n8n.io/integrations/creating-nodes/