TeleFlow icon

TeleFlow

Interact with TeleFlow API

Actions82

Overview

This node interacts with the TeleFlow API to manage various resources, including Billing Entries. Specifically, the Update operation for the Billing Entry resource allows users to modify existing billing entry records by specifying their unique ID and providing updated field values.

Common scenarios where this node is beneficial include:

  • Adjusting billing details after corrections or audits.
  • Updating billing entries with new information such as descriptions or amounts.
  • Automating billing data maintenance within workflows that integrate TeleFlow with other systems.

For example, a user might automate updating billing entries after receiving corrected invoice data from an external accounting system.

Properties

Name Meaning
ID The unique identifier of the billing entry to update. This is required to specify which record to modify.
Fields A collection of field-value pairs representing the properties of the billing entry to update. Each pair includes:
- Name: The name of the field to update.
- Value: The new value to assign to that field.

Output

The node outputs an array of JSON objects, each representing the response from the TeleFlow API after attempting to update a billing entry. The structure corresponds to the updated billing entry data returned by the API.

No binary data output is produced by this operation.

Example output JSON snippet (conceptual):

{
  "id": "12345",
  "field1": "updated value",
  "field2": "another updated value",
  ...
}

Dependencies

  • Requires an active connection to the TeleFlow API via an API key credential configured in n8n.
  • The base URL for the TeleFlow API must be set in the node credentials.
  • The node uses HTTP methods (PUT) to communicate with the API endpoint corresponding to billing entries.

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 update operation. Ensure the ID of the billing entry to update is specified.
  • API Request Failures: Network issues, invalid credentials, or incorrect field names/values may cause the API request to fail. Check the API key validity, network connectivity, and confirm that the fields being updated exist and accept the provided values.
  • Partial Updates: Only fields included in the "Fields" collection are updated; omitting required fields may lead to incomplete updates or errors.
  • Continue on Fail: If enabled, the node will continue processing subsequent items even if one update fails, returning error details in the output JSON.

Links and References

Discussion