Connect Secure icon

Connect Secure

Consume Connect Secure API

Actions222

Overview

This node interacts with the Connect Secure API to update credential information. It is designed to send an update request for a specific credential identified by its ID, allowing users to modify properties such as exclusion status or other metadata associated with that credential.

Common scenarios include:

  • Updating user credentials in a secure system.
  • Changing flags or attributes related to credentials without needing to recreate them.
  • Automating credential management workflows where credential properties need to be programmatically adjusted.

For example, a user might use this node to mark a credential as excluded from certain processes by setting the is_excluded flag to true.

Properties

Name Meaning
X USER ID The User Id header value sent with the request to identify the user making the update.
Data JSON object containing the fields to update on the credential. Example: { "is_excluded": false }.
Id Numeric identifier of the credential to update.

Output

The node outputs the response from the Connect Secure API after attempting to update the credential. This output is structured as JSON and typically contains the updated credential data or confirmation of the update operation.

If the API supports binary data responses (not indicated here), it would be included accordingly, but based on the provided code and properties, the output is JSON only.

Dependencies

  • Requires an active connection to the Connect Secure API.
  • Needs an API authentication token or key configured in n8n credentials (referred generically as an API key credential).
  • The node uses HTTP headers, including a custom X-USER-ID header, which must be supplied.
  • The node depends on the @devlikeapro/n8n-openapi-node package and the OpenAPI specification (openapi.json) for building its operations.

Troubleshooting

  • Missing or invalid X USER ID: The API may reject requests if the user ID header is missing or incorrect. Ensure this property is set correctly.
  • Invalid credential ID: If the Id does not correspond to an existing credential, the API will likely return an error indicating the resource was not found.
  • Malformed JSON in Data: The Data property expects valid JSON. Invalid JSON syntax will cause parsing errors before sending the request.
  • Authentication errors: If the API key or authentication token is missing or expired, the API will reject the request.
  • Network issues: Connectivity problems can prevent the node from reaching the API endpoint.

To resolve these issues:

  • Verify all required properties are correctly filled.
  • Confirm the API credentials are valid and have necessary permissions.
  • Validate JSON syntax in the Data field.
  • Check network connectivity and API endpoint availability.

Links and References

Discussion