TeleFlow icon

TeleFlow

Interact with TeleFlow API

Overview

This node interacts with the TeleFlow API to perform various operations on different resources, including tariffs. Specifically, the "Get" operation for the "Tariff" resource retrieves detailed information about a single tariff by its unique identifier. This is useful when you need to fetch specific tariff details such as pricing or configuration from TeleFlow within an automated workflow.

Practical examples include:

  • Retrieving tariff details to display or process in billing workflows.
  • Fetching tariff information before updating or validating related data.
  • Integrating tariff data into reporting or analytics pipelines.

Properties

Name Meaning
ID The unique identifier of the tariff resource to retrieve. This is required.
Fields Optional key-value pairs specifying additional fields to include in the request query. You can add multiple fields, each with a name and value, to filter or customize the returned data.

Output

The node outputs JSON data representing the tariff object retrieved from the TeleFlow API. The structure corresponds directly to the API response for a tariff resource, containing all relevant tariff details.

If the API supports binary data for tariffs (not indicated here), it would be included in the binary output field; otherwise, only JSON output is provided.

Dependencies

  • Requires an API authentication credential configured in n8n to access the TeleFlow API.
  • The base URL for the TeleFlow API must be set in the credentials.
  • The node uses HTTP requests to communicate with the TeleFlow REST endpoints.

Troubleshooting

  • Missing ID Error: If the "ID" property is not provided, the node will throw an error stating that the ID is required for the get operation. Ensure the ID is correctly set.
  • API Request Failures: Network issues, invalid credentials, or incorrect base URL configurations can cause HTTP request failures. Verify API credentials and connectivity.
  • Field Parameter Issues: Incorrectly formatted or unsupported field names/values may result in unexpected responses or errors. Double-check field names against the TeleFlow API documentation.

Links and References

Discussion