TeleFlow icon

TeleFlow

Interact with TeleFlow API

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.

Practical examples include:

  • Retrieving audit details of a tenant after a configuration change.
  • Fetching tenant audit records to display in an administrative dashboard.
  • Integrating tenant audit data into reporting workflows.

Properties

Name Meaning
ID The unique identifier of the tenant audit record to retrieve. This is required.
Fields Optional key-value pairs to specify additional fields to include in the request query.

The Fields property allows adding multiple field name and value pairs to refine or customize the GET request parameters.

Output

The output is a JSON object representing the tenant audit record retrieved from the TeleFlow API. It contains all the data fields returned by the API for that specific tenant audit ID, including any metadata or audit details.

No binary data output is produced by this operation.

Example output structure (simplified):

{
  "id": "string",
  "timestamp": "string",
  "action": "string",
  "user": "string",
  "details": { /* audit-specific details */ }
}

The exact fields depend on the TeleFlow API response schema for tenant audits.

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 for the get operation. Ensure the ID is correctly set.
  • API connectivity issues: Network errors or invalid credentials will cause HTTP request failures. Verify API keys and network access.
  • Invalid field names: Providing incorrect field names in the Fields property may result in unexpected API responses or errors.
  • Continue on Fail: If enabled, the node will continue processing subsequent items even if one fails, returning error details in the output JSON.

Links and References

Discussion