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 integrates with the TeleFlow API to perform various operations on different resources. Specifically, for the Provision resource with the Create operation, it allows users to create new provision entries by sending specified fields to the TeleFlow system.
Typical use cases include automating the provisioning of telephony or communication-related configurations within TeleFlow, such as setting up new devices, accounts, or other provisionable entities programmatically. For example, a user might automate the creation of provisioning records when onboarding new customers or devices in bulk.
Properties
| Name | Meaning |
|---|---|
| Fields | A collection of field-value pairs to include in the creation request. Users can add multiple fields specifying the exact data to send for the provision creation. Each field has: - Name: The name of the field to set. - Value: The value to assign to that field. |
Output
The node outputs an array of JSON objects, each representing the response from the TeleFlow API after creating a provision entry. The structure of the JSON output corresponds directly to the API's response for the created provision resource, typically including identifiers and any relevant metadata 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 mandatory fields for the provision creation are included.
- API Authentication Errors: If the API key or base URL is incorrect or missing, authentication will fail. Verify the credential configuration.
- HTTP Request Failures: Network issues or incorrect endpoint URLs can cause errors. Check connectivity and ensure the resource path
/provisionsis correct. - Error Messages: The node throws errors if required parameters are missing (e.g., ID for get/update/delete operations). For create, ensure fields are properly set. If the node is set to continue on fail, errors will be returned in the output JSON under an
errorkey.
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/