TeleFlowInstall

Overview

This node interacts with the TeleFlow API to manage various resources, including Call Detail Records (CDRs). Specifically, for the Call Detail Record resource and the Create operation, it allows users to create new call detail records by sending specified fields to the TeleFlow system.

Typical use cases include:

• Automatically logging call details into TeleFlow from other systems.
• Creating custom call records based on external data inputs.
• Integrating call data creation as part of a larger workflow automation.

For example, you might use this node to create a CDR entry whenever a call is completed in your telephony system, passing relevant metadata such as caller ID, call duration, or call status.

Properties

The "Fields" property supports multiple entries, each consisting of:

• Name: The name of the field to set on the Call Detail Record.
• Value: The value to assign to that field.

This flexible structure allows specifying any number of custom fields required by the TeleFlow API for creating a CDR.

Output

The node outputs an array of JSON objects, each representing the response from the TeleFlow API after creating a Call Detail Record. The exact structure depends on the API's response but typically includes the newly created record's details such as its unique identifier and the fields set.

No binary data output is produced by this node.

Example output snippet (conceptual):

{
  "id": "12345",
  "caller": "+1234567890",
  "duration": 300,
  "status": "completed",
  ...
}

Dependencies

• Requires an API key credential for authenticating with the TeleFlow API.
• The base URL for the TeleFlow API must be configured in the node credentials.
• The node uses HTTP requests to communicate with the TeleFlow REST endpoints.

Troubleshooting

• Missing Required Fields: If mandatory fields for creating a Call Detail Record are not provided, the API may return validation errors. Ensure all required fields are included in the "Fields" property.
• Authentication Errors: Incorrect or missing API credentials will cause authentication failures. Verify the API key and base URL configuration.
• ID Requirement for Other Operations: Although not applicable for Create, other operations like Get, Update, or Delete require an ID parameter. Omitting it will throw an error.
• API Request Failures: Network issues or incorrect endpoint URLs can cause HTTP request failures. Check connectivity and credential settings.
• Error Handling: If the node is set to continue on fail, errors will be returned as JSON objects with an "error" message instead of stopping execution.

Links and References

• TeleFlow API Documentation (Replace with actual URL)
• n8n Documentation on Creating Custom Nodes
• General REST API usage in n8n: HTTP Request Node