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. Specifically, for the Tenant Audit resource with the Get operation, it retrieves detailed information about a specific tenant audit record by its unique ID. This is useful in scenarios where you need to fetch audit logs or history related to tenants for compliance, troubleshooting, or monitoring purposes.
For example, you might use this node to:
- Retrieve audit details of a tenant after a configuration change.
- Fetch tenant audit records to verify user activities or system events.
- Integrate tenant audit data into reporting or alerting workflows.
Properties
| Name | Meaning |
|---|---|
| ID | The unique identifier of the tenant audit record to retrieve. This is required. |
| Fields | Optional field-value pairs to include additional query parameters for more specific data. You can add multiple fields, each with a name and value. |
Output
The output is a JSON object representing the tenant audit record retrieved from the TeleFlow API. It contains all the details of the specified tenant audit entry as returned by the API.
No binary data output is produced by this operation.
Example output structure (simplified):
{
"id": "string",
"timestamp": "string",
"user": "string",
"action": "string",
"details": "object"
}
The exact fields depend on the TeleFlow API response for tenant audits.
Dependencies
- Requires an active connection to the TeleFlow API.
- Needs an API authentication token configured in the node credentials.
- The base URL for the TeleFlow API must be set in the 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 tenant audit ID.
- API request failures: Network issues, invalid credentials, or incorrect base URL configurations can cause HTTP request errors. Verify your API key and endpoint settings.
- Invalid field names: Providing unsupported or misspelled field names in the Fields property may result in incomplete or failed queries. Double-check field names against the TeleFlow API documentation.
Links and References
- TeleFlow API Documentation (replace with actual URL)
- n8n Documentation on HTTP Request Node for understanding how API calls are made within nodes.