Zammad icon

Zammad

Consume Zammad REST API

Actions57

Ticket → Create

AI-generated

Overview

This node integrates with the Zammad REST API to create tickets. It allows users to create a new ticket by specifying required fields such as group, title, customer ID, and the body of the article associated with the ticket. Additional optional fields for both the ticket and the article can be provided to customize the ticket further. This node is useful in customer support workflows where automated ticket creation is needed based on incoming data or events.

Use Case Examples

  1. Automatically create a support ticket when a customer submits a form, including details like group, title, and customer ID.
  2. Create a ticket with an initial article body describing the issue, and optionally set priority, state, and owner information.
  3. Add custom fields to tickets for specialized tracking or integration with other systems.

Properties

Name Meaning
Authentication The authentication method to use for connecting to the Zammad API. Options include Basic Authentication, OAuth2, and Token Authentication.
API The API to use for the operation, either REST API or CTI API.
Group The group to which the ticket belongs. This is a required field for ticket creation.
Title The title of the ticket. This is a required field for ticket creation.
Customer ID The ID of the customer for whom the ticket is created. This is a required field.
Additional Fields Optional additional fields for the ticket such as customer email, group ID, priority ID, state ID, owner ID, notes, various timestamps, ticket type, and time unit.
Article Body The body content of the initial article associated with the ticket. This is a required field.
Article Additional Fields Optional additional fields for the article such as recipient, cc, reply-to, message ID, subject, content type, type, internal flag, and time unit.
Custom Fields Allows adding custom fields with name and value pairs to extend the ticket data.

Output

JSON

  • id - The unique identifier of the created ticket.
  • group - The group associated with the ticket.
  • title - The title of the ticket.
  • customer_id - The ID of the customer for whom the ticket was created.
  • article
    • body - The body content of the initial article associated with the ticket.
    • to - The recipient of the article.
    • cc - CC recipients of the article.
    • reply_to - Reply-to information of the article.
    • in_reply_to - Reference to what this article is replying to.
    • message_id - Message ID of the article.
    • subject - Subject of the article.
    • content_type - Content type of the article.
    • type - Type of the article.
    • internal - Flag indicating if the article is internal.

Dependencies

  • Zammad REST API

Troubleshooting

  • Ensure that the required fields (group, title, customer ID, and article body) are provided; missing these will cause API errors.
  • Verify that the authentication credentials (Basic Auth, OAuth2, or Token) are correctly configured and valid.
  • Check API endpoint availability and network connectivity to avoid request failures.
  • When using custom fields, ensure the field names match those expected by the Zammad API to prevent errors.

Links

  • Zammad API Documentation - Official documentation for the Zammad REST API, including ticket creation endpoints and field descriptions.

Discussion