Connect n8n to Hushdesk
Trigger 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.
Last updated 2 min read
n8n is an automation tool you can run yourself. It works with Hushdesk today through the Webhooks app: Hushdesk posts ticket events to an n8n Webhook node, and your workflow takes it from there.
Before you start
- Who can do this: owners and admins in Hushdesk.
- Plan: all Hushdesk plans; n8n Cloud or a self-hosted n8n reachable over public HTTPS.
- What you need: an n8n workflow you can edit.
- Time: about ten minutes.
Step by step
- In Hushdesk, open Settings > Apps > n8n and read Set it up in 3 steps.
- In n8n, create a workflow that starts with a Webhook node, method
POST. Copy its production URL. - In Hushdesk, press Open Webhooks, paste the URL into Endpoint URL and type a Signing secret.
- Activate the n8n workflow, then press Connect and test in Hushdesk.
- Create a test ticket (email your support address) and look at the execution in n8n to see every field.
- Add an IF or Switch node on
event, then your action nodes.
What happens next
New tickets, customer replies and tickets closed by a person run your workflow. The Hushdesk Webhooks card shows the last delivery and its status.
Verify in a Code node
With the Webhook node's raw body option on, a Code node can recompute sha256= + HMAC-SHA256 of the raw body using your secret and compare it with X-Hushdesk-Signature. See Verify webhook signatures for the calculation.
Workflow ideas
| Goal | Nodes |
|---|---|
| Store every ticket | Webhook → Postgres: Insert |
| Enrich new tickets | Webhook → IF ticket.created → HTTP Request to your API → Slack |
| Close-out report | Webhook → IF ticket.closed → Google Sheets: Append |
Test and production URLs
n8n gives every Webhook node two addresses. The test URL only listens while you press Listen for test event in the editor. The production URL works once the workflow is active. Use the test URL while building, then paste the production URL into Hushdesk and press Update and test.
Tips
- Keep the Webhook node set to respond immediately, so Hushdesk's five-second limit is never reached.
- Store the signing secret in n8n credentials or environment variables, not in the node text.
- Hushdesk checks the address on every delivery and never posts to private networks.
Troubleshooting
"Your endpoint did not answer the test event with a 2xx"
Activate the workflow and use the production URL.
"That endpoint url does not look right"
The URL must start with https://.
Frequently asked questions
Can I use a self-hosted n8n with Hushdesk?
Yes, as long as its webhook URL is reachable on the public internet over HTTPS. Hushdesk refuses private addresses such as a home network or localhost. Put n8n behind a domain with a valid certificate, and use the Webhook node's production URL in Hushdesk.
Should I use the n8n test URL or production URL?
Use the test URL only while you build, with Listen for test event running. For everyday use, activate the workflow and paste the production URL into Hushdesk, then press Update and test. The test URL stops listening once you leave the editor.
How do I check the Hushdesk signature in n8n?
Turn on the Webhook node's raw body option, then add a Code node that computes HMAC-SHA256 of the raw body with your signing secret and compares it with the X-Hushdesk-Signature header. Stop the workflow when they differ. The Node example in our signature guide works as a starting point.
What can n8n do with Hushdesk events?
Anything n8n can connect to. Common workflows write tickets to a database, enrich new tickets with data from your own systems and post a summary to a team channel, or send closed-ticket details to a CRM. n8n is a good fit when you want full control of the data.
Why does Hushdesk say my n8n endpoint did not answer?
The workflow is not active, the production URL is wrong, the server is not public, or the Webhook node answers with an error. Activate the workflow, set the node to respond immediately and check the URL starts with https.
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.
- 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.
- 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 Zapier to HushdeskStart 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.
Still stuck?
Chat with the Hushdesk team. A person answers on every plan.