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 Device Templates. Specifically, the Update operation for the Device Template resource allows users to modify an existing device template by specifying its unique ID and the fields to update.
Common scenarios where this node is beneficial include automating updates to device templates in bulk or integrating device template management into larger workflows, such as provisioning or configuration management systems.
For example, you might use this node to update the name or other attributes of a device template automatically when certain conditions are met in your workflow, ensuring that your device configurations remain consistent and up-to-date without manual intervention.
Properties
| Name | Meaning |
|---|---|
| ID | The unique identifier of the device template to update. This is required to specify which device template to modify. |
| Fields | A collection of field-value pairs representing the specific properties of the device template to update. Each pair includes: - Name: The field name to update. - Value: The new value for that field. |
Output
The node outputs an array of JSON objects corresponding to each input item processed. For the Update operation on Device Template, the output JSON contains the response from the TeleFlow API after updating the specified device template. This typically includes the updated device template's details reflecting the changes made.
No binary data output is produced by this node.
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 TeleFlow API must be set in the node credentials.
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 that the ID of the device template you want to update is correctly specified.
- Invalid Field Names or Values: Providing incorrect field names or invalid values in the "Fields" collection may cause the API to reject the request or ignore those fields. Verify field names against the TeleFlow API documentation.
- Authentication Issues: Errors related to authentication usually indicate missing or invalid API credentials. Confirm that the API key/token is correctly configured and has sufficient permissions.
- API Connectivity Problems: Network issues or incorrect base URL settings can prevent successful communication with the TeleFlow API. Check network connectivity and credential configuration.
Links and References
- TeleFlow API Documentation (Replace with actual URL)
- n8n Documentation on Creating Custom Nodes