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 interacts with the TeleFlow API to manage various resources, including Feature Codes. Specifically, the "Feature Code" resource's "Create" operation allows users to create new feature codes by sending specified fields to the API. This is useful in telephony systems where feature codes represent special dialing sequences or service activations.
Practical examples include:
- Creating a new feature code to enable call forwarding.
- Adding custom feature codes for internal telephony features.
- Automating the setup of telephony services via workflows.
Properties
| Name | Meaning |
|---|---|
| Fields | A collection of field-value pairs to include in the creation request. Users can add multiple fields specifying the properties of the feature code to be created. |
The "Fields" property supports multiple entries, each consisting of:
- Name: The name of the field to set on the feature code.
- Value: The corresponding value for that field.
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 output corresponds directly to the API's response for the created feature code, typically including details such as the feature code's ID, name, and other attributes as returned by the API.
No binary data output is produced by this operation.
Dependencies
- Requires an API key credential for authenticating with the TeleFlow API.
- The base URL for the API must be configured in the credentials.
- The node uses HTTP requests to communicate with the TeleFlow REST API.
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 configured.
- Invalid Field Names or Values: Providing invalid field names or values may result in API errors. Double-check the field names against the TeleFlow API documentation.
- Network Issues: Connectivity problems can cause request failures. Check network access and proxy settings if applicable.
- Error Messages: The node throws errors with messages from the API or internal validation. When "Continue On Fail" is enabled, errors are returned as part of the output JSON under an
errorkey.
Links and References
- TeleFlow API Documentation (example link, replace with actual)
- n8n HTTP Request Node Documentation: https://docs.n8n.io/nodes/n8n-nodes-base.httpRequest/