TeleFlow icon

TeleFlow

Interact with TeleFlow API

Actions82

Overview

This node interacts with the TeleFlow API to perform various operations on different resources. Specifically, for the LCR (Least Cost Routing) resource and the Delete operation, it deletes an LCR entry identified by a unique ID. This is useful in scenarios where you need to programmatically remove routing configurations or entries from your telephony system managed via TeleFlow.

Practical example: If you maintain a list of LCR entries for call routing optimization and want to automate cleanup of obsolete or incorrect entries, this node can delete those entries by their IDs.

Properties

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

Output

  • The output JSON contains the response from the TeleFlow API after attempting to delete the specified LCR entry.
  • Typically, this will be a confirmation of deletion or an error message if the deletion failed.
  • No binary data is output by this operation.

Example output JSON might look like:

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

or in case of failure:

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

Dependencies

  • Requires an API key credential configured in n8n to authenticate requests to the TeleFlow API.
  • The base URL for the TeleFlow API must be set in the node credentials.
  • The node uses HTTP methods (DELETE) to communicate with the TeleFlow REST API.

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 ID.
  • API Errors: If the API returns an error (e.g., entry not found, permission denied), the node outputs the error message in the JSON output. Check that the ID exists and that your API credentials have sufficient permissions.
  • Network Issues: Connectivity problems or incorrect base URL settings may cause request failures. Verify network access and correct API endpoint configuration.
  • Continue On Fail: If enabled, the node will continue processing subsequent items even if one fails, outputting error details instead of stopping execution.

Links and References

Discussion