Connect Secure icon

Connect Secure

Consume Connect Secure API

Actions222

Overview

This node operation, List Standard Report under the Reports resource, is designed to retrieve a list of standard reports from an external API. It allows users to specify pagination parameters and filter by whether the report is global or not. This operation is useful in scenarios where you want to programmatically access and manage reports data, such as generating dashboards, automating report retrieval for further processing, or integrating report data into other systems.

Practical examples include:

  • Fetching a paginated list of reports for display in a custom UI.
  • Automating the download or analysis of reports marked as global.
  • Integrating report metadata into a business intelligence workflow.

Properties

Name Meaning
X USER ID User Id header required for authentication or identification with the API.
Skip Number of records to skip (pagination offset).
Limit Maximum number of records to return (pagination limit).
Is Global Boolean flag indicating whether to list only global reports (true) or not (false).

Output

The output of this operation will be JSON data representing the list of standard reports retrieved from the API. Each item in the list typically contains report metadata such as report ID, name, description, creation date, and possibly other relevant fields depending on the API's response schema.

If the API supports binary data for reports (e.g., downloadable files), this node would handle it accordingly, but based on the provided code and properties, the output focuses on JSON metadata listing.

Dependencies

  • Requires an API key credential for authenticating requests to the external Connect Secure API.
  • The node depends on the external Connect Secure API endpoint that provides the reports data.
  • Proper configuration of the API credentials within n8n is necessary.
  • The X-USER-ID header must be supplied to identify the user making the request.

Troubleshooting

  • Missing or invalid X USER ID header: The API may reject requests without a valid user ID header. Ensure this property is set correctly.
  • Pagination issues: Setting skip or limit incorrectly (e.g., negative numbers) might cause errors or unexpected results.
  • API authentication errors: If the API key credential is missing or invalid, the node will fail to authenticate.
  • Network or API downtime: Connectivity issues or API service interruptions will cause the node to error out.
  • Boolean value for Is Global: Ensure this is set explicitly; omitting it or providing invalid values may lead to incorrect filtering.

Links and References

Discussion