Connect Secure icon

Connect Secure

Consume Connect Secure API

Actions222

Overview

This node interacts with the "Connect Secure" API to create an Application Baseline Rule. It allows users to define baseline rules for applications by specifying various parameters such as denied applications, included or excluded companies, global scope, and tags to include or ignore. This is useful in scenarios where organizations want to enforce security policies or compliance rules on application usage within their environment.

Practical examples:

  • Creating a rule that denies certain applications across the company.
  • Defining baseline rules that apply only to specific companies or tags.
  • Setting global rules that affect all users and applications.

Properties

Name Meaning
X USER ID User Id header value required for authentication or identification in the API request headers.
Data JSON object containing the rule details:
- denied_applications: List of applications to deny (array).
- include_company: List of companies to include (array).
- exclude_company: List of companies to exclude (array).
- is_global: Boolean indicating if the rule applies globally.
- ignore_tags: List of tags to ignore (array).
- include_tags: List of tags to include (array).

Output

The node outputs JSON data representing the response from the Connect Secure API after creating the Application Baseline Rule. The exact structure depends on the API but typically includes confirmation of the created rule, its ID, status, and any relevant metadata.

No binary data output is indicated.

Dependencies

  • Requires an API key credential for authenticating with the Connect Secure API.
  • The node uses the bundled OpenAPI specification (openapi.json) to build properties and handle requests.
  • No additional external dependencies beyond the API and n8n's HTTP capabilities.

Troubleshooting

  • Missing or invalid X USER ID: The API requires a valid user ID header; ensure this is provided and correct.
  • Malformed JSON in Data property: The data field must be valid JSON; errors parsing it will cause failures.
  • API authentication errors: Verify that the API key credential is correctly configured and has necessary permissions.
  • Network or connectivity issues: Ensure n8n can reach the Connect Secure API endpoint.
  • Unexpected API responses: Check the API documentation for error codes and messages returned by the service.

Links and References

  • Connect Secure API documentation (refer to your organization's API docs).
  • n8n documentation on creating custom nodes and using API credentials.
  • JSON formatting guides for preparing the data property payload.

Discussion