AvantGuard - ConnectSecure icon

AvantGuard - ConnectSecure

AvantGuard - ConnectSecure

Actions223

Overview

This node operation allows users to create a custom ticketing template by sending a POST request with user-specific and optional additional data fields. It is useful in scenarios where an organization needs to programmatically define or update ticket templates in their ticketing system, enabling automation of ticket management workflows. For example, a support team could automate the creation of standardized ticket templates that include company lists, integrations, and detailed template information.

Properties

Name Meaning
X USER ID The User Id header value required for authentication or identification of the user making the request.
Additional Body Fields Optional JSON fields to add extra data to the request body. These can include: companies_list, integrations, and template_details.

The "Additional Body Fields" property accepts a JSON object with customizable keys and values, allowing flexible extension of the request payload.

Output

The node outputs JSON data representing the response from the ticketing system after creating the custom ticket template. This typically includes confirmation details about the created template, such as its ID, status, or any metadata returned by the API.

No binary data output is indicated.

Dependencies

  • Requires an API key credential for authenticating requests to the ticketing system.
  • The base URL for the API must be configured in the node credentials.
  • Uses HTTP headers including X-USER-ID to identify the user.
  • The node depends on an OpenAPI specification (openapi.json) bundled within the source code to build request properties and handle communication.

Troubleshooting

  • Missing or invalid X USER ID header: The API may reject requests without a valid user ID header. Ensure this field is correctly set.
  • Malformed JSON in Additional Body Fields: If the JSON provided is invalid, the request will fail. Validate JSON syntax before submission.
  • API connectivity issues: Verify that the base URL and API credentials are correct and that the API service is reachable.
  • Unexpected API errors: Check the response message for error details; ensure all required fields are included and properly formatted.

Links and References

  • Refer to your ticketing system’s API documentation for details on the expected structure of ticket templates and required authentication.
  • n8n documentation on how to configure HTTP Request nodes and use credentials for API authentication.

Discussion