Connect Secure icon

Connect Secure

Consume Connect Secure API

Actions222

Overview

This node allows users to create reports by sending detailed report data to an external API. It is useful in scenarios where automated report generation is needed based on dynamic input parameters such as company details, report identifiers, and filtering options. For example, a user can automate the creation of sales or financial reports for different companies by specifying the relevant report type and filters.

Properties

Name Meaning
X USER ID User identifier sent as a header to authenticate or identify the request origin.
Company Id Numeric identifier of the company for which the report is being created.
Company Name Name of the company associated with the report.
Report Id Unique string identifier for the report.
Report Name Descriptive name of the report.
Report Type Type/category of the report (e.g., sales, inventory).
File Type Desired file format of the generated report (e.g., PDF, CSV).
Is Filter Boolean flag indicating whether to apply filters to the report data.
Report Filter JSON object defining specific filter criteria to customize the report content.

Output

The node outputs JSON data representing the response from the report creation API. This typically includes confirmation details about the created report, such as its ID, status, or any metadata returned by the service. The node does not output binary data.

Dependencies

  • Requires an API key credential to authenticate requests to the external Connect Secure API.
  • Depends on the external Connect Secure API endpoint that handles report creation.
  • No additional environment variables are explicitly required beyond the API authentication setup.

Troubleshooting

  • Missing or invalid X USER ID header: Ensure the "X USER ID" property is provided and correctly set, as it is required for authentication or identification.
  • Invalid JSON in Report Filter: The "Report Filter" must be valid JSON; otherwise, parsing errors will occur. Validate JSON syntax before input.
  • API authentication failures: Verify that the API key credential is correctly configured and has sufficient permissions.
  • Incorrect property types: For example, "Company Id" must be a number; providing a string may cause request failures.
  • Empty required fields: Required properties like "X USER ID" must not be empty to avoid request rejection.

Links and References

Discussion