Actions145
- User Actions
- Voice Actions
- File Actions
- Flow Actions
- Reseller Actions
- SIP Trunk Actions
- Transcription Actions
- Voice Mail Message Actions
- 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
- Flow Template Actions
- LCR Actions
- Mobile SIM Actions
- Number Port Actions
- Phone Number Actions
- Provision Actions
- Report Actions
- Tariff Actions
- Tariff Code Actions
- Tariff Profile Actions
- Tenant Actions
- Tenant Audit Actions
Overview
This node integrates with the TeleFlow API to perform various operations on different resources, including "Voice". Specifically, for the "Voice" resource and the "Create" operation, it allows users to create a new voice-related entity by sending specified fields to the TeleFlow API. This is useful in scenarios where you want to programmatically add voice configurations or records within TeleFlow as part of an automated workflow.
For example, you might use this node to create a new voice configuration by specifying custom fields that define its properties, enabling seamless integration of voice management into your automation processes.
Properties
| Name | Meaning |
|---|---|
| Fields | A collection of field-value pairs to include in the creation request. Users can add multiple fields, each with a name and corresponding value, to specify details about the voice entity being created. |
Output
The node outputs JSON data representing the response from the TeleFlow API after creating the voice resource. This typically includes the details of the newly created voice entity 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 API endpoints.
Troubleshooting
- Missing Required Fields: If required fields are not provided in the "Fields" property, the API may reject the request. Ensure all necessary fields for creating a voice resource are included.
- Authentication Errors: If the API key or base URL is incorrect or missing, authentication will fail. Verify that the API credentials are correctly set up.
- API Request Failures: Network issues or invalid field values can cause the API request to fail. Check error messages logged by the node for details.
- Error Messages: The node throws errors if required parameters like resource ID (for other operations) are missing. For the create operation, ensure the "Fields" collection is properly populated.
Links and References
- TeleFlow API Documentation (Replace with actual URL)
- n8n Documentation on Creating Custom Nodes