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 perform various operations on different resources, including "Reseller". Specifically, for the Reseller - Create operation, it allows users to create a new reseller 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 resellers within a telecom or VoIP platform, integrating reseller creation into workflows that provision accounts or services, and synchronizing reseller data from external systems.
For example, you might use this node to automatically add a new reseller when a sales team closes a deal, passing along relevant details such as the reseller's name and other custom fields.
Properties
| Name | Meaning |
|---|---|
| Fields | A collection of field-value pairs to include in the create request. Each pair specifies a field name and its corresponding value to define the reseller's properties. |
The "Fields" property supports multiple entries, allowing you to specify any number of custom fields required by the TeleFlow API for creating a reseller.
Output
The node outputs an array of JSON objects, each representing the response from the TeleFlow API after attempting to create a reseller. The JSON structure corresponds directly to the API's response, typically containing details of the newly created reseller such as its ID, name, and other attributes.
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 POST requests to communicate with the TeleFlow API endpoint for resellers.
Troubleshooting
- Missing Required Fields: If mandatory fields for creating a reseller are not provided, the API may return an error. Ensure all required fields 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 incorrect field names can cause the request to fail. Check the error message returned by the node for clues.
- 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 instead of stopping execution.
Links and References
- TeleFlow API Documentation (Replace with actual URL)
- n8n HTTP Request Node documentation: https://docs.n8n.io/nodes/n8n-nodes-base.httpRequest/