Actions82
- 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
Overview
This node interacts with the TeleFlow API to perform various operations on different resources. Specifically, for the LCR (Least Cost Routing) resource with the Get Many operation, it retrieves multiple LCR records from the TeleFlow system. This is useful when you want to fetch a list of LCR entries, optionally filtered by specific fields.
Common scenarios include:
- Retrieving all LCR configurations to analyze or audit routing rules.
- Filtering LCRs based on certain criteria such as name or other attributes.
- Integrating TeleFlow LCR data into workflows for reporting or further processing.
Example: You might use this node to get all LCR entries where the "name" field matches a particular pattern, then process those entries downstream in your workflow.
Properties
| Name | Meaning |
|---|---|
| Fields | A collection of field-value pairs used to filter the request. You can add multiple pairs to specify which LCR records to retrieve. For example, filtering by "name" or other LCR attributes. |
The "Fields" property allows specifying multiple filters, each consisting of:
- Name: The field name to filter by (e.g., "name").
- Value: The value to match for that field.
Output
The output is an array of JSON objects representing the retrieved LCR records. Each item corresponds to one LCR entry returned by the TeleFlow API.
- The
jsonfield contains the raw data of the LCR(s) fetched. - No binary data output is produced by this operation.
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 sends HTTP GET requests to the TeleFlow API endpoints corresponding to the LCR resource.
Troubleshooting
- Missing or invalid API credentials: Ensure the API key and base URL are correctly set in the node credentials.
- Empty or no results returned: Check the filter fields; incorrect or overly restrictive filters may return no data.
- Error messages about missing ID: Not applicable for "Get Many" but relevant for single record retrieval operations.
- HTTP errors: Network issues or incorrect API endpoint configuration can cause failures. Verify connectivity and API access permissions.
- If the node is set to continue on fail, errors will be returned in the output JSON under an
errorkey.
Links and References
- TeleFlow API Documentation (replace with actual URL)
- n8n documentation on HTTP Request Node for understanding underlying HTTP calls
- General info on Least Cost Routing concepts for telephony systems