Guides · Make
Get a Mac notification from a Make scenario with the HTTP module
Make's HTTP module can POST JSON from any step of a scenario, so a scenario that watches a mailbox, a sheet or an RSS feed can end with 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 Make 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 Make. In the scenario: add a module, HTTP, then Make a request. URL your hook URL, Method POST, Body type Raw, Content type JSON (application/json), Request content
{"event":"new_row","title":"{{1.title}}"}with values mapped from earlier modules. Create the EventBar hook as Generic JSON with type fieldevent. - 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 |
|---|---|---|
new_row | New row | {title} |
new_email | {from} · {subject} | |
feed_item | Feed item | {title} |
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
- The field names are yours. Map a
urlfield from the source item and the notification gets a link; maptimeand the event shows the item's own time. - Each run that reaches the module is one event. A scenario on a 15-minute schedule that finds nothing should stop at a filter before the HTTP module, or you count empty runs.
- The HTTP module is on Make's free plan; the hook URL is the secret, so keep it in the module rather than in a shared template.
The full contract, including how each preset reads a payload and what the answers mean, is in the API docs. Something about Make's payload changed? Tell us and we'll fix the guide.