AvantGuard - ConnectSecure icon

AvantGuard - ConnectSecure

AvantGuard - ConnectSecure

Actions223

Overview

This node allows updating credentials by sending a PATCH request to an external API. It is designed to modify specific fields of a credential resource, such as toggling exclusion status or updating the credential's ID. This operation is useful when you need to programmatically update credential details without recreating them from scratch.

Common scenarios include:

  • Updating user-specific credential flags (e.g., marking a credential as excluded).
  • Changing metadata associated with a credential.
  • Automating credential management workflows where partial updates are required.

Example: You might use this node to mark a credential as excluded (is_excluded: true) for a particular user by providing their user ID and the updated data in the request body.

Properties

Name Meaning
X USER ID The User ID header value to identify the user making the request.
Additional Body Fields Optional additional fields to include in the PATCH request body:
data (JSON) - JSON object representing data to update, e.g., { "is_excluded": false }.
id (number) - Numeric identifier of the credential to update.

Output

The node outputs the JSON response returned by the PATCH request to the API. This typically contains the updated credential information reflecting the changes made.

If the API supports binary data output, it would be handled accordingly, but based on the provided code and properties, the output is expected to be purely JSON.

Dependencies

  • Requires an API key credential for authentication to the external service.
  • The base URL for the API must be configured in the node credentials.
  • The node uses HTTP PATCH method with JSON content type.
  • No other external dependencies are indicated in the source code.

Troubleshooting

  • Missing or invalid X USER ID header: The API may reject requests without a valid user ID header. Ensure the "X USER ID" property is set correctly.
  • Invalid JSON in data field: If the JSON string in the data property is malformed, the request will fail. Validate JSON syntax before running.
  • Credential ID missing or incorrect: The id field is necessary to specify which credential to update. Omitting or providing an incorrect ID may cause errors or no effect.
  • API authentication errors: Ensure that the API key credential is properly configured and has sufficient permissions.
  • Network or connectivity issues: Verify network access to the API endpoint.

Links and References

  • Refer to the external API documentation for the PATCH /credentials endpoint for detailed schema and behavior.
  • JSON validation tools can help ensure correct formatting of the data field.
  • n8n documentation on HTTP Request nodes and custom node development for further customization.

Discussion