Guides · Zapier

Get a Mac notification from any Zap with Webhooks by Zapier

Any Zap can end with a Webhooks by Zapier POST, which means anything Zapier can see, a form response, a new CRM lead, a calendar booking, can be a notification and a count on your Mac. You choose the fields.

Needs: the free EventBar app on your Mac, an EventBar account, and a Zapier account with permission to add webhooks. About five minutes. Generic JSON.

Steps

1. Create the webhook URL. In the EventBar dashboard, open the Webhooks tab, pick the group this belongs to (one group per site or app is the usual shape), choose the provider Generic JSON, name it, and press Create. Copy the URL; it stays visible and can be rotated any time.
2. Paste it into Zapier. In the Zap editor: add an action, app Webhooks by Zapier, event POST. URL your hook URL, Payload Type json, and under Data add the fields, for example event set to lead and name mapped from the trigger. Leave Wrap Request In Array off, or the hook sees one text body instead of fields. Create the EventBar hook as Generic JSON with type field event.
3. Trigger one. Most services offer a test delivery; otherwise do the real thing once. It shows up in the dashboard's Events tab within a second and in the menu bar, as an undefined type named after the event. That first one is your proof the wiring works.
4. Make it read well. Press Define on the new type and give it a title and a body template. Fields come from the payload, nested ones with dots. The table below is a starting point.

What you'll see

Every type has its own switch in the menu bar, so a noisy one can be quiet on this Mac and still counted. Counts cover the last hour, 24 hours, 7 days, 30 days and all time.

Worth knowing

• Webhooks by Zapier is a premium action, so it needs a paid Zapier plan; nothing on the EventBar side does.
• The field names are whatever you type under Data. Keep event fixed per Zap, or map it from the trigger if one Zap should produce several types.
• Zapier's Test step sends a real POST; it counts once, which is a fine way to confirm the wiring.

The full contract, including how each preset reads a payload and what the answers mean, is in the API docs. Something about Zapier's payload changed? Tell us and we'll fix the guide.