TeleFlow icon

TeleFlow

Interact with TeleFlow API

Actions82

Overview

The node interacts with the TeleFlow API to perform various operations on different resources. Specifically, for the Carrier resource with the Update operation, it updates an existing carrier's details by sending a PUT request to the TeleFlow API. This is useful when you need to modify carrier information such as its name or other attributes dynamically within an automation workflow.

Practical examples include:

  • Updating carrier details after receiving new information from an external system.
  • Automating maintenance tasks where carrier data needs periodic updates.
  • Integrating with CRM or billing systems to keep carrier records synchronized.

Properties

Name Meaning
ID The unique identifier of the carrier resource to update. This is required.
Fields A collection of field-value pairs specifying which fields to update and their new values.

Note: The "Fields" property allows multiple entries, each with:

  • Name: The field name to update.
  • Value: The new value for that field.

Output

The output is an array of JSON objects representing the updated carrier resource as returned by the TeleFlow API. Each item corresponds to one update operation and contains the full updated carrier data.

No binary data output is produced by this node.

Example output structure (simplified):

{
  "id": "carrier-id",
  "name": "Updated Carrier Name",
  "...": "other carrier properties"
}

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 uses HTTP requests to communicate with the TeleFlow REST API.

Troubleshooting

  • Missing ID error: If the "ID" property is not provided for the update operation, the node will throw an error stating that the ID is required. Ensure the ID is correctly set.
  • API request failures: Network issues, invalid credentials, or incorrect field names can cause HTTP errors. Verify API credentials and field names.
  • Field validation: The API may reject updates if field values are invalid or missing required fields. Double-check the fields and values sent.
  • Continue on Fail: If enabled, the node will continue processing subsequent items even if one fails, returning error details in the output JSON.

Links and References

Discussion