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 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 examples include:
- Updating audit trail entries when additional context or corrections are needed.
- Modifying metadata associated with account audits for compliance or reporting purposes.
Properties
| Name | Meaning |
|---|---|
| ID | The unique identifier of the Account Audit record to update. This is required. |
| Fields | A collection of field-value pairs specifying which fields to update and their new values. |
The Fields property allows multiple entries, each consisting of:
- 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 resource as returned by the TeleFlow API. It contains all the properties of the updated audit record reflecting the changes made.
No binary data output is produced by this operation.
Dependencies
- Requires an active connection to the TeleFlow API.
- Needs an API authentication token configured in the node credentials.
- The base URL for the API must be set in the node's credential 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 specified.
- API Request Failures: Network issues or invalid credentials can cause HTTP request failures. Verify API keys and network connectivity.
- Invalid Field Names or Values: Providing incorrect field names or incompatible values may result in API errors. Double-check the field names against the TeleFlow API documentation.
- Continue On Fail: If enabled, the node will continue processing subsequent items even if one fails, returning error details in the output JSON.
Links and References
- TeleFlow API Documentation (Replace with actual URL)
- n8n Documentation on Creating Custom Nodes