Actions145
- 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
- Report Actions
- Reseller Actions
- SIP Trunk Actions
- Tariff Actions
- Tariff Code Actions
- Tariff Profile Actions
- Tenant Actions
- Tenant Audit Actions
- Transcription Actions
- User Actions
- Voice Actions
- Voice Mail Message Actions
Overview
This node integrates with the TeleFlow API to perform various operations on different resources, including Flow Templates. Specifically, for the Flow Template - Create operation, it allows users to create new flow templates by sending specified field data to the TeleFlow service.
Typical use cases include automating the creation of telephony flow templates within a larger workflow, such as setting up call routing or IVR flows programmatically. For example, a user might create a new flow template by specifying its name and other relevant properties, enabling dynamic provisioning of telephony configurations.
Properties
| Name | Meaning |
|---|---|
| Fields | A collection of field-value pairs to include in the request body. Users can add multiple fields to specify detailed attributes for the flow template being created. Each field consists of: - Name: The field's name (string). - Value: The corresponding value (string). |
Output
The node outputs an array of JSON objects, each representing the response from the TeleFlow API for the create operation. The json output contains the newly created flow template's details as returned by the API.
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 node credentials.
- The node uses HTTP requests to communicate with the TeleFlow REST endpoints.
Troubleshooting
- Missing Required Fields: If required fields for creating a flow template are not provided, the API may return errors. Ensure all mandatory fields are included in the "Fields" property.
- API Authentication Errors: Invalid or missing API credentials will cause authentication failures. Verify that the API key and base URL are correctly set in the node credentials.
- HTTP Request Failures: Network issues or incorrect endpoint URLs can cause request failures. Check connectivity and ensure the resource and operation parameters are correct.
- Error Messages: The node throws errors if required parameters like IDs are missing for certain operations. For create operations, ensure the "Fields" collection is properly populated.
Links and References
- TeleFlow API Documentation (Replace with actual URL)
- n8n HTTP Request Node documentation for understanding underlying request mechanics: https://docs.n8n.io/nodes/n8n-nodes-base.httpRequest/