AvantGuard - ConnectSecure icon

AvantGuard - ConnectSecure

AvantGuard - ConnectSecure
Join our community

Actions223

Overview

This node allows users to create an Application Baseline Rule by sending a POST request to the relevant API endpoint. It is useful in scenarios where you want to define or update baseline rules for applications, such as specifying which applications are denied, included, or excluded for certain companies or tags. This can help enforce security policies or compliance requirements by controlling application access or behavior.

Practical examples include:

  • Creating a rule that denies specific applications globally.
  • Including or excluding applications based on company or tag filters.
  • Setting up global or scoped baseline rules for application management.

Properties

Name Meaning
X USER ID The user identifier required for authentication or tracking purposes.
Additional Body Fields Optional JSON fields to customize the body of the POST request. Includes:
- 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 flag 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 API after creating the Application Baseline Rule. This typically includes details about the created rule such as its ID, status, and configuration. There is no indication that binary data is output by this node.

Dependencies

  • Requires an API key credential for authenticating requests to the AvantGuard ConnectSecure service.
  • Needs the base URL of the API configured in the credentials.
  • The node depends on the @avantguardllc/n8n-openapi-node package and an OpenAPI specification (openapi.json) bundled with the node.

Troubleshooting

  • Missing or invalid X USER ID: The node requires the "X USER ID" header; ensure it is provided and valid.
  • Invalid JSON in Additional Body Fields: The data field expects valid JSON; malformed JSON will cause errors.
  • API Authentication Errors: Verify that the API key credential is correctly set up and has necessary permissions.
  • Network or Endpoint Issues: Check the base URL and network connectivity to the API server.
  • Unexpected API Response: If the API returns errors, review the request payload and headers for correctness.

Links and References

Discussion