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 "Voice". Specifically, for the "Voice" resource and the "Create" operation, the node allows users to create a new voice-related entity in the TeleFlow system by sending specified fields as part of the request.
Common scenarios where this node is beneficial include automating the creation of voice configurations or entries within TeleFlow as part of a larger workflow, such as provisioning new voice services or managing telephony resources programmatically.
For example, a user might use this node to create a new voice configuration by specifying relevant fields, which then triggers downstream processes like updating billing or notifying administrators.
Properties
| Name | Meaning |
|---|---|
| Fields | A collection of field-value pairs to include in the creation request. Users can add multiple fields, each consisting of a name and its corresponding value, to specify details for the new voice entity. |
Output
The node outputs an array of JSON objects, each representing the response from the TeleFlow API after creating a voice resource. The structure of the json output corresponds directly to the API's response for the created voice entity, typically including identifiers and any other data 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.
Troubleshooting
- Missing Required Fields: If required fields for creating a voice resource are not provided, the API may return errors. Ensure all mandatory fields are included in the "Fields" property.
- 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 HTTP request to fail. Check error messages logged by the node for details.
- Error Handling: If the node is set to continue on failure, errors will be returned in the output JSON under an
errorproperty; otherwise, execution will stop on the first error.
Links and References
- TeleFlow API Documentation (Replace with actual URL)
- n8n Documentation on Creating Custom Nodes