AvantGuard - ConnectSecure icon

AvantGuard - ConnectSecure

AvantGuard - ConnectSecure

Actions223

Overview

This node performs a patch update operation on Backup Software configurations or data. It allows users to send partial updates to the backup software system by specifying certain fields that need modification. This is useful in scenarios where you want to update specific attributes of a backup configuration without replacing the entire object.

For example, you might want to toggle a regex flag or exclude certain files from backup by sending only those changes rather than resubmitting the full backup configuration.

Properties

Name Meaning
X USER ID The user identifier required for authentication or tracking purposes in the request header.
Additional Body Fields Optional additional fields to include in the request body:
- Data JSON object with properties such as regex (boolean) and exculde (boolean).
- Id Numeric identifier representing the specific backup software entity to update.

The "Additional Body Fields" property allows flexible inclusion of extra parameters in the PATCH request body, enabling customization of the update payload.

Output

The node outputs JSON data representing the response from the backup software API after applying the patch update. This typically includes confirmation of updated fields or the current state of the patched resource.

No binary data output is indicated.

Dependencies

  • Requires an API key credential for authenticating requests to the backup software service.
  • The base URL for the API is configured via credentials.
  • Uses HTTP PATCH method with JSON content type.
  • Depends on the @avantguardllc/n8n-openapi-node package for building request properties from OpenAPI specifications.

Troubleshooting

  • Missing or invalid X USER ID: The node requires a valid user ID header; ensure this is provided and correctly formatted.
  • Invalid JSON in 'Data' field: The data field expects valid JSON; malformed JSON will cause errors.
  • Incorrect 'Id' value: The numeric ID must correspond to an existing backup software entity; otherwise, the API may return not found or validation errors.
  • API connectivity issues: Verify the base URL and API credentials are correct and the service is reachable.
  • Permission errors: Ensure the API key has sufficient permissions to perform patch updates.

Links and References

Discussion