Zammad
App · 10 actions
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.
Actions
| Action | What it does |
|---|---|
| Add reply or note | Add an internal note, a note the customer can see, or an email reply that Zammad sends, to a ticket. |
| Add tag | Put a tag on a ticket. |
| Create customer | Add a customer to Zammad. |
| Create ticket | Open a ticket for a customer, with its first message. |
| Find organizations | Find the organizations customers belong to, by name or email domain. |
| Find users | Find customers and agents by name, email address, phone number or organization. |
| Get ticket | Get a ticket's details and tags, and its replies and notes if you ask. |
| Remove tag | Take a tag off a ticket. |
| Search tickets | Find tickets by words, state, group, priority, owner or customer, newest first. |
| Update ticket | Change a ticket's title, state, priority, owner or group. |
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
tickettextRequired - The ticket's ID, from a trigger or an earlier step, its link, or its number with a #, such as #31001.
- Message
bodytextRequired - What to write, as plain text or HTML.
- Type
message_typetext - 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
totext - Who the email goes to. Leave blank for the ticket's customer.Only when Type is Email reply.
- CC
cctext - Email addresses to copy, separated by commas.Only when Type is Email reply.
- Subject
subjecttext - The subject. Leave blank for the ticket's title on an email.
Outputs
bodytext- What it says, as plain text
cctext- Who an email was copied to
created_attext- When it was added (ISO 8601)
fromtext- Who wrote it
idnumber- The reply or note's ID
internaltrue/false- True when only agents can see it
linktext- A link to the ticket in Zammad
sendertext- Who it came from: Customer, Agent or System
subjecttext- Its subject
ticket_idnumber- The ticket's ID
totext- Who an email went to
typetext- What it is: email, note, phone or web
Example output
{
"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
tickettextRequired - The ticket's ID, from a trigger or an earlier step, its link, or its number with a #, such as #31001.
- Tag
tagtextRequired - The tag, such as vip.
Outputs
linktext- A link to the ticket in Zammad
tagtext- The tag added or taken off
tagslist- The ticket's tags now
ticket_idnumber- The ticket's ID
Example output
{
"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
emailtextRequired - The customer's email address.
- First name
firstnametext - Their first name.
- Last name
lastnametext - Their last name.
- Phone
phonetext - Their phone number.
- Organization
organizationtext - The organization they belong to, by its name in Zammad.
- Note
notetext - A note about them, shown to agents.
Outputs
activetrue/false- Whether they can sign in
createdtrue/false- True when made now; false when found by email
created_attext- When they were added (ISO 8601)
emailtext- Their email address
firstnametext- Their first name
idnumber- The user's ID
lastnametext- Their last name
linktext- A link to them in Zammad
nametext- Their full name
notetext- Zammad's note about them
organizationtext- Their organization, if any
phonetext- Their phone number
roleslist- Their roles, such as Customer or Agent
Example output
{
"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
titletextRequired - What the ticket is about, such as Invoice 1001 is missing.
- Group
grouptextRequired - The group the ticket goes to, such as Users or Billing.
- Customer email
customer_emailtextRequired - The customer's email address. A new address makes a new customer.
- Message
bodytextRequired - The ticket's first message, as plain text or HTML.
- Customer name
customer_nametext - The customer's full name, used only when they're new to Zammad.
- Opened by
opened_bytext - 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
statetext - The ticket's state. Leave blank for new.
- Pending till
pending_timedate and time - When a pending ticket comes back. Needed with a pending state.
- Priority
prioritytext - The ticket's priority. Leave blank for Zammad's default.
- Owner
ownertext - The agent to assign it to, or their email address. Leave blank for nobody.
- Tags
tagslist - Tags to put on the ticket.
Outputs
article_countnumber- How many replies and notes it has
created_attext- When it was opened (ISO 8601)
customertext- The customer's name
customer_emailtext- The customer's email address
customer_idnumber- The customer's ID
grouptext- The group it's in
idnumber- The ticket's ID, for other Zammad steps
linktext- A link to it in Zammad
numbertext- The ticket's number, as Zammad shows it (without the #)
organizationtext- The customer's organization, if any
ownertext- The agent it's assigned to; empty if nobody
owner_emailtext- The owner's email address
pending_timetext- When a pending ticket comes back (ISO 8601); empty if not pending
prioritytext- Its priority, such as 2 normal
statetext- Its state, such as new, open or closed
tagslist- Its tags
titletext- Its title
updated_attext- When it last changed (ISO 8601)
Example output
{
"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
querytextRequired - An organization's name or email domain.
- How many
limitnumber - The most to list. Defaults to 25.From 1 to 100.
Outputs
countnumber- How many are listed
organizationslist- The organizations found
Example output
{
"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
querytextRequired - A name, email address or phone number.
- How many
limitnumber - The most to list. Defaults to 25.From 1 to 100.
Outputs
countnumber- How many are listed
userslist- The users found
Example output
{
"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
tickettextRequired - 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_articlestrue/false - Also get every reply and note on the ticket, oldest first.Default:
false.
Outputs
article_countnumber- How many replies and notes it has
articleslist- Its replies and notes, oldest first, when asked for
created_attext- When it was opened (ISO 8601)
customertext- The customer's name
customer_emailtext- The customer's email address
customer_idnumber- The customer's ID
grouptext- The group it's in
idnumber- The ticket's ID, for other Zammad steps
linktext- A link to it in Zammad
numbertext- The ticket's number, as Zammad shows it (without the #)
organizationtext- The customer's organization, if any
ownertext- The agent it's assigned to; empty if nobody
owner_emailtext- The owner's email address
pending_timetext- When a pending ticket comes back (ISO 8601); empty if not pending
prioritytext- Its priority, such as 2 normal
statetext- Its state, such as new, open or closed
tagslist- Its tags
titletext- Its title
updated_attext- When it last changed (ISO 8601)
Example output
{
"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
tickettextRequired - The ticket's ID, from a trigger or an earlier step, its link, or its number with a #, such as #31001.
- Tag
tagtextRequired - The tag to take off.
Outputs
linktext- A link to the ticket in Zammad
tagtext- The tag added or taken off
tagslist- The ticket's tags now
ticket_idnumber- The ticket's ID
Example output
{
"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
querytext - Words to look for, such as a title, a ticket number or a customer's name. Leave blank to match every ticket.
- State
statetext - Only tickets in this state.
- Group
grouptext - Only tickets in this group.
- Priority
prioritytext - Only tickets with this priority.
- Owner
ownertext - Only tickets assigned to this agent, or their email address.
- Customer email
customer_emailtext - Only this customer's tickets.
- How many
limitnumber - The most to list. Defaults to 25.From 1 to 100.
Outputs
countnumber- How many are listed
ticketslist- The tickets found, newest first
totalnumber- How many match in all
Example output
{
"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
tickettextRequired - The ticket's ID, from a trigger or an earlier step, its link, or its number with a #, such as #31001.
- Title
titletext - A new title. Leave blank to keep it.
- State
statetext - A new state, such as open or closed. Leave blank to keep it.
- Pending till
pending_timedate and time - When a pending ticket comes back. Needed with a pending state.
- Priority
prioritytext - A new priority. Leave blank to keep it.
- Owner
ownertext - The agent to assign it to, or their email address. Leave blank to keep it.
- Group
grouptext - A group to move it to. Leave blank to keep it.
Outputs
article_countnumber- How many replies and notes it has
created_attext- When it was opened (ISO 8601)
customertext- The customer's name
customer_emailtext- The customer's email address
customer_idnumber- The customer's ID
grouptext- The group it's in
idnumber- The ticket's ID, for other Zammad steps
linktext- A link to it in Zammad
numbertext- The ticket's number, as Zammad shows it (without the #)
organizationtext- The customer's organization, if any
ownertext- The agent it's assigned to; empty if nobody
owner_emailtext- The owner's email address
pending_timetext- When a pending ticket comes back (ISO 8601); empty if not pending
prioritytext- Its priority, such as 2 normal
statetext- Its state, such as new, open or closed
tagslist- Its tags
titletext- Its title
updated_attext- When it last changed (ISO 8601)
Example output
{
"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"
}