Connect Secure icon

Connect Secure

Consume Connect Secure API

Actions222

Overview

This node operation updates an existing integration rule in the Connect Secure system via its API. It is useful when you need to modify specific settings or attributes of an integration rule, such as toggling whether it is the default rule or changing other configuration data.

Practical examples include:

  • Changing which integration rule is marked as the default.
  • Updating rule parameters dynamically based on user input or workflow conditions.
  • Managing integration rules programmatically without manual intervention in the Connect Secure UI.

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 and values to update in the integration rule. Example: { "is_default": false }
Id Numeric identifier of the integration rule to update.

Output

The node outputs JSON data representing the response from the Connect Secure API after attempting to update the integration rule. This typically includes confirmation of the updated fields or error details if the update failed.

No binary data output is involved.

Dependencies

  • Requires an API key credential for authenticating with the Connect Secure API.
  • The node depends on the Connect Secure API being accessible and properly configured.
  • No additional environment variables are explicitly required beyond the API credential.

Troubleshooting

  • Common issues:

    • Invalid or missing X USER ID header causing authentication failures.
    • Incorrect or missing id property leading to failure in identifying the integration rule to update.
    • Malformed JSON in the Data property causing request body parsing errors.
    • Network connectivity issues preventing access to the Connect Secure API.
  • Error messages and resolutions:

    • 401 Unauthorized — Check that the API key credential is valid and has necessary permissions.
    • 404 Not Found — Verify that the id corresponds to an existing integration rule.
    • 400 Bad Request — Ensure the JSON in Data is correctly formatted and contains valid fields.
    • Network errors — Confirm network connectivity and API endpoint availability.

Links and References

  • Connect Secure API documentation (refer to your organization's internal API docs or vendor-provided resources).
  • n8n documentation on creating and using HTTP request nodes and custom credentials.

Discussion