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 Resellers. Specifically, the Update Reseller operation allows users to modify details of an existing reseller by specifying its unique ID and the fields to update.
Common scenarios for this node include automating updates to reseller information in bulk or integrating TeleFlow reseller management into broader workflows. For example, a user might update reseller names or other attributes programmatically when syncing data from another system.
Properties
| Name | Meaning |
|---|---|
| ID | The unique identifier of the reseller resource to update. This is required. |
| Fields | A collection of field-value pairs representing the properties to update on the reseller. Each pair includes: - Name: The name of the field to update. - Value: The new value for that field. |
Output
The node outputs JSON data representing the updated reseller resource as returned by the TeleFlow API after a successful update operation. The structure corresponds to the API's response format for a reseller object, typically including updated fields and metadata.
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 methods (PUT) to communicate with the TeleFlow REST API endpoints.
Troubleshooting
- Missing ID Error: If the "ID" property is not provided, the node will throw an error stating that the ID is required for the update operation. Ensure the ID is correctly set.
- API Request Failures: Network issues, invalid credentials, or incorrect field names/values may cause the API request to fail. Check the API key validity, endpoint accessibility, and field correctness.
- Partial Updates: Only fields specified in the "Fields" collection are updated; omitting required fields or providing invalid values may result in incomplete or failed updates.
- Error Handling: If the node is set to continue on failure, errors will be included in the output JSON under an
errorproperty instead of stopping execution.
Links and References
- TeleFlow API Documentation (Replace with actual URL)
- n8n HTTP Request Node documentation for understanding underlying HTTP calls: https://docs.n8n.io/nodes/n8n-nodes-base.httpRequest/