Zammad ServiceNow integration: two-way sync without scripts
Without integration, teams enter the same issue in Zammad and ServiceNow and chase each other for status.
Zammad 
ServiceNow Tickets are handled in Zammad while the wider IT team works incidents in ServiceNow. The two records drift: the same issue is entered twice, and updates and files have to be copied across and chased by hand.
ZigiOps creates a ServiceNow incident for each Zammad ticket you select and links the two with correlation fields. Updates and attachments are written back to the Zammad ticket, so both teams work from the same facts.
What manual work disappears
- Entering the same issue twice, once in Zammad and once in ServiceNow
- Chasing the service desk for status
- Copying comments and attachments between the two tools
- Translating states and priorities by hand
- Updating the ticket when the incident is resolved
What does this handoff cost you?
A quick estimate for this integration.
Illustrative estimate based on your inputs. Not a guaranteed cash saving. Actual results depend on workflow design and volume.
How the Zammad ↔ ServiceNow mapping works inside ZigiOps
A look at the visual field-mapping canvas ZigiOps engineers use to configure this pair — point, click, connect. No scripts, no pipelines.
Zammad 
ServiceNow Per field, not per record — if only the priority changed on one side, only that field is resolved, not the whole ticket.
Lock specific fields (e.g. Priority) to always defer to one system, regardless of which side changed last.
Route simultaneous conflicting edits to a review queue instead of silently picking a winner, when that's the safer default.
Zammad connector ServiceNow connector Every field that matters, mapped both ways
Map Zammad entities to ServiceNow entities down to the individual field, without writing a script.
More control over how Zammad ↔ ServiceNow syncs
Set how often ZigiOps checks for new and updated records, or trigger an action by hand with Run.
Pick up only what you need — for example tickets created or updated since the last run, or tickets matching a field value.
Each Zammad ticket is linked to its ServiceNow incident through correlation fields, so ZigiOps always knows which record belongs to which.
Map ticket fields to ServiceNow fields, including custom fields, by choosing them from a list — no code.
File content and file name are mapped, so files added on one side appear on the other automatically.
The Troubleshooting view shows every run, its result and how long it took, so failures are easy to spot.
A helpdesk ticket, escalated to the service desk
A ticket raised in Zammad needs the IT service desk. ZigiOps keeps the Zammad ticket and the ServiceNow incident on one shared thread.
The helpdesk logs a ticket with the customer and details.
A matching ServiceNow incident is created and linked to the ticket through correlation fields.
State changes, comments and attachments on the incident sync back to the ticket.
When the incident is resolved, the Zammad ticket reflects the outcome without manual updates.
Zammad ↔ ServiceNow FAQ
Is the Zammad–ServiceNow sync two-way?
Yes. A Zammad ticket creates a ServiceNow incident, and updates and attachments made in ServiceNow are written back to the matching Zammad ticket. Correlation fields link each pair of records.
What fields map between Zammad and ServiceNow?
Ticket ↔ incident, title ↔ short description, state ↔ state, priority ↔ priority, articles ↔ comments, and attachments ↔ attachments. Mappings are configured point and click in the field map, and you can add any field, including custom fields.
Do I need to write scripts or install plugins?
No. The integration is configured visually in ZigiOps. You connect Zammad with its URL and an API token, connect ServiceNow, and build the workflow.
How does ZigiOps know which tickets to pick up?
The source side polls on an interval you choose, and a filter selects the records to sync — for example only tickets created since the last run. You can also run an action manually.
Can I see what happened on each run?
Yes. The Troubleshooting view lists every execution with its result and duration, so you can confirm each sync completed.
Show us your Zammad–ServiceNow process.
Book a demo and we'll connect your Zammad helpdesk and ServiceNow instance.