TeleFlowInstall

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 or value, then process that list downstream in your workflow.

Properties

The "Fields" property supports multiple entries, allowing complex filtering by combining several field-value conditions.

Output

The output is an array of JSON objects representing the retrieved LCR records. Each object corresponds to one LCR entry returned by the TeleFlow API.

• The structure of each JSON object depends on the TeleFlow API's LCR resource schema.
• No binary data is output by this operation.

Example output snippet (conceptual):

[
  {
    "id": "123",
    "name": "Primary LCR",
    "description": "Main routing configuration",
    ...
  },
  {
    "id": "456",
    "name": "Backup LCR",
    "description": "Secondary routing configuration",
    ...
  }
]

Dependencies

• Requires an active connection to the TeleFlow API.
• Needs an API authentication credential configured in n8n (an API key or token).
• The base URL for the TeleFlow API must be set in the credentials.
• The node sends HTTP GET requests to the /lcrs endpoint with optional query parameters derived from the "Fields" input.

Troubleshooting

• Missing or incorrect API credentials: Ensure the API key/token and base URL are correctly configured in the node credentials.
• Invalid field names in filters: If you specify field names that do not exist in the TeleFlow LCR resource, the API may return errors or empty results. Verify field names against TeleFlow API documentation.
• Empty results: If no LCR entries match the provided filters, the output will be an empty array.
• API connectivity issues: Network problems or incorrect base URL settings can cause request failures.
• Error messages: The node throws errors if the API returns an error response. Check the error message for details and verify the request parameters.

If the node is set to continue on fail, errors will be included in the output JSON under an error property instead of stopping execution.

Links and References

• TeleFlow API Documentation (replace with actual URL)
• n8n HTTP Request Node documentation: https://docs.n8n.io/nodes/n8n-nodes-base.httpRequest/
• General n8n credential setup guide: https://docs.n8n.io/credentials/overview/