Make

When to pick Make over Zapier

• You want to see the workflow as a graph rather than a linear list.
• You need conditional branching (if-action-A-then-do-X-else-Y) without paying for Zapier's top tier.
• You're running enough volume that Zapier's task limit pinches.

For a single zap on a low-volume server, Zapier is simpler. For more than three steps or anything with branching, Make beats it.

Set up

1. Read the Webhooks setup guide — same flow, same secret.
2. Create a new Scenario in Make.
3. Add a Webhooks → Custom webhook trigger; copy the URL.
4. Paste the URL into Sloth Lee's webhook subscription form.
5. Pick events. Make's trigger gives you the full payload as a structured object — drag fields straight into downstream modules.

Templates worth a look

Ban + Trello + Slack

On mod_action with action == "ban":

• Create a Trello card on the moderation board with case + reason.
• Post to a Slack channel with a one-line summary + the dashboard URL.
• If severity == "major", also DM the on-call mod.

One scenario covers all three with branching.

Tickets → Notion database

• On ticket_open, create a row in Notion.
• On ticket_reply, append the new message body to the row's comments.
• On ticket close, set the row status to Closed with the resolution note.

Signature verification

Make's custom-webhook trigger doesn't natively verify HMAC signatures, but you can do it in a one-line filter module before any downstream actions run. Same algorithm as the Zapier setup — read the Webhooks docs for the exact code.