Actions82
- 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
Overview
This node interacts with the TeleFlow API to manage various resources such as accounts, devices, phone numbers, and feature codes. Specifically, for the Feature Code resource with the Update operation, it updates an existing feature code by its unique ID with specified fields.
Common scenarios where this node is beneficial include automating the management of telephony system configurations, updating feature codes programmatically in bulk, or integrating TeleFlow feature code updates into larger workflows.
For example, you might use this node to update the name or other attributes of a feature code identified by its ID without manually accessing the TeleFlow interface.
Properties
Name | Meaning |
---|---|
ID | The unique identifier of the feature code to update. This is required to specify which feature code to modify. |
Fields | A collection of field-value pairs representing the properties to update on the feature code. Each pair includes: - Name: The field name to update. - Value: The new value for that field. |
Output
The output is a JSON object representing the updated feature code resource as returned by the TeleFlow API after the update operation. It contains all the current properties of the feature code, reflecting the changes made.
No binary data output is produced by this node.
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 of the feature code to update is correctly set.
- API Request Failures: Network issues, invalid credentials, or incorrect field names can cause the API request to fail. Check the API key validity, network connectivity, and ensure the fields being updated are valid for the feature code resource.
- Partial Updates: Only fields included in the "Fields" collection are updated; others remain unchanged. Make sure to include all necessary fields if a full update is intended.
- Continue On Fail: If enabled, the node will continue processing subsequent items even if one update fails, returning the error message in the output JSON for that item.
Links and References
- TeleFlow API Documentation (Replace with actual URL)
- n8n HTTP Request Node Documentation
- n8n Custom Node Development Guide