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 Profile resource and the Update operation, it updates an existing tariff profile by sending a PUT request to the API with specified fields.
This node is useful in scenarios where you need to programmatically update tariff profiles in TeleFlow, such as modifying pricing plans or adjusting profile details based on business rules or external triggers.
Example use case: Automatically updating tariff profile details when a new pricing strategy is deployed, ensuring all related systems stay synchronized without manual intervention.
Properties
| Name | Meaning |
|---|---|
| ID | The unique identifier of the Tariff Profile to update. This is required to specify which profile to modify. |
| Fields | A collection of field-value pairs representing the properties to update on the Tariff Profile. You can add multiple fields, each with a name and corresponding value. |
Output
- The output is a JSON object representing the updated Tariff Profile as returned by the TeleFlow API.
- The structure depends on the API response but typically includes the updated fields and metadata about the tariff profile.
- 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 to authorize requests.
- The base URL for the API must be set in the node credentials configuration.
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 may cause the HTTP request to fail. Check API credentials and field names for correctness.
- Partial updates: Only fields included in the "Fields" collection are updated; omitting necessary fields might lead to incomplete updates.
- Continue on Fail: If enabled, the node will continue processing subsequent items even if one update fails, returning error details in the output JSON.
Links and References
- TeleFlow API Documentation (Replace with actual link)
- n8n Documentation on HTTP Request Node (for understanding underlying HTTP calls)
- General guide on Using API Credentials in n8n