# Zammad

> Run your Zammad help desk from workflows: open tickets from forms, emails and alerts, reply or add notes, change state, priority, owner and group, tag tickets, and find tickets, customers and organizations. Start a workflow when a ticket is created or changes.

App · 10 actions. Web page: https://docs.lodol.com/docs/integrations/zammad

## Actions

### Add reply or note

Add an internal note, a note the customer can see, or an email reply that Zammad sends, to a ticket.

**Inputs**

- Ticket (`ticket`, text, required): The ticket's ID, from a trigger or an earlier step, its link, or its number with a #, such as #31001.
- Message (`body`, text, required): What to write, as plain text or HTML.
- Type (`message_type`, text): An internal note is seen only by agents; a public note shows in the customer's portal; an email reply is sent. One of: `internal_note` (Internal note), `public_note` (Public note), `email_reply` (Email reply). Default: `internal_note`.
- To (`to`, text): Who the email goes to. Leave blank for the ticket's customer. Only when Type is Email reply.
- CC (`cc`, text): Email addresses to copy, separated by commas. Only when Type is Email reply.
- Subject (`subject`, text): The subject. Leave blank for the ticket's title on an email.

**Outputs**

- `body` (text): What it says, as plain text
- `cc` (text): Who an email was copied to
- `created_at` (text): When it was added (ISO 8601)
- `from` (text): Who wrote it
- `id` (number): The reply or note's ID
- `internal` (true/false): True when only agents can see it
- `link` (text): A link to the ticket in Zammad
- `sender` (text): Who it came from: Customer, Agent or System
- `subject` (text): Its subject
- `ticket_id` (number): The ticket's ID
- `to` (text): Who an email went to
- `type` (text): What it is: email, note, phone or web

**Example output**

```json
{
  "body": "Here it is again. Sorry it went missing.",
  "cc": "",
  "created_at": "2026-11-04T09:12:44.233Z",
  "from": "Sam Agent via Billing <billing@yourcompany.com>",
  "id": 1094,
  "internal": false,
  "link": "https://yourcompany.zammad.com/#ticket/zoom/412",
  "sender": "Agent",
  "subject": "Invoice 1001 is missing",
  "ticket_id": 412,
  "to": "jane@acme.example.com",
  "type": "email"
}
```

### Add tag

Put a tag on a ticket. A new tag is made as it's used.

**Inputs**

- Ticket (`ticket`, text, required): The ticket's ID, from a trigger or an earlier step, its link, or its number with a #, such as #31001.
- Tag (`tag`, text, required): The tag, such as vip.

**Outputs**

- `link` (text): A link to the ticket in Zammad
- `tag` (text): The tag added or taken off
- `tags` (list): The ticket's tags now
- `ticket_id` (number): The ticket's ID

**Example output**

```json
{
  "link": "https://yourcompany.zammad.com/#ticket/zoom/412",
  "tag": "invoice",
  "tags": [
    "billing",
    "invoice"
  ],
  "ticket_id": 412
}
```

### Create customer

Add a customer to Zammad. If someone already has the email address, they're returned instead, unchanged.

**Inputs**

- Email (`email`, text, required): The customer's email address.
- First name (`firstname`, text): Their first name.
- Last name (`lastname`, text): Their last name.
- Phone (`phone`, text): Their phone number.
- Organization (`organization`, text): The organization they belong to, by its name in Zammad.
- Note (`note`, text): A note about them, shown to agents.

**Outputs**

- `active` (true/false): Whether they can sign in
- `created` (true/false): True when made now; false when found by email
- `created_at` (text): When they were added (ISO 8601)
- `email` (text): Their email address
- `firstname` (text): Their first name
- `id` (number): The user's ID
- `lastname` (text): Their last name
- `link` (text): A link to them in Zammad
- `name` (text): Their full name
- `note` (text): Zammad's note about them
- `organization` (text): Their organization, if any
- `phone` (text): Their phone number
- `roles` (list): Their roles, such as Customer or Agent

**Example output**

```json
{
  "active": true,
  "created": true,
  "created_at": "2026-10-01T08:00:00.000Z",
  "email": "jane@acme.example.com",
  "firstname": "Jane",
  "id": 57,
  "lastname": "Customer",
  "link": "https://yourcompany.zammad.com/#user/profile/57",
  "name": "Jane Customer",
  "note": "",
  "organization": "Acme Corp",
  "phone": "+1 555 0100",
  "roles": [
    "Customer"
  ]
}
```

### Create ticket

Open a ticket for a customer, with its first message. The customer is found by email, or made if they're new.

**Inputs**

- Title (`title`, text, required): What the ticket is about, such as Invoice 1001 is missing.
- Group (`group`, text, required): The group the ticket goes to, such as Users or Billing.
- Customer email (`customer_email`, text, required): The customer's email address. A new address makes a new customer.
- Message (`body`, text, required): The ticket's first message, as plain text or HTML.
- Customer name (`customer_name`, text): The customer's full name, used only when they're new to Zammad.
- Opened by (`opened_by`, text): How the ticket started. An email to the customer is sent by Zammad from the group's address. One of: `customer_message` (A message from the customer), `phone_call` (A phone call from the customer), `email_to_customer` (An email to the customer). Default: `customer_message`.
- State (`state`, text): The ticket's state. Leave blank for new.
- Pending till (`pending_time`, date and time): When a pending ticket comes back. Needed with a pending state.
- Priority (`priority`, text): The ticket's priority. Leave blank for Zammad's default.
- Owner (`owner`, text): The agent to assign it to, or their email address. Leave blank for nobody.
- Tags (`tags`, list): Tags to put on the ticket.

**Outputs**

- `article_count` (number): How many replies and notes it has
- `created_at` (text): When it was opened (ISO 8601)
- `customer` (text): The customer's name
- `customer_email` (text): The customer's email address
- `customer_id` (number): The customer's ID
- `group` (text): The group it's in
- `id` (number): The ticket's ID, for other Zammad steps
- `link` (text): A link to it in Zammad
- `number` (text): The ticket's number, as Zammad shows it (without the #)
- `organization` (text): The customer's organization, if any
- `owner` (text): The agent it's assigned to; empty if nobody
- `owner_email` (text): The owner's email address
- `pending_time` (text): When a pending ticket comes back (ISO 8601); empty if not pending
- `priority` (text): Its priority, such as 2 normal
- `state` (text): Its state, such as new, open or closed
- `tags` (list): Its tags
- `title` (text): Its title
- `updated_at` (text): When it last changed (ISO 8601)

**Example output**

```json
{
  "article_count": 2,
  "created_at": "2026-11-04T09:12:44.120Z",
  "customer": "Jane Customer",
  "customer_email": "jane@acme.example.com",
  "customer_id": 57,
  "group": "Billing",
  "id": 412,
  "link": "https://yourcompany.zammad.com/#ticket/zoom/412",
  "number": "31412",
  "organization": "Acme Corp",
  "owner": "Sam Agent",
  "owner_email": "sam@yourcompany.com",
  "pending_time": "",
  "priority": "2 normal",
  "state": "open",
  "tags": [
    "billing",
    "invoice"
  ],
  "title": "Invoice 1001 is missing",
  "updated_at": "2026-11-04T10:02:13.501Z"
}
```

### Find organizations

Find the organizations customers belong to, by name or email domain.

**Inputs**

- Search for (`query`, text, required): An organization's name or email domain.
- How many (`limit`, number): The most to list. Defaults to 25. From 1 to 100.

**Outputs**

- `count` (number): How many are listed
- `organizations` (list): The organizations found

**Example output**

```json
{
  "count": 1,
  "organizations": [
    {
      "active": true,
      "domain": "acme.example.com",
      "id": 9,
      "link": "https://yourcompany.zammad.com/#organization/profile/9",
      "member_count": 14,
      "name": "Acme Corp",
      "note": "",
      "vip": false
    }
  ]
}
```

### Find users

Find customers and agents by name, email address, phone number or organization.

**Inputs**

- Search for (`query`, text, required): A name, email address or phone number.
- How many (`limit`, number): The most to list. Defaults to 25. From 1 to 100.

**Outputs**

- `count` (number): How many are listed
- `users` (list): The users found

**Example output**

```json
{
  "count": 1,
  "users": [
    {
      "active": true,
      "created_at": "2026-10-01T08:00:00.000Z",
      "email": "jane@acme.example.com",
      "firstname": "Jane",
      "id": 57,
      "lastname": "Customer",
      "link": "https://yourcompany.zammad.com/#user/profile/57",
      "name": "Jane Customer",
      "note": "",
      "organization": "Acme Corp",
      "phone": "+1 555 0100",
      "roles": [
        "Customer"
      ]
    }
  ]
}
```

### Get ticket

Get a ticket's details and tags, and its replies and notes if you ask.

**Inputs**

- Ticket (`ticket`, text, required): The ticket's ID, from a trigger or an earlier step, its link, or its number with a #, such as #31001.
- Include replies and notes (`include_articles`, true/false): Also get every reply and note on the ticket, oldest first. Default: `false`.

**Outputs**

- `article_count` (number): How many replies and notes it has
- `articles` (list): Its replies and notes, oldest first, when asked for
- `created_at` (text): When it was opened (ISO 8601)
- `customer` (text): The customer's name
- `customer_email` (text): The customer's email address
- `customer_id` (number): The customer's ID
- `group` (text): The group it's in
- `id` (number): The ticket's ID, for other Zammad steps
- `link` (text): A link to it in Zammad
- `number` (text): The ticket's number, as Zammad shows it (without the #)
- `organization` (text): The customer's organization, if any
- `owner` (text): The agent it's assigned to; empty if nobody
- `owner_email` (text): The owner's email address
- `pending_time` (text): When a pending ticket comes back (ISO 8601); empty if not pending
- `priority` (text): Its priority, such as 2 normal
- `state` (text): Its state, such as new, open or closed
- `tags` (list): Its tags
- `title` (text): Its title
- `updated_at` (text): When it last changed (ISO 8601)

**Example output**

```json
{
  "article_count": 2,
  "articles": [
    {
      "body": "Can you send invoice 1001 again? It never arrived.",
      "cc": "",
      "created_at": "2026-11-04T09:12:44.233Z",
      "from": "Jane Customer <jane@acme.example.com>",
      "id": 1093,
      "internal": false,
      "sender": "Customer",
      "subject": "Invoice 1001 is missing",
      "to": "",
      "type": "web"
    }
  ],
  "created_at": "2026-11-04T09:12:44.120Z",
  "customer": "Jane Customer",
  "customer_email": "jane@acme.example.com",
  "customer_id": 57,
  "group": "Billing",
  "id": 412,
  "link": "https://yourcompany.zammad.com/#ticket/zoom/412",
  "number": "31412",
  "organization": "Acme Corp",
  "owner": "Sam Agent",
  "owner_email": "sam@yourcompany.com",
  "pending_time": "",
  "priority": "2 normal",
  "state": "open",
  "tags": [
    "billing",
    "invoice"
  ],
  "title": "Invoice 1001 is missing",
  "updated_at": "2026-11-04T10:02:13.501Z"
}
```

### Remove tag

Take a tag off a ticket.

**Inputs**

- Ticket (`ticket`, text, required): The ticket's ID, from a trigger or an earlier step, its link, or its number with a #, such as #31001.
- Tag (`tag`, text, required): The tag to take off.

**Outputs**

- `link` (text): A link to the ticket in Zammad
- `tag` (text): The tag added or taken off
- `tags` (list): The ticket's tags now
- `ticket_id` (number): The ticket's ID

**Example output**

```json
{
  "link": "https://yourcompany.zammad.com/#ticket/zoom/412",
  "tag": "invoice",
  "tags": [
    "billing"
  ],
  "ticket_id": 412
}
```

### Search tickets

Find tickets by words, state, group, priority, owner or customer, newest first.

**Inputs**

- Words (`query`, text): Words to look for, such as a title, a ticket number or a customer's name. Leave blank to match every ticket.
- State (`state`, text): Only tickets in this state.
- Group (`group`, text): Only tickets in this group.
- Priority (`priority`, text): Only tickets with this priority.
- Owner (`owner`, text): Only tickets assigned to this agent, or their email address.
- Customer email (`customer_email`, text): Only this customer's tickets.
- How many (`limit`, number): The most to list. Defaults to 25. From 1 to 100.

**Outputs**

- `count` (number): How many are listed
- `tickets` (list): The tickets found, newest first
- `total` (number): How many match in all

**Example output**

```json
{
  "count": 1,
  "tickets": [
    {
      "article_count": 2,
      "created_at": "2026-11-04T09:12:44.120Z",
      "customer": "Jane Customer",
      "customer_email": "jane@acme.example.com",
      "customer_id": 57,
      "group": "Billing",
      "id": 412,
      "link": "https://yourcompany.zammad.com/#ticket/zoom/412",
      "number": "31412",
      "organization": "Acme Corp",
      "owner": "Sam Agent",
      "owner_email": "sam@yourcompany.com",
      "pending_time": "",
      "priority": "2 normal",
      "state": "open",
      "title": "Invoice 1001 is missing",
      "updated_at": "2026-11-04T10:02:13.501Z"
    }
  ],
  "total": 1
}
```

### Update ticket

Change a ticket's title, state, priority, owner or group. Blank fields stay as they are.

**Inputs**

- Ticket (`ticket`, text, required): The ticket's ID, from a trigger or an earlier step, its link, or its number with a #, such as #31001.
- Title (`title`, text): A new title. Leave blank to keep it.
- State (`state`, text): A new state, such as open or closed. Leave blank to keep it.
- Pending till (`pending_time`, date and time): When a pending ticket comes back. Needed with a pending state.
- Priority (`priority`, text): A new priority. Leave blank to keep it.
- Owner (`owner`, text): The agent to assign it to, or their email address. Leave blank to keep it.
- Group (`group`, text): A group to move it to. Leave blank to keep it.

**Outputs**

- `article_count` (number): How many replies and notes it has
- `created_at` (text): When it was opened (ISO 8601)
- `customer` (text): The customer's name
- `customer_email` (text): The customer's email address
- `customer_id` (number): The customer's ID
- `group` (text): The group it's in
- `id` (number): The ticket's ID, for other Zammad steps
- `link` (text): A link to it in Zammad
- `number` (text): The ticket's number, as Zammad shows it (without the #)
- `organization` (text): The customer's organization, if any
- `owner` (text): The agent it's assigned to; empty if nobody
- `owner_email` (text): The owner's email address
- `pending_time` (text): When a pending ticket comes back (ISO 8601); empty if not pending
- `priority` (text): Its priority, such as 2 normal
- `state` (text): Its state, such as new, open or closed
- `tags` (list): Its tags
- `title` (text): Its title
- `updated_at` (text): When it last changed (ISO 8601)

**Example output**

```json
{
  "article_count": 2,
  "created_at": "2026-11-04T09:12:44.120Z",
  "customer": "Jane Customer",
  "customer_email": "jane@acme.example.com",
  "customer_id": 57,
  "group": "Billing",
  "id": 412,
  "link": "https://yourcompany.zammad.com/#ticket/zoom/412",
  "number": "31412",
  "organization": "Acme Corp",
  "owner": "Sam Agent",
  "owner_email": "sam@yourcompany.com",
  "pending_time": "",
  "priority": "2 normal",
  "state": "open",
  "tags": [
    "billing",
    "invoice"
  ],
  "title": "Invoice 1001 is missing",
  "updated_at": "2026-11-04T10:02:13.501Z"
}
```
