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 LCR (Least Cost Routing) resource with the Create operation, it allows users to create a new LCR entry by sending specified fields to the TeleFlow API.
Common scenarios where this node is beneficial include automating telecom management tasks such as creating routing rules or entries in a telephony system, integrating with billing or provisioning workflows, or managing call routing configurations programmatically.
For example, a user can automate the creation of an LCR record by specifying custom fields that define routing preferences or cost parameters, enabling dynamic updates to telephony routing without manual intervention.
Properties
| Name | Meaning |
|---|---|
| Fields | A collection of field-value pairs to include in the request when creating the LCR entry. You can add multiple fields, each with a name and corresponding value, to specify details of the LCR being created. |
The "Fields" property supports multiple entries, allowing flexible specification of any number of attributes required by the TeleFlow API for the LCR resource.
Output
The node outputs an array of JSON objects, each representing the response from the TeleFlow API for the respective input item processed.
- The
jsonoutput contains the full API response for the created LCR resource, which typically includes the details of the newly created LCR entry. - 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 mandatory fields for the LCR creation are not provided, the API may return errors. Ensure all necessary fields are included in the "Fields" property.
- API Authentication Errors: If the API key or base URL is incorrect or missing, authentication will fail. Verify the credential configuration.
- ID Requirement Errors: Although not applicable for Create operation, other operations require an ID parameter; ensure correct usage per operation.
- Network Issues: Connectivity problems can cause request failures; check network access to the TeleFlow API endpoint.
- Error Handling: If an error occurs during execution, the node logs the error message. If "Continue On Fail" is enabled, the node outputs the error message in the JSON output instead of stopping execution.
Links and References
- TeleFlow API Documentation (Replace with actual URL if available)
- n8n Documentation: Creating Custom Nodes
- General REST API concepts: REST API Tutorial