Integration · Zapier

Integrate Zapier with Slugy: automate every lead and sale

Forward signed webhooks to a catch hook and trigger 7,000+ app workflows — CRM, Sheets, email, Slack — with no glue code.

Automate freeWebhook reference

Setup in four steps

  1. 1

    Create a Zap with a Catch Hook trigger

    In Zapier, create a new Zap → Trigger: Webhooks by Zapier → Catch Hook. Copy the custom webhook URL (https://hooks.zapier.com/hooks/catch/…). Keep the “find data” test window open — you will send a test event from Slugy in step 3.

  2. 2

    Add the webhook in Slugy

    Open Settings → Integrations → Webhooks → Add webhook. Paste the Zapier catch-hook URL, select lead.created and (on Growth) sale.created, and copy the signing secret shown once. Leave the endpoint enabled. If you need per-campaign routing, add one webhook per Zap and filter by slug downstream.

  3. 3

    Send a test and map fields

    Click Send test on the webhook card, then return to Zapier → Test trigger. You should see a payload with event, workspaceId, createdAt, and data { slug, clickId, customerEmail, saleAmount, saleCurrency }. Map customerEmail to your CRM, saleAmount to Sheets, slug to a digest — every field is plain JSON.

  4. 4

    Add actions and go live

    Common stacks: add a row to Google Sheets for every lead, create/update a HubSpot or Salesforce contact, send a Slack DM for sales over $100, or delay + email a review request. Turn the Zap on. Failed deliveries stay visible in Slugy for debugging; old ones are purged automatically.

Example delivery

POST https://hooks.zapier.com/hooks/catch/… HTTP/1.1
slugy-timestamp: 1728123456
slugy-signature: v1=9f2c…
content-type: application/json

{
  "event": "lead.created",
  "workspaceId": "ws_…",
  "createdAt": "2026-10-05T…Z",
  "data": {
    "slug": "launch",
    "clickId": "clk_…",
    "customerEmail": "buyer@example.com",
    "saleAmount": 49,
    "saleCurrency": "USD"
  }
}
  • Filter in Zapier by event or slug — one webhook can feed many Zaps via Paths.
  • Pause the endpoint with the toggle in Slugy when debugging; no need to delete the Zap.
  • Need Make or Segment too? Add more webhook URLs — events fan out to every endpoint.

FAQ

Do I need code for the Zapier integration?

No. It is a plain outbound webhook — paste the catch-hook URL into Slugy and map JSON fields in Zapier. Signature verification is optional unless you forward to your own server first.

How do I verify webhook signatures?

Compute HMAC_SHA256(secret, timestamp + '.' + rawBody) and compare to the slugy-signature header (v1=…). Reject timestamps older than five minutes to block replays.

Which plan do I need?

lead.created needs Pro; sale.created with revenue fields needs Growth. Webhook configuration itself is available on all workspaces — events simply do not fire until the plan unlocks them.

Zapier vs Make vs Segment?

Same webhook powers all three. Use Zapier for 7,000+ app coverage, Make for visual branching scenarios, or Segment to stream lead and sale events into your warehouse. You can attach all three endpoints at once.

Connect ZapierAll integrations

Bottom line: paste one webhook URL and every lead and sale flows into the 7,000+ apps Zapier connects — no code, no servers.