Connect Secure icon

Connect Secure

Consume Connect Secure API

Actions222

Overview

This node operation updates an existing Application Baseline Rule by sending new configuration data to the Connect Secure API. It is useful for managing security policies related to application usage within an organization, such as specifying which applications are denied, included, or excluded for certain companies or tags. For example, a security administrator can update baseline rules to block unauthorized applications globally or for specific company groups.

Properties

Name Meaning
X USER ID The user identifier required for authentication or tracking purposes in the API request header.
Data JSON object containing the rule details to update, including:
- 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).
Id Numeric identifier of the Application Baseline Rule to update.

Output

The node outputs the response from the API call in the json field of the output item. This typically contains the updated Application Baseline Rule data or confirmation of the update operation. There is no indication that binary data is returned.

Dependencies

  • Requires an API key credential for authenticating with the Connect Secure API.
  • The node depends on the external Connect Secure API endpoint to perform the update operation.
  • Proper configuration of the API credentials and network access to the API service is necessary.

Troubleshooting

  • Common issues:
    • Missing or invalid X USER ID header may cause authentication errors.
    • Incorrect or malformed JSON in the Data property can lead to request failures.
    • Providing an invalid or non-existent Id will result in the API not finding the rule to update.
  • Error messages:
    • Authentication errors usually indicate missing or incorrect user ID or API credentials.
    • Validation errors from the API may point to incorrect data structure or types in the Data JSON.
    • Network or connectivity errors suggest issues reaching the Connect Secure API endpoint.

Links and References

  • Connect Secure API documentation (refer to your organization's API docs for detailed schema and examples).
  • n8n documentation on creating and using custom nodes with API integrations.

Discussion