Connect Secure icon

Connect Secure

Consume Connect Secure API

Actions222

Overview

This node interacts with the "Reports" resource of an API, specifically performing the "Report Settings" operation. It is designed to retrieve or manipulate settings related to reports based on user identification and report type parameters. This node is useful in scenarios where users need to programmatically access or configure report settings, such as automating report generation preferences or managing report visibility (global or user-specific).

Practical examples include:

  • Fetching configuration details for a specific report type for a given user.
  • Setting whether a report should be global or restricted to a particular user context.

Properties

Name Meaning
X USER ID The unique identifier of the user making the request. Used for authentication or scoping.
Reporttype The type of report to query or configure.
Is Global Boolean flag indicating if the report is global (true) or user-specific (false).

Output

The node outputs JSON data representing the response from the "Report Settings" API endpoint. This typically includes the settings or configuration details of the specified report type for the given user context. The exact structure depends on the API response but generally contains report metadata and configuration flags.

No binary data output is indicated by the source code.

Dependencies

  • Requires an API key credential for authenticating with the Connect Secure API.
  • Depends on the external Connect Secure API service.
  • The node uses an OpenAPI specification internally to build its properties and operations.
  • Proper configuration of the API credentials within n8n is necessary for successful execution.

Troubleshooting

  • Missing or invalid X USER ID: The node requires a valid user ID header; ensure this is provided and correctly formatted.
  • Incorrect reporttype value: Using an unsupported or misspelled report type may cause errors or empty responses.
  • Authentication failures: Ensure that the API key credential is correctly set up and has sufficient permissions.
  • Network or API errors: Check connectivity and API availability; transient issues might require retries.
  • Boolean property misconfiguration: The "Is Global" property must be a boolean; passing other types may cause unexpected behavior.

Common error messages will likely relate to authentication failures, missing required parameters, or invalid query values. Resolving these involves verifying input parameters and credential configurations.

Links and References

Discussion