AvantGuard - ConnectSecure icon

AvantGuard - ConnectSecure

AvantGuard - ConnectSecure

Actions223

Overview

This node is designed to update integration credentials by sending a PATCH request to an external service. It allows users to modify specific fields of an existing integration credential, such as the user ID and additional optional data. This node is useful in scenarios where integration credentials need to be updated dynamically within an automation workflow, for example, updating access tokens or metadata associated with an integration.

Practical examples include:

  • Updating the credential information for a third-party API integration when user permissions change.
  • Modifying metadata or configuration details related to an integration credential without recreating it.
  • Automating the maintenance of integration credentials based on external triggers or events.

Properties

Name Meaning
X USER ID The User ID header value required for authentication or identification in the request.
Additional Body Fields Optional fields to include in the request body:
- Data: JSON object with arbitrary data.
- Id: Numeric identifier of the integration credential to update.

Output

The node outputs JSON data representing the response from the PATCH update operation on the integration credential. This typically includes confirmation of the update, the updated credential details, or error information if the update failed.

If the node supports binary data output (not evident from the provided code), it would represent any file or binary content returned by the API, but this is not indicated here.

Dependencies

  • Requires an API key or authentication token configured in the node's credentials to authorize requests to the external service.
  • Depends on the base URL and headers set in the node's configuration to correctly target the API endpoint.
  • Uses an OpenAPI-based properties builder internally to define its parameters and request structure.

Troubleshooting

  • Missing or invalid X USER ID: The node requires a valid "X USER ID" header; ensure this is provided and correct to avoid authentication errors.
  • Invalid JSON in Data field: The "Data" property expects valid JSON; malformed JSON will cause parsing errors.
  • Incorrect Id value: The "Id" must correspond to an existing integration credential; using an invalid or non-existent Id will result in update failures.
  • API connectivity issues: Verify network connectivity and that the base URL is correctly configured.
  • Authentication failures: Ensure the API key or authentication token is valid and has sufficient permissions.

Links and References

  • Refer to the external API documentation for the integration service to understand the expected request format and response structure.
  • n8n documentation on HTTP Request node for general guidance on making authenticated API calls.
  • JSON validation tools to verify the correctness of the "Data" input field.

Discussion