Guides · Netlify

Get a Mac notification when a Netlify deploy succeeds or fails

Netlify's outgoing webhook notifications send the deploy object to a URL when a deploy starts, succeeds or fails. One hook per outcome gives you clean types.

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

Steps

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.
Paste it into Netlify. In Netlify: Site configuration, then Notifications, then Add notification, then Outgoing webhook. Event Deploy succeeded, URL your hook URL. Create the EventBar hook as Generic JSON with default type deploy_succeeded; make a second notification and hook with default type deploy_failed. The payload carries no event name, so the default type does the naming.
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.
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

Type	Title	Body template
`deploy_succeeded`	Deployed	`{name} · {branch} · {deploy_time}s`
`deploy_failed`	Deploy failed	`{name} · {branch} · {error_message}`

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

Link template {deploy_ssl_url} opens the site; {admin_url} opens the Netlify deploy log.
Netlify offers a JWS secret for signing; the generic preset doesn't verify it, the URL is the secret.

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