AvantGuard - ConnectSecure icon

AvantGuard - ConnectSecure

AvantGuard - ConnectSecure

Actions223

Overview

This node operation allows updating an existing Tag by sending a PATCH request with specified fields. It is useful when you want to modify certain attributes of a Tag without replacing the entire resource. Typical use cases include updating metadata or properties of tags in a system that supports tagging, such as categorizing items, labeling content, or managing organizational data.

For example, you might update a tag's name or associated data fields dynamically based on workflow conditions.

Properties

Name Meaning
X USER ID The user identifier required for authentication or tracking purposes in the API request.
Additional Body Fields Optional fields to include in the request body:
- Data JSON object containing additional data to update within the tag.
- Id Numeric identifier of the tag to be updated.

Output

The node outputs JSON data representing the response from the API after the patch update operation. This typically includes the updated tag details reflecting the changes made. There is no indication of binary data output.

Dependencies

  • Requires an API key credential for authenticating requests.
  • Needs the base URL of the target API configured in credentials.
  • Depends on the external AvantGuard ConnectSecure API service (as inferred from bundled code naming).
  • The node sends HTTP PATCH requests with appropriate headers and body constructed from input parameters.

Troubleshooting

  • Missing or invalid X USER ID: The API may reject requests if the user ID header is missing or incorrect. Ensure this field is provided and valid.
  • Invalid JSON in Data field: If the "Data" property contains malformed JSON, the request will fail. Validate JSON syntax before execution.
  • Tag ID not found or invalid: Providing an incorrect tag ID will result in errors or no updates. Confirm the tag exists and the ID is correct.
  • API connectivity issues: Network problems or incorrect base URL configuration can cause failures. Verify API endpoint accessibility.
  • Authentication errors: Ensure the API key credential is correctly set up and has necessary permissions.

Links and References

  • HTTP PATCH Method
  • JSON Syntax
  • Documentation for the specific API being used (not provided here) would be essential for detailed field descriptions and error codes.

Discussion