Dispatch Tickets for Zapier
A native Zapier app that connects your support tickets to 8,000+ other apps — no code required. It's in active development. Here's what's coming, and how to automate against Dispatch Tickets today.
Why a native app
Unlike Claude, n8n, and Make, Zapier doesn't consume Model Context Protocol servers directly. So instead of pointing Zapier at our MCP endpoint, we're building a first-class Zapier Platform integration with real triggers and actions — built on the same REST API and webhooks that power everything else.
When it lands, you'll connect it by pasting a Dispatch Tickets API key — the same sk_live_… key you use everywhere else — and start building Zaps.
Planned triggers
Triggers start a Zap. These are powered by Dispatch Tickets webhooks, so they fire in real time.
New Ticket
Fires when a ticket is created in a brand — kick off any downstream Zap.
Ticket Updated
Fires when a ticket's status, priority, or assignee changes.
New Comment
Fires when a reply or internal note is added to a ticket.
Planned actions & searches
Actions do something in Dispatch Tickets as a later step in a Zap.
Create Ticket
Open a new ticket in a brand from any Zap.
Update Ticket
Change status, priority, assignee, category, or tags.
Add Internal Note
Post a private team note. Sends nothing to the customer.
Reply to Customer
Post a public reply that emails the customer.
Find Ticket
Search for a ticket to use in later steps.
One action sends email. Reply to Customer posts a public reply that's emailed to the customer. Add Internal Note stays private to your team. Everything else reads data or changes it without notifying anyone.
Want early access?
We're inviting teams to test the Zapier app before it hits the public directory. Tell us what you'd automate and we'll get you in.
Automate against us today
You don't have to wait. A few options work right now: