Connect Secure icon

Connect Secure

Consume Connect Secure API

Actions222

Overview

This node interacts with the Connect Secure API to update an existing Event Set. It allows users to modify properties of an Event Set such as alert rules and default status by sending updated data to the API. This is useful in scenarios where event configurations need to be programmatically adjusted, for example, updating alerting criteria or toggling whether an Event Set is the default one.

Practical examples include:

  • Automating updates to monitoring or alerting configurations based on external triggers.
  • Integrating event set management into larger workflows that adjust system behavior dynamically.

Properties

Name Meaning
X USER ID The user identifier required for authentication or tracking purposes in the API request.
Data JSON object containing the fields to update in the Event Set. Common fields include alert_rules (an array) and is_default (boolean).
Id Numeric identifier of the Event Set to update.

Output

The node outputs the JSON response returned by the Connect Secure API after attempting to update the Event Set. This typically includes the updated Event Set details or confirmation of the update operation.

If the API returns binary data (not indicated here), it would represent raw content related to the Event Set, but this node primarily deals with JSON data.

Dependencies

  • Requires an active connection to the Connect Secure API.
  • Needs an API key or token credential configured in n8n for authentication.
  • The node depends on the @devlikeapro/n8n-openapi-node package and a local OpenAPI specification (openapi.json) to define its operations.

Troubleshooting

  • Missing or invalid X USER ID: The API may reject requests without a valid user ID header. Ensure the "X USER ID" property is correctly set.
  • Invalid JSON in Data field: The "Data" property expects valid JSON. Malformed JSON will cause parsing errors.
  • Incorrect Event Set Id: Providing an invalid or non-existent Event Set ID will result in API errors indicating the resource was not found.
  • Authentication errors: If the API key or token is missing or expired, the node will fail to authenticate.
  • Network issues: Connectivity problems can cause timeouts or failed requests.

To resolve these:

  • Double-check all input values for correctness.
  • Validate JSON syntax before running the node.
  • Confirm API credentials are properly configured and have necessary permissions.
  • Verify network connectivity to the API endpoint.

Links and References

Discussion