Zapier

Make any Zap reach your phone.

Turn any event from the 7000+ apps Zapier connects into a push on your phone, in under a second and with no code. The booking, the new lead, the row added to a sheet — straight to your pocket.

Push in <1sNo code needed7000+ apps
Features

From any app event to lock screen

Zapier already connects your apps. PocketAlert turns any Zap into a push you cannot miss, no code.

Works with any Zapier trigger

The built-in Webhooks by Zapier action POSTs to your PocketAlert URL, so any of 7000+ Zapier apps can push to your phone.

Map fields in the Zap

Build the JSON Data field once and drop trigger fields into the title and message right inside Zapier.

Route to any app

Set application_id in the body to route a Zap to a specific PocketAlert app, so feeds stay separated.

A channel per Zap

Each application is its own channel, so sales, support, and ops Zaps land in feeds you can mute apart.

Sub-second delivery

The event hits your phone in under a second once the Zap runs, no polling on your end.

Secret webhook URL

The webhook URL is your application secret over HTTPS. Rotate it whenever you need a fresh endpoint.

Get started

Three steps to Zapier notifications on your phone

1

Get an API key

Create an API key on the API Keys page for the Token header.

2

Wire up the Zap

Add a Webhooks by Zapier Custom Request action and POST it to the messages API.

3

Map and ship

Map trigger fields into title and message. The next Zap run buzzes your phone.

Send Zapier events to your phone

1. Get an API key

Create a key on the API Keys page. Zapier sends it in the Token header on every request.

2. Add a Webhooks by Zapier action

In your Zap add an action step, pick Webhooks by Zapier, choose the Custom Request event, and fill it in:

Method:        POST
URL:           https://api.pocketalert.app/v1/messages
Data Pass-Through?: no
Data:          {"title":"New lead","message":"Acme Inc. just booked a demo","level":"high","application_id":"qm47b9pzxzxg"}
Headers:       Token | YOUR_API_KEY
               Content-Type | application/json

3. Map the trigger fields

In the Data JSON, drop fields from the trigger step into title and message:

{"title":"New lead: {{company}}","message":"{{name}} booked a {{plan}} demo","application_id":"qm47b9pzxzxg"}

Test the step and your phone buzzes. The getting-started docs cover every field.

FAQ

Questions, answered

Add a Webhooks by Zapier action set to Custom Request, POST it to https://api.pocketalert.app/v1/messages with a Token header, and map trigger fields into the title and message. Any of the 7000+ apps Zapier supports can now push to your phone.

In the Data field you build a JSON body and drop trigger fields into it. Map a record name into title and any details into message, so each notification reads exactly how you want.

Add application_id to the JSON body to route a Zap to a specific PocketAlert app. Sales, support, and ops events then land in separate channels you can mute independently.

Point different Zaps at different application_id values. Each app is its own channel on your phone, so you keep noisy and urgent feeds apart.

No code and no Zapier app to publish. The built-in Webhooks by Zapier action posts straight to the PocketAlert messages API, so any trigger Zapier offers works out of the box.

Yes. Add a level field to the Data JSON, from silent (-2) to critical (2). Give the closed-won Zap level high so it lands as a time-sensitive push that breaks through iPhone Focus, and set the nightly report Zap to silent — it files into your history without a sound.

Turn any app event into a push, no code.

Create an API key, then add a Webhooks by Zapier POST step that calls the PocketAlert API.