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 Carrier resource with the Create operation, it allows users to create a new carrier entity in the TeleFlow system by sending specified fields as part of the request.
Common scenarios where this node is beneficial include automating the management of telecommunication carriers within a workflow, such as adding new carriers dynamically based on external data or user input.
Practical example: A telecom company could use this node to automatically add new carrier information received from a partner system into their TeleFlow account without manual entry.
Properties
| Name | Meaning |
|---|---|
| Fields | Field-value pairs to include in the creation request. Users can add multiple fields specifying the carrier's attributes (e.g., name, description). |
The "Fields" property is a fixed collection allowing multiple entries, each consisting of:
- Name: The field name to set on the carrier.
- 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 the created carrier, typically including details like the carrier's ID, name, and other attributes 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 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 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 base URL is incorrect or missing, authentication will fail. Verify the credential configuration.
- API Request Failures: Network issues or invalid field names/values can cause request failures. Check error messages logged by the node for details.
- Error Messages: The node throws errors if required parameters are missing or if the API returns an error. When "Continue On Fail" is enabled, errors are returned as JSON objects with an "error" property containing the message.
Links and References
- TeleFlow API Documentation (hypothetical link)
- n8n HTTP Request Node documentation for understanding underlying request mechanics: https://docs.n8n.io/nodes/n8n-nodes-base.httpRequest/