Connect Zapier to Hushdesk
Start a Zap whenever a ticket is created, a customer replies or a ticket closes, using a Webhooks by Zapier trigger and the Hushdesk Webhooks app.
Last updated 2 min read
Zapier connects Hushdesk to thousands of apps without code. It works today through the Webhooks app: Hushdesk posts ticket events to a Zapier catch hook, and your Zap does the rest.
Before you start
- Who can do this: owners and admins in Hushdesk.
- Plan: all Hushdesk plans; a Zapier plan that includes Webhooks by Zapier.
- What you need: a Zapier account.
- Time: about ten minutes.
Step by step
- In Hushdesk, open Settings > Apps > Zapier and read Set it up in 3 steps.
- In Zapier, create a Zap with the trigger Webhooks by Zapier, event Catch Hook, and copy its URL.
- Back in Hushdesk, press Open Webhooks. Paste the Zapier URL into Endpoint URL and type a Signing secret.
- Press Connect and test. Hushdesk sends a
pingevent to Zapier. - In Zapier, test the trigger. Then create a test ticket (email your support address) so Zapier sees a real
ticket.createdevent. - Map the fields from the test event, such as
ticket.subjectandticket.customer.email, add your action steps and switch the Zap on.
What happens next
Every new ticket, customer reply and ticket closed by a person starts your Zap. The Webhooks card in Hushdesk shows the last delivery and whether Zapier accepted it.
Recipe ideas
| Goal | Zap |
|---|---|
| Log tickets to a sheet | Catch Hook → Filter event is ticket.created → Google Sheets: Create row |
| Thank customers after a close | Catch Hook → Filter ticket.closed → your email tool: Send email |
| Grow a list from replies | Catch Hook → Filter customer.replied → Mailchimp or Klaviyo: Add subscriber |
| Tag-based alerts | Catch Hook → Filter tags contain vip → Slack: Send channel message |
See the field list in Webhook events and payload.
Tips
- Add a Filter step so only the events you care about continue.
- Zapier cannot check the signature without a Code step. If the Zap does something sensitive, add a Code by Zapier step that recomputes the HMAC. See Verify webhook signatures.
- One Webhooks endpoint per workspace: if you need several Zaps, start one Zap and use Paths to branch.
Troubleshooting
"Your endpoint did not answer the test event with a 2xx"
The Zapier URL is wrong, or the Zap's trigger was deleted. Copy the catch hook URL again.
"That endpoint url does not look right"
The URL must start with https://.
Zapier shows only the ping
Create a real test ticket so Zapier can see the full ticket fields.
Frequently asked questions
Does Hushdesk have a Zapier app?
Not a dedicated one. Zapier works today through the Webhooks app. You create a Zap that starts with a Webhooks by Zapier catch hook, paste its URL into Hushdesk and every new ticket, customer reply and closed ticket starts your Zap with the ticket's details.
Which Zapier plan do I need for Hushdesk webhooks?
Webhooks by Zapier is a premium trigger in Zapier, so it needs a Zapier plan that includes premium apps. Check Zapier's pricing page for the current plans. Hushdesk does not charge anything extra for sending webhooks on any of its own plans, including Free.
Can Zapier send data into Hushdesk?
Not today. The Webhooks app sends events out of Hushdesk to Zapier, but Hushdesk does not yet offer a public API for Zapier to create tickets or change them. You can still start tickets by sending an email to your support address from a Zap.
What can I do with Hushdesk and Zapier?
Common Zaps log every new ticket to a Google Sheet, post closed tickets to a CRM, add customers who reply to an email list, or alert a specific Slack channel for tickets with certain tags. Any of Zapier's apps can follow the Hushdesk trigger.
How do I filter which tickets start my Zap?
Hushdesk sends every event to the URL, so add a Filter by Zapier step after the trigger. For example, continue only when event is ticket.closed, or when tags contain refund. The event name is also sent in the X-Hushdesk-Event header.
Was this helpful?
Related articles
- Send ticket events with webhooksConnect the Webhooks app to post a signed JSON event to your HTTPS endpoint when a ticket is created, a customer replies or a ticket is closed.
- Webhook events and payload referenceThe exact JSON Hushdesk posts for ticket.created, customer.replied, ticket.closed and the test ping, with every field and header explained.
- Connect Make to HushdeskRun a Make scenario when a ticket is created, a customer replies or a ticket closes, using a Make custom webhook and the Hushdesk Webhooks app.
- Connect n8n to HushdeskTrigger an n8n workflow from Hushdesk ticket events with the n8n Webhook node, and verify the signature in a Code node on your own n8n instance.
- Verify webhook signatures in Node, Python or PHPCheck the X-Hushdesk-Signature header so your endpoint only trusts events Hushdesk sent. Ready-to-copy code for Node.js, Python and PHP.
Still stuck?
Chat with the Hushdesk team. A person answers on every plan.