AvantGuard - ConnectSecure icon

AvantGuard - ConnectSecure

AvantGuard - ConnectSecure

Actions223

Overview

This node operation allows users to patch update a custom ticketing template by sending partial updates to the ticket template resource. It is useful when you want to modify specific fields of an existing ticket template without replacing the entire template data. For example, updating integration settings or company lists within a ticket template can be done efficiently using this patch update operation.

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 string representing complex nested data such as companies list, integrations, and template details.
- Id Numeric identifier of the ticket template to update.

Output

The node outputs JSON data representing the response from the API after the patch update operation. This typically includes the updated ticket template information or confirmation of the successful update. There is no binary output expected from this operation.

Dependencies

  • Requires an API key credential for authenticating requests to the external ticketing service.
  • The base URL for the API must be configured in the node credentials.
  • The node uses HTTP PATCH method with JSON content type.
  • The X USER ID header must be provided for each request.

Troubleshooting

  • Missing or invalid X USER ID header: The API may reject requests if this header is missing or incorrect. Ensure it is set properly.
  • Invalid JSON in Data field: The data property expects valid JSON. Malformed JSON will cause errors. Use proper JSON formatting.
  • Incorrect Id value: The id must correspond to an existing ticket template. Using an invalid or non-existent id will result in not found or error responses.
  • API connectivity issues: Verify that the base URL and credentials are correctly configured and that the API endpoint is reachable.
  • Partial update conflicts: If the patch data conflicts with existing template constraints, the API might return validation errors.

Links and References

  • Refer to your ticketing system's API documentation for details on the ticket template patch update endpoint.
  • JSON formatting guides for constructing the data field.
  • n8n documentation on how to configure HTTP headers and body parameters in custom nodes.

Discussion