How to send a push notification with Zapier or Make (no code)

The idea in one sentence

Lert gives you a unique URL. Zapier and Make both have a generic "send an HTTP request" step. You put your Lert URL in that step, map some text into it, and every time your trigger fires, your phone gets a push. That's the whole pattern — the rest is just clicking through the editor.

First: copy your Lert URL

Open the Lert app and your unique endpoint is on screen — something like https://lert.dev/p/your-id. Tap Copy. Treat it like a password: anyone who has it can send you a notification, so paste it only into your own Zaps and scenarios, and regenerate it in the app if it ever leaks. This URL is all the authentication you need — there's no API key to create.

In Zapier: a Webhooks by Zapier action

Start a Zap with whatever trigger you like — a new Google Forms response, a new Airtable record, a starred Gmail email. Then add an action step:

1. For the action app, choose Webhooks by Zapier and the event POST. (Webhooks is available on paid Zapier plans.)
2. In URL, paste your Lert endpoint: https://lert.dev/p/your-id.
3. Set Payload Type to JSON.
4. Under Data, add a title field and a body field. Click into each value and pick fields from your trigger — for a form, that might be the respondent's name as the title and their message as the body. Optionally add a tag to label it in your Lert history.
5. Leave Wrap Request In Array off and Unflatten on the default.

Zapier assembles a request that looks like this behind the scenes:

POST https://lert.dev/p/your-id
Content-Type: application/json

{
  "title": "New form response",
  "body": "Ada Lovelace — Interested in a demo",
  "tag": "leads"
}

Hit Test action. Zapier fires the request, Lert returns {"delivered":1}, and your phone buzzes within a second or two. Turn the Zap on and you're done.

In Make: an HTTP module

Make (formerly Integromat) calls the same thing an HTTP module. Build a scenario with your trigger, then add a module:

1. Add HTTP → Make a request as the next module.
2. URL: your Lert endpoint, https://lert.dev/p/your-id.
3. Method: POST.
4. Under Headers, add Content-Type with value application/json.
5. Set Body type to Raw, content type JSON (application/json), and in the request-content box write the JSON, dragging in mapped values from earlier modules where you want dynamic text.

{
  "title": "Airtable: new row",
  "body": "{{1.Name}} added to Leads",
  "tag": "airtable"
}

The {{1.Name}} token is Make's way of dropping a value from module 1 into the text. Run the scenario once to test, confirm your phone buzzes, then schedule it or set it to run instantly.

Things worth connecting

• Google Forms → Lert: get pinged the moment someone submits, with their answers on your lock screen.
• Airtable / Google Sheets → Lert: a new row in a "Leads" or "Bugs" table becomes an instant buzz.
• Gmail → Lert: a label or a matching search fires a push, so you notice the emails that actually matter without watching the inbox.
• Stripe / Shopify → Lert: a new payment or order taps you on the shoulder — see the new-sale use case.

Keep an eye on volume

Automations can fire more often than you expect. Lert allows 60 requests per minute per IP and, on the Free plan, 50 notifications a day (Pro is unlimited, 10,000/day fair use). If a Zap or scenario suddenly loops, you'll get a 429 response rather than an endless stream — but it's worth adding a filter step so you only notify on the events you actually care about.

Why Lert for no-code notifications

Most push services want you to create an account, generate an API key, and store credentials inside your automation tool before anything works. Lert needs none of that: paste one URL into a webhook step and you have push notifications. It's the simplest possible bridge between "something happened in one of my apps" and "my phone told me."