TeleFlow icon

TeleFlow

Interact with TeleFlow API

Overview

This node interacts with the TeleFlow API to manage various resources, including Billing Entries. Specifically, for the Billing Entry - Delete operation, it deletes a billing entry identified by its unique ID from the TeleFlow system.

Common scenarios where this node is beneficial include:

  • Automating cleanup of obsolete or incorrect billing entries.
  • Integrating TeleFlow billing management into broader workflows that handle account and usage data.
  • Programmatically managing billing data without manual intervention in the TeleFlow UI.

For example, you might use this node in a workflow that detects duplicate billing entries and automatically removes them, or in a process that archives old billing data by deleting entries after export.

Properties

Name Meaning
ID The unique identifier of the billing entry to delete. This is required to specify which billing entry to remove.
Fields Optional field-value pairs to include in the request for more specific queries (not typically used in delete but available for other operations).

Output

The output JSON contains the response from the TeleFlow API after attempting to delete the specified billing entry. Typically, this will be an object indicating success or failure of the deletion operation. The exact structure depends on the API's response but generally confirms whether the resource was deleted.

No binary data output is produced by this operation.

Example output JSON might look like:

{
  "success": true,
  "message": "Billing entry deleted successfully"
}

or in case of error:

{
  "error": "Billing entry not found"
}

Dependencies

  • Requires an active connection to the TeleFlow API via an API key credential configured in n8n.
  • The node uses HTTP requests to communicate with the TeleFlow API endpoint defined by the base URL in the credentials.
  • Proper permissions on the API key are necessary to perform delete operations on billing entries.

Troubleshooting

  • Missing ID Error: If the "ID" property is not provided, the node throws an error stating that the ID is required. Ensure you provide a valid billing entry ID.
  • API Authentication Errors: If the API key or base URL is incorrect or missing, the node will fail to authenticate. Verify your credentials configuration.
  • Resource Not Found: If the billing entry ID does not exist, the API may return an error indicating the resource was not found. Confirm the ID is correct.
  • Permission Denied: Insufficient permissions on the API key can cause authorization errors. Check that the API key has delete rights for billing entries.
  • Network Issues: Connectivity problems can cause request failures. Ensure the n8n instance has network access to the TeleFlow API endpoint.

Links and References

Discussion