Actions145
- User Actions
- Voice Actions
- File Actions
- Flow Actions
- Reseller Actions
- SIP Trunk Actions
- Transcription Actions
- Voice Mail Message Actions
- 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
- Flow Template Actions
- LCR Actions
- Mobile SIM Actions
- Number Port Actions
- Phone Number Actions
- Provision Actions
- Report Actions
- Tariff Actions
- Tariff Code Actions
- Tariff Profile Actions
- Tenant Actions
- Tenant Audit 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 scenarios where you want to fetch audit logs or historical changes related to tenants in bulk, such as monitoring tenant activities, compliance auditing, or generating reports.
For example, a user might want to retrieve all tenant audit entries filtered by specific fields like date ranges or event types to analyze tenant behavior over time.
Properties
| Name | Meaning |
|---|---|
| Fields | A collection of field-value pairs used to filter or specify which fields to include in the request. You can add multiple pairs to refine your query. For each pair: - 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 the tenant audit records retrieved from the TeleFlow API. Each object corresponds to one audit entry and contains the data fields returned by the API based on the specified filters.
No binary data output is produced by this operation.
Dependencies
- Requires an API key credential for authenticating with the TeleFlow API.
- The base URL for the TeleFlow API must be configured in the node credentials.
- The node sends HTTP requests with JSON content type and expects JSON responses.
Troubleshooting
- Missing or invalid API credentials: Ensure that the API key and base URL are correctly set up in the node credentials.
- Invalid field names or values: If the fields used for filtering do not match the API's expected parameters, the request may return empty results or errors.
- Network issues or API downtime: Connectivity problems can cause request failures; verify network access and TeleFlow service status.
- Error messages about missing IDs: Although not applicable for "Get Many," other operations require IDs; ensure correct parameters are provided for those operations.
- Handling errors: If the node is set to continue on failure, errors will be included in the output JSON under an
errorproperty.
Links and References
- TeleFlow API Documentation (Replace with actual URL if available)