Skip to content

Connect Make to Hushdesk

Run 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.

Last updated 2 min read

On this page

Make (formerly Integromat) builds visual automations. It works with Hushdesk today through the Webhooks app: Hushdesk sends ticket events to a Make custom webhook, and your scenario routes them anywhere.

Before you start

  • Who can do this: owners and admins in Hushdesk.
  • Plan: all Hushdesk plans; any Make plan.
  • What you need: a Make account.
  • Time: about ten minutes.

Step by step

  1. In Hushdesk, open Settings > Apps > Make and read Set it up in 3 steps.
  2. In Make, create a scenario. Add the Webhooks module Custom webhook, create a webhook and copy its URL.
  3. In Hushdesk, press Open Webhooks, paste the URL into Endpoint URL and type a Signing secret.
  4. Press Connect and test.
  5. In Make, press Redetermine data structure on the webhook, then create a test ticket in Hushdesk (email your support address).
  6. Make now knows every field. Add a Router or Filter, then your action modules, and switch the scenario on.

What happens next

Each new ticket, customer reply and ticket closed by a person runs your scenario. The Hushdesk Webhooks card shows the last delivery result.

Scenario ideas

Goal Modules
Daily ticket log Custom webhook → Filter ticket.created → Google Sheets: Add a row
CRM timeline Custom webhook → Filter ticket.closed → HubSpot: Create engagement
Route by tag Custom webhook → Router on ticket.tags → Slack channels per team

Field names are listed in Webhook events and payload.

Mapping the fields

After Make has seen a real event, the webhook output lists event, at, workspace_id and the ticket bundle with id, subject, status, channel, priority, tags, url, customer and last_message. Map these into later modules by clicking them in the field picker.

Tips

  • Put the filter right after the webhook to save operations.
  • Make replies Accepted with a 200 status by default, which is what Hushdesk needs.
  • Use the ticket.url field to link back to the ticket from any message Make sends.

Troubleshooting

"Your endpoint did not answer the test event with a 2xx"

The scenario's webhook was deleted or the URL is wrong. Copy it again from Make.

My scenario does not run

Make scenarios only run when switched on, or while you press Run once. Switch it on after testing.

Frequently asked questions

How do I connect Make to Hushdesk?

Create a Make scenario that starts with the Webhooks module Custom webhook, copy its URL, then open Settings, Apps, Webhooks in Hushdesk, paste the URL with a signing secret and press Connect and test. Run the scenario once to learn the data structure, then switch it on.

Why does Make not see my ticket fields?

Make learns a webhook's structure from the first request it receives. The ping Hushdesk sends on connect only has event and at. Press Redetermine data structure on the webhook, then create a test ticket so Make receives a full ticket.created event with every field.

Can I verify the Hushdesk signature in Make?

Make can compute an HMAC with its built-in functions, but it is easier to keep sensitive actions behind a filter on fields you control, or to verify in a small service of your own. For most logging and notification scenarios, the private webhook URL is enough.

Do Make operations cost anything for each Hushdesk event?

Each event that reaches your scenario uses Make operations from your Make plan. Hushdesk itself does not charge for webhooks. Add a filter right after the webhook so events you do not need stop early and use fewer operations.

Can Make create tickets in Hushdesk?

Not through an API yet. Hushdesk sends events to Make but does not offer a public API for creating or updating tickets. A scenario can still send an email to your support address, which arrives as a new ticket.

Was this helpful?

Related articles

Still stuck?

Chat with the Hushdesk team. A person answers on every plan.