Integration

Zammad integration

Zammad REST API for a self-hosted help desk: list, read, create, update and delete tickets, search tickets with the full-text query language, read and write ticket articles including replies and internal notes, manage users and organizations, list groups and run a global search. Authentication uses a personal access token sent in the Authorization header.

Connect Zammad How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in Zammad.Built from the 18 Zammad tools below, on the connection you add once.

Common Zammad use cases

syncing the agent roster
syncing companies from a CRM
reading the members of a company
sending an automated first reply
summarising a support conversation
choosing the queue for a new ticket
finding open tickets for one customer
checking the current state of a ticket
turning an alert into a support ticket
building a daily report of open tickets

What you can do with Zammad

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

Ticket, 6 operations

create_ticketCreate ticketPOSTOpens a ticket and writes its opening message.
delete_ticketDelete ticketDELETERemoves a ticket and its articles permanently.
get_ticketGet ticketGETReads one ticket by identifier.
list_ticketsList ticketsGETReturns a page of tickets.
search_ticketsSearch ticketsGETFinds tickets matching a search expression.
update_ticketUpdate ticketPUTChanges ticket attributes such as state, owner or priority, and can add a reply in the same call.

User, 4 operations

create_userCreate userPOSTAdds an agent or a customer to the help desk.
get_current_userGet current userGETReturns the profile behind the current token.
get_userGet userGETReads one user by identifier.
list_usersList usersGETReturns a page of users.

Article, 3 operations

create_ticket_articleCreate ticket articlePOSTWrites a reply or an internal note on a ticket.
get_ticket_articleGet ticket articleGETReads one message of a ticket.
list_ticket_articlesList ticket articlesGETReturns the full message history of a ticket.

Organization, 3 operations

create_organizationCreate organizationPOSTAdds a company that customers can be linked to.
get_organizationGet organizationGETReads one organization by identifier.
list_organizationsList organizationsGETReturns a page of organizations.

Group, 1 operation

list_groupsList groupsGETReturns the ticket groups of the instance.

Search, 1 operation

searchSearchGETRuns one query over every searchable object type.

Use Zammad from Claude Code, Cursor or Codex

Connect Zammad in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its Zammad operations become tools the client can call, next to every other integration you connected.

Claude Code

claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"

Codex (~/.codex/config.toml)

[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"

Cursor, Claude Desktop and other JSON configs

{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect Zammad

Create your workspace
Sign up free. Nothing to install.
Connect Zammad once
Add your Zammad connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.
Describe the job in chat
The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.

Zammad integration FAQ

What can you do with the Zammad integration?

LiveContext exposes 18 operations on Zammad, covering ticket, user, article and organization. Common uses include syncing the agent roster, syncing companies from a CRM and reading the members of a company.