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. Specifically, for the Carrier resource with the Create operation, it allows users to create a new carrier entity by sending specified fields to the TeleFlow system.
Common scenarios where this node is beneficial include automating the management of telecommunication carriers within a business workflow, such as adding new carriers dynamically based on external data or user input.
For example, a user might use this node to add a new carrier with specific attributes (like name, code, or other custom fields) whenever a new carrier contract is signed, streamlining the provisioning process.
Properties
| Name | Meaning |
|---|---|
| Fields | A collection of field-value pairs to include in the creation request. Users can add multiple fields specifying the carrier's attributes. Each field has: - Name: The field name to set. - 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 carrier. The structure of the JSON output corresponds directly to the API's response for a newly created carrier, typically including details like the carrier's ID, name, and any other properties returned by the API.
No binary data output is produced by this node.
Dependencies
- Requires an active connection to the TeleFlow API.
- Needs an API authentication credential configured in n8n (an API key or token).
- The base URL for the TeleFlow API must be set in the credentials configuration.
- The node uses HTTP POST requests to send creation data to the
/carriersendpoint of the TeleFlow API.
Troubleshooting
- Missing Required Fields: If required fields for creating a carrier are not provided, the API may return an error. Ensure all mandatory fields expected by the TeleFlow API for a carrier are included in the "Fields" property.
- Authentication Errors: If the API key or credentials are invalid or missing, the node will fail to authenticate. Verify that the API credentials are correctly configured.
- API Endpoint Issues: If the base URL is incorrect or the TeleFlow service is unreachable, HTTP requests will fail. Confirm network connectivity and correct API endpoint configuration.
- Error Messages: The node throws errors if required parameters like IDs are missing for other operations, but for the Create operation, ensure the fields are properly set. If an error occurs, enabling "Continue On Fail" allows the workflow to proceed while capturing error messages in the output.
Links and References
- TeleFlow API Documentation (Replace with actual URL)
- n8n HTTP Request Node Documentation: https://docs.n8n.io/nodes/n8n-nodes-base.httpRequest/