TeleFlow icon

TeleFlow

Interact with TeleFlow API
Join our community

Actions145

Overview

This node interacts with the TeleFlow API to perform various operations on different resources. Specifically, for the Provision resource and the Get Many operation, it retrieves multiple provision records from the TeleFlow system. This is useful when you want to fetch a list of provisions with optional filtering based on specific fields.

Common scenarios include:

  • Retrieving all provision entries to display or process them in bulk.
  • Filtering provisions by certain attributes (e.g., name, status) to narrow down results.
  • Integrating TeleFlow provisioning data into workflows for reporting or automation.

Example: You might use this node to get all provisions where the "status" field equals "active" to trigger further processing only on active provisions.

Properties

Name Meaning
Fields A collection of field-value pairs used to filter the request. You can specify multiple fields to refine the query. For example, you could add a field "status" with value "active" to retrieve only active provisions.

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

  • Name: The field name to filter by (string).
  • Value: The corresponding value to match (string).

Output

The output is an array of JSON objects representing the provision records retrieved from the TeleFlow API. Each item corresponds to one provision entry matching the query parameters.

  • The json field contains the raw response data from the API call.
  • 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 API must be configured in the node credentials.
  • The node sends HTTP requests with JSON content type and expects JSON responses.

Troubleshooting

  • Missing or invalid API credentials: Ensure that the API key and base URL are correctly set in the node credentials.
  • Empty or no results returned: Verify that the field filters are correct and that matching provisions exist.
  • Error messages about missing ID: Not applicable for "Get Many" operation but relevant for other operations like "Get" or "Update".
  • HTTP errors: Check network connectivity and API endpoint availability.
  • If the node is set to continue on fail, errors will be returned as JSON objects with an error property instead of stopping execution.

Links and References

Discussion