Actions82
- Account Actions
- Account Audit Actions
- Billing Entry Actions
- Call Detail Record Actions
- Carrier Actions
- Device Actions
- Device Template Actions
- Email Template Actions
- Feature Code Actions
- File Actions
- Flow Actions
- Flow Template Actions
- LCR Actions
- Mobile SIM Actions
- Number Port Actions
- Phone Number Actions
- Provision Actions
Overview
This node, named "TeleFlow," interacts with the TeleFlow API to perform various operations on different resources. Specifically for the Flow Template resource with the Create operation, it allows users to create new flow templates by sending specified fields to the TeleFlow API.
Common scenarios where this node is beneficial include automating the creation of telephony flow templates in bulk or integrating TeleFlow template management into broader workflows. For example, a user might automate creating customized call routing flows based on external data or trigger template creation as part of a provisioning process.
Properties
| Name | Meaning |
|---|---|
| Fields | A collection of field-value pairs to include in the request body when creating the flow template. Users can add multiple fields specifying the exact properties and values for the new flow template. |
The "Fields" property supports multiple entries, each consisting of:
- Name: The name of the field to set.
- Value: The value to assign to that field.
This flexible structure allows users to specify any number of custom fields required by the TeleFlow API for creating a flow template.
Output
The node outputs an array of JSON objects, each representing the response from the TeleFlow API for each input item processed.
For the Create operation on Flow Template, the output JSON contains the newly created flow template's details as returned by the API. This typically includes identifiers, names, and other metadata related to the created template.
No binary data output is produced by this node.
Dependencies
- Requires an API key credential for authenticating with the TeleFlow API.
- The base URL for the TeleFlow API must be configured in the credentials.
- The node uses HTTP requests with JSON payloads to communicate with the TeleFlow API.
Troubleshooting
- Missing Required Fields: If mandatory fields for creating a flow template are not provided, the API may return errors. Ensure all required fields are included in the "Fields" property.
- API Authentication Errors: Incorrect or missing API credentials will cause authentication failures. Verify that the API key and base URL are correctly configured.
- Invalid Field Names or Values: Providing incorrect field names or invalid values may result in API errors. Consult the TeleFlow API documentation for valid field names and expected formats.
- Network Issues: Connectivity problems can cause request failures. Check network access to the TeleFlow API endpoint.
- Error Messages: The node throws errors with messages from the API or internal validation. When "Continue On Fail" is enabled, errors are returned as JSON objects with an "error" property containing the message.
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