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 Many operation, it retrieves multiple tenant audit records from the TeleFlow system. This is useful for auditing and monitoring changes or activities related to tenants in an organization.
Common scenarios include:
- Fetching audit logs to review tenant activity history.
- Filtering tenant audits based on specific fields to narrow down results.
- Integrating tenant audit data into workflows for compliance or reporting purposes.
Example: You might use this node to get all tenant audit entries where a particular field (e.g., "user" or "action") matches a certain value, helping you track who made changes and when.
Properties
| Name | Meaning |
|---|---|
| Fields | Field-value pairs to filter the request. You can specify multiple fields to refine the query. For example, you might add a field named "user" with a value of "admin" to get audits related to that user. |
The "Fields" property is a fixed collection allowing multiple entries, each with:
- Name: The name of the field to filter by.
- Value: The value to match for that field.
Output
The output is an array of JSON objects representing tenant audit records retrieved from the TeleFlow API. Each object corresponds to one audit entry and contains all relevant audit details as provided by the API.
No binary data is output by this node.
Dependencies
- Requires an API key credential for authenticating with the TeleFlow API.
- The base URL for the TeleFlow API must be configured in the credentials.
- The node uses HTTP requests to communicate with the TeleFlow API endpoints.
Troubleshooting
- Missing or invalid API credentials: Ensure the API key and base URL are correctly set in the node's credentials.
- Empty or no results returned: Check the field filters; overly restrictive filters may return no data.
- Error messages about missing ID: Not applicable for "Get Many" operation but common in other operations requiring an ID.
- HTTP errors: Network issues or incorrect API endpoint URLs can cause failures. Verify connectivity and configuration.
- If the node throws errors, enabling "Continue On Fail" allows the workflow to proceed while capturing error details in the output.
Links and References
- TeleFlow API Documentation (replace with actual URL)
- n8n documentation on HTTP Request Node for understanding underlying HTTP calls
- General n8n Custom Node Development Guide