TeleFlow icon

TeleFlow

Interact with TeleFlow API

Overview

This node interacts with the TeleFlow API to manage various resources such as accounts, devices, phone numbers, users, and more. Specifically, for the Account - Delete operation, it deletes an account resource identified by a unique ID. This is useful in scenarios where you need to programmatically remove obsolete or unwanted account records from your TeleFlow system.

Practical example: Automatically deleting user accounts that have been inactive for a certain period or removing test accounts created during development.

Properties

Name Meaning
ID The unique identifier of the account resource to delete. This is required.
Fields Optional field-value pairs to include in the request for more specific queries (not used in delete but available for other operations).
Additional Details Informational notice related to the Account resource (displayed in the UI, no direct effect on delete operation).

Output

The output JSON contains the response from the TeleFlow API after attempting to delete the specified account. Typically, this will be a confirmation of deletion or an empty object if successful. If the deletion fails, the output may contain error details.

No binary data is output by this node.

Example output:

{
  "success": true,
  "message": "Account deleted successfully"
}

or

{}

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 DELETE requests to the endpoint /accounts/{id} to perform deletions.

Troubleshooting

  • Missing ID Error: If the "ID" property is not provided, the node throws an error stating that the ID is required for the delete operation. Ensure you provide a valid account 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 specified account ID does not exist, the API may return a 404 error. Confirm the ID is correct.
  • Permission Denied: Insufficient permissions for the API key can cause authorization errors. Check API key scopes and permissions.
  • Continue On Fail: If enabled, the node will continue processing subsequent items even if one deletion fails, returning error details in the output JSON.

Links and References

Discussion