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
The node interacts with the TeleFlow API to perform CRUD (Create, Read, Update, Delete) operations on various resources. Specifically for the Feature Code resource and the Update operation, it updates an existing feature code by its unique ID with specified fields.
This node is beneficial in scenarios where you need to programmatically manage telephony-related configurations such as feature codes within a workflow automation. For example, updating the name or other attributes of a feature code after changes in your telephony system without manual intervention.
Properties
| Name | Meaning |
|---|---|
| ID | The unique identifier of the feature code resource to update. This is required. |
| Fields | A collection of field-value pairs specifying which fields of the feature code to update. |
- The Fields property allows adding multiple entries, each with:
- Name: The name of the field 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.
- The
jsonoutput contains the full response from the API reflecting the current state of the updated feature code. - No binary data output is produced by this operation.
Dependencies
- Requires an API key credential configured in n8n to authenticate requests against the TeleFlow API.
- The base URL for the API is taken from the credential configuration.
- The node sends HTTP PUT requests to the endpoint
/featureCodes/{id}with the update payload.
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 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, network connectivity, and field correctness.
- Continue On Fail: If enabled, errors will be caught and returned as part of the output JSON instead of stopping execution.
Links and References
- TeleFlow API Documentation (Replace with actual URL if available)
- n8n HTTP Request Node documentation for understanding how HTTP methods are used within workflows.