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
The node interacts with the TeleFlow API to perform various operations on different resources. Specifically, for the Account Audit resource with the Update operation, it updates an existing account audit record by its unique ID. This is useful in scenarios where you need to modify audit details related to accounts, such as correcting or adding information after the initial creation.
Practical example: If an audit entry was created with incomplete or incorrect data, this node can update that entry by specifying the ID and the fields to change.
Properties
| Name | Meaning |
|---|---|
| ID | The unique identifier of the Account Audit record to update. This is required. |
| Fields | A collection of field-value pairs representing the properties to update on the record. |
- Fields allows multiple entries, each with:
- Name: The name of the field to update.
- Value: The new value to assign to that field.
Output
The output is a JSON object representing the updated Account Audit record as returned by the TeleFlow API after the update operation. It contains all the properties of the updated resource, reflecting the changes made.
No binary data output is produced by this operation.
Dependencies
- Requires an API key credential for authenticating with the TeleFlow API.
- The base URL for the API must be configured in the node credentials.
- The node uses HTTP PUT requests to update resources.
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 or invalid credentials may cause HTTP errors. Verify API key validity and network connectivity.
- Field validation errors: If the fields provided do not match expected names or types, the API might reject the update. Double-check field names and values against the TeleFlow API documentation.
- Continue on Fail: If enabled, the node will continue processing subsequent items even if one fails, returning the error message in the output JSON.
Links and References
- TeleFlow API Documentation (replace with actual URL)
- n8n HTTP Request Node documentation: https://docs.n8n.io/nodes/n8n-nodes-base.httpRequest/