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 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 logs or history related to accounts for compliance, troubleshooting, or monitoring purposes.
Practical examples:
- Fetching an audit record to review changes made to an account.
- Retrieving audit details before generating reports or alerts.
- Integrating audit data into workflows for automated compliance checks.
Properties
Name | Meaning |
---|---|
ID | The unique identifier of the Account Audit record to retrieve. This is required. |
Fields | Optional key-value pairs specifying additional fields to include in the request query string. You can add multiple field name and value pairs to filter or customize the returned data. |
Output
The node outputs JSON data representing the retrieved Account Audit record. The structure corresponds directly to the API response for the specified audit ID, containing all relevant audit details such as timestamps, user actions, and changed data.
No binary data output is produced by this operation.
Example output snippet (conceptual):
{
"id": "audit123",
"accountId": "account456",
"action": "update",
"changedFields": {
"name": "New Account Name"
},
"timestamp": "2024-01-01T12:00:00Z",
"user": "adminUser"
}
Dependencies
- Requires an active connection to the TeleFlow API.
- Needs an API authentication credential configured in n8n with base URL and access token.
- The node uses HTTP requests to communicate with the TeleFlow REST endpoints.
Troubleshooting
- Missing ID error: If the "ID" property is not provided for the get operation, the node will throw an error stating that the ID is required. Ensure you provide a valid audit record ID.
- Authentication errors: If the API credentials are invalid or missing, the node will fail to connect. Verify your API key/token and base URL configuration.
- Network issues: Timeouts or connectivity problems may cause failures. Check network access to the TeleFlow API endpoint.
- Invalid fields: Providing incorrect or unsupported field names in the "Fields" collection may result in incomplete or empty responses. Confirm field names against the TeleFlow API documentation.
Links and References
- TeleFlow API Documentation (replace with actual URL)
- n8n HTTP Request Node Documentation: https://docs.n8n.io/nodes/n8n-nodes-base.httpRequest/
- General n8n Credential Setup Guide: https://docs.n8n.io/credentials/overview/