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 perform various operations on different resources, including "Account Audit". Specifically, for the Account Audit - Get operation, it retrieves detailed information about a specific account audit record by its unique ID. This is useful in scenarios where you need to fetch audit trail data for accounts to monitor changes, track user actions, or comply with auditing requirements.
Practical examples:
- Fetching an audit record to review changes made to an account.
- Retrieving audit details for compliance reporting.
- Debugging issues by examining historical account modifications.
Properties
| Name | Meaning |
|---|---|
| ID | The unique identifier of the Account Audit resource to retrieve. This is required. |
| Fields | Optional key-value pairs specifying additional fields to include as query parameters in the request. You can add multiple field name and value pairs to filter or customize the returned data. |
Output
The output is a JSON object representing the retrieved Account Audit record from the TeleFlow API. It contains all the properties of the audit entry as returned by the API, which typically includes metadata such as timestamps, user info, changes made, and other audit details.
No binary data output is produced by this operation.
Dependencies
- Requires an active connection to the TeleFlow API.
- Needs an API authentication credential configured in n8n (an API key or token).
- 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. Ensure you provide a valid ID for the audit record.
- API connectivity issues: Errors related to network or authentication failures may occur if the API key is invalid or the base URL is incorrect. Verify your credentials and endpoint configuration.
- Invalid field names: Providing unsupported or incorrect field names in the "Fields" property may result in unexpected API responses or errors. Double-check the API documentation for valid query parameters.
Links and References
- TeleFlow API Documentation (replace with actual URL)
- n8n HTTP Request Node Documentation