AvantGuard - ConnectSecure icon

AvantGuard - ConnectSecure

AvantGuard - ConnectSecure

Actions223

Overview

This node operation allows updating a tag rule by sending a PATCH request to the relevant API endpoint. It is useful in scenarios where you need to modify existing tag rules dynamically, such as updating metadata tags or adjusting tagging criteria in an automated workflow. For example, you might use this node to update the tags associated with a user or resource based on changing conditions or inputs from other nodes.

Properties

Name Meaning
X USER ID The user identifier required for authentication or tracking purposes in the request header.
Additional Body Fields Optional fields to include in the request body:
- Data: JSON object representing the tags array (e.g., {"tags": []}).
- Id: Numeric identifier of the tag rule to update.

Output

The node outputs JSON data representing the response from the API after attempting to patch the tag rule. This typically includes confirmation of the updated tag rule or error details if the update failed. There is no indication that binary data is returned.

Dependencies

  • Requires an API key credential for authenticating requests.
  • Needs the base URL of the API configured in the node credentials.
  • The node depends on the external AvantGuard ConnectSecure API service.

Troubleshooting

  • Missing or invalid X USER ID: The request will fail if the "X USER ID" header is not provided or incorrect. Ensure this value is set correctly.
  • Invalid or missing Id in body: The tag rule ID must be specified to identify which rule to update; otherwise, the API may return an error.
  • Malformed JSON in Data field: The "Data" property expects valid JSON. Invalid JSON syntax will cause parsing errors.
  • API connectivity issues: Verify network access and correct base URL configuration.
  • Authorization errors: Check that the API key credential is valid and has sufficient permissions.

Links and References

Discussion