TeleFlow icon

TeleFlow

Interact with TeleFlow API

Overview

This node interacts with the TeleFlow API to perform various operations on different resources, including creating, retrieving, updating, and deleting entities. Specifically, for the Tariff resource with the Create operation, it allows users to create a new tariff entry by sending specified fields to the TeleFlow system.

This node is beneficial in scenarios where you need to automate the management of telecommunication tariffs within your workflows, such as setting up new pricing plans or updating existing ones programmatically.

Example use case: Automatically create new tariff entries based on external data feeds or user input, enabling dynamic tariff management without manual intervention.

Properties

Name Meaning
Fields A collection of field-value pairs to include in the creation request. Users can add multiple fields specifying the name and value for each property relevant to the tariff being created.

The "Fields" property supports multiple entries, each consisting of:

  • Name: The field name to set in the tariff.
  • Value: The corresponding value for that field.

Output

The node outputs an array of JSON objects, each representing the response from the TeleFlow API after creating a tariff. The structure of the JSON output corresponds directly to the API's response for a newly created tariff entity, typically including details such as the tariff ID, name, and other properties returned by the API.

No binary data output is produced by this node.

Dependencies

  • Requires an active connection to the TeleFlow API.
  • Needs an API authentication token or key configured in the node credentials to authorize requests.
  • The base URL for the TeleFlow API must be set in the credentials configuration.

Troubleshooting

  • Missing required fields: If mandatory fields for creating a tariff are not provided, the API may return errors. Ensure all necessary fields are included in the "Fields" property.
  • Authentication errors: If the API key or token is invalid or missing, requests will fail. Verify credential setup.
  • API endpoint issues: Network problems or incorrect base URL settings can cause request failures. Confirm the base URL and network connectivity.
  • Error messages: The node throws errors if required parameters (like IDs for other operations) are missing or if the API returns an error. When using "continue on fail," errors are captured in the output JSON under an error property.

Links and References

Discussion