Actions145
- User Actions
- Voice Actions
- File Actions
- Flow Actions
- Reseller Actions
- SIP Trunk Actions
- Transcription Actions
- Voice Mail Message Actions
- 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
- Flow Template Actions
- LCR Actions
- Mobile SIM Actions
- Number Port Actions
- Phone Number Actions
- Provision Actions
- Report Actions
- Tariff Actions
- Tariff Code Actions
- Tariff Profile Actions
- Tenant Actions
- Tenant Audit Actions
Overview
The node interacts with the TeleFlow API to perform various operations on different resources. Specifically, for the Tariff resource and the Update operation, it updates an existing tariff entry identified by its unique ID. This is useful in scenarios where you need to modify tariff details dynamically, such as updating pricing plans or tariff attributes in a telecom billing system.
Practical example: You have a tariff plan that needs a name change or other attribute updates. Using this node, you can specify the tariff ID and the fields to update, and the node will send the update request to the TeleFlow API.
Properties
| Name | Meaning |
|---|---|
| ID | The unique identifier of the tariff resource to update. This is required. |
| Fields | A collection of field-value pairs representing the properties of the tariff to be updated. Each pair includes: - Name: The field name to update (string). - Value: The new value for the field (string). |
Output
The output is a JSON object representing the response from the TeleFlow API after the update operation. It typically contains the updated tariff resource data reflecting the changes made.
No binary data output is produced by this operation.
Dependencies
- Requires an active connection to the TeleFlow API.
- Needs an API authentication token or key configured in the node credentials.
- The base URL for the TeleFlow API must be set in the node's credential configuration.
Troubleshooting
- Missing ID Error: If the "ID" property is not provided, the node throws an error stating that the ID is required for the update operation. Ensure the ID is correctly specified.
- API Request Failures: Network issues or invalid credentials may cause HTTP request failures. Verify API keys and network connectivity.
- Invalid Field Names: Providing incorrect or unsupported field names in the "Fields" collection may result in API errors. Confirm field names are valid according to TeleFlow API documentation.
- Continue On Fail: If enabled, the node will continue processing subsequent items even if one fails, returning error details in the output JSON.
Links and References
- TeleFlow API Documentation (Replace with actual URL)
- n8n Documentation on HTTP Request Node (for understanding underlying HTTP calls)