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, including accounts. Specifically, the Account - Get operation retrieves detailed information about a single account by its unique identifier. This is useful when you need to fetch current data for an account, such as in customer management, billing reconciliation, or auditing scenarios.

For example, you might use this node to:

  • Retrieve an account's details before updating it.
  • Fetch specific fields of an account for reporting purposes.
  • Integrate account data into other workflows or systems.

Properties

Name Meaning
ID The unique identifier of the account resource to retrieve. This is required.
Fields Optional key-value pairs specifying additional query parameters to filter or customize the returned data. Each pair consists of a field name and its value.
Additional Details Informational notice related to the Account resource (displayed in the UI, no input).

Output

The output is a JSON object representing the retrieved account data as returned by the TeleFlow API. It contains all the fields of the account resource, potentially filtered or customized based on the optional "Fields" input.

No binary data is output by this operation.

Example output structure (simplified):

{
  "id": "string",
  "name": "string",
  "otherAccountField1": "...",
  "otherAccountField2": "..."
}

Dependencies

  • Requires an API authentication credential configured in n8n to access the TeleFlow API.
  • The base URL for the API is taken from the credential configuration.
  • The node sends HTTP requests with JSON content type and expects JSON responses.

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 you provide a valid account ID.
  • API request failures: Errors from the TeleFlow API (e.g., invalid ID, network issues) will be logged and can cause the node to fail unless "Continue On Fail" is enabled.
  • Incorrect field names in "Fields": Providing invalid or unsupported field names in the "Fields" collection may result in unexpected API responses or errors.

Links and References

Discussion