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 interacts with the TeleFlow API to manage various resources, including Feature Codes. Specifically, for the "Feature Code" resource and the "Create" operation, it allows users to create new feature codes by sending specified fields to the TeleFlow system.
Common scenarios where this node is beneficial include automating the creation of telephony feature codes within a larger workflow, such as provisioning new telephony features or integrating TeleFlow management into business processes.
For example, you might use this node to programmatically add new feature codes with specific attributes defined in your workflow, avoiding manual entry in the TeleFlow interface.
Properties
| Name | Meaning |
|---|---|
| Fields | A collection of field-value pairs to include in the creation request. Users can add multiple fields specifying the name and value for each attribute relevant to the feature code being created. |
The "Fields" property supports multiple entries, allowing detailed customization of the feature code's properties during creation.
Output
The node outputs an array of JSON objects, each representing the response from the TeleFlow API after creating a feature code. The structure of the JSON corresponds directly to the API's response for the created feature code, 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 endpoints.
Troubleshooting
- Missing Required Fields: If required fields for creating a feature code are not provided, the API may return errors. Ensure all mandatory 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 set in the node credentials.
- HTTP Request Failures: Network issues or incorrect endpoint URLs can cause request failures. Check connectivity and ensure the base URL is correct.
- Error Messages: The node throws errors if required parameters like IDs (for other operations) are missing. For the create operation, ensure all necessary fields are supplied to avoid errors.
If the node is set to continue on failure, errors will be returned in the output JSON under an error property instead of stopping execution.
Links and References
- TeleFlow API Documentation (Replace with actual URL)
- n8n HTTP Request Node documentation for understanding underlying HTTP calls: https://docs.n8n.io/nodes/n8n-nodes-base.httpRequest/