Nashpush Zapier integrationAutomate Nashpush with Zapier.
The Nashpush Zapier integration gives you 1 trigger and 1 action: react when a new consumer is added, and send push notifications from a Zap. The trigger is instant, Nashpush is not a premium app, and a two-step Zap runs on the free plan.
Verified Trustpilot reviews · AI, automation & growth agency
What the Nashpush Zapier integration does
The Nashpush Zapier integration connects your Nashpush push notification account to your other apps. It has two moving parts: a trigger that fires when a new consumer is added, and an action that sends notifications to an audience. Small, but each piece does one clear job, and the trigger is instant.
A notification for every new consumer. With New Consumer as the starting point and Send Notifications right after it, a notification goes out to the audience you specify each time a consumer is added. You write the title and the text once, in the Zap.
A list of consumers you can work with. The same trigger can feed a spreadsheet instead, one row per new consumer, so you can count and sort them without exporting anything from Nashpush.
A heads-up for your team. A new consumer can also become a message in your team chat tool, so your team hears about each new consumer without opening Nashpush.
Because New Consumer is an instant trigger, none of these Zaps waits for a check: Nashpush tells Zapier itself, whatever your plan. That is the main thing to remember if you are on the free plan.
What Zapier does not do here: there is no search step, nothing to look up or update an existing consumer, and no trigger for other events in your account. Any Zap you build with Nashpush has to start with a new consumer. To see how Zapier compares with other tools, see our Make vs Zapier comparison.
Zapier words in one minute
Seven terms come back across this page. Here they are once, in plain words.
- Zap
- The automation you build on Zapier: one trigger, then one or more actions that run every time that event happens.
- Trigger
- The event in an app that starts the Zap. Once the Zap is on, Zapier waits for it, here a new Nashpush consumer.
- Action
- What the Zap does once it has started: the step that writes, sends or moves something for you, like a push notification.
- Task
- The unit Zapier bills: one action your Zap completes successfully. The number on your plan counts only those.
- Polling trigger
- A trigger Zapier checks on a timer: it asks the app for new items at a fixed interval. Nashpush has none on Zapier.
- Instant trigger
- A trigger the app reports itself, the moment the event happens, so nothing waits for a check. New Consumer works this way.
- Filter
- A step that lets the Zap go on only when what arrived meets a condition you set, and stops it otherwise.
What a Nashpush Zap costs you
Zapier bills tasks, and only one thing counts as a task: an action that went through.
- Free plan100 tasks a month, unlimited Zaps, two steps each
- Premium appNo, Nashpush works on the free plan
- TriggerInstant, the plan interval does not apply
- Failed actionNot counted
The trigger never costs anything: a new consumer starting the Zap is free. Each successful action counts once, so every Send Notifications step that goes through uses one task. An action that fails is not counted. The free plan gives you 100 tasks a month and as many Zaps as you like, but each one stops at two steps. Add a filter or a second action and the Zap becomes multi-step, which needs a paid plan. The grid below shows how often Zapier checks polling triggers on each plan. It does not apply to Nashpush: its only trigger is instant.
Connect Nashpush to Zapier in 3 steps
- 01
Open the connection dialog
Go to the Apps page of your Zapier account and click + Add connection. A dialog opens with a search box where every app Zapier supports can be found by name.
- 02
Pick Nashpush and add it
Type Nashpush in the search box, select it, then click Add connection. A new tab opens where you sign in to Nashpush with the account you send notifications from.
- 03
Grant access
Give Zapier access to the account in that tab. You need a Nashpush account, plus read or write access on anything you do not own yourself and want the Zap to touch. Every Nashpush step then reuses this connection.
Your first Nashpush Zap
GoalSend a push notification each time a new consumer is added, with a two-step Zap.
- 01
Create the Zap
Start a new Zap, pick Nashpush as the app that starts it and New Consumer as the event, then choose the Nashpush connection you added.
- 02
Test the trigger
Run the trigger test. Zapier brings back the three most recent consumers of the account, so you can see which fields arrive and map them on a real one.
- 03
Add the action
Add Nashpush with Send Notifications. Fill the required Title and Text, typed in the Zap or mapped from the trigger. This two-step Zap runs on the free plan.
- 04
Test, then publish
Run each step once and read what came back. When it looks right, click Publish. Consumers added before that moment do not start the Zap.
Nashpush trigger
1 event starts a Zap when something happens in Nashpush, and one of them is instant: the app calls Zapier straight away, whatever your plan.
New Consumer
Instant triggerIn Zapier“Triggers when a new consumer is added.”
Starts your Zap each time a new consumer is added to your Nashpush account, and hands that consumer's details to the steps that follow.
Nashpush action
Nashpush gives you 1 action. For each one: what it does for you, when to reach for it, and what to watch out for.
Send Notifications
ActionIn Zapier“Sends notifications to specified audience”
Sends a push notification from your Nashpush account to the audience you specify, with the title and the text the Zap gives it.
When a Nashpush Zap breaks
Zapier attaches no help article to Nashpush, so the cases below are the general limits every Zap runs into.
Three cases are worth knowing before you publish. If a Zap stops doing what you expect, our Zapier troubleshooting guide is the place to start.
Existing consumers are not picked up
A Zap only reacts to what happens after you switch it on. Consumers already in Nashpush do not start it, and reaching them is a separate job.A Zap that sets itself off
A Zap that writes into the same place its own trigger watches can start itself again and again, and burn through your task count fast.A sudden flood of consumers
If a trigger suddenly returns a huge batch, after a bulk import or a migration, Zapier's flood protection can hold the run back.
Need help automating Nashpush with Zapier?
A person reads every message.
