Nudge Zapier integrationAutomate Nudge with Zapier.
Nudge Zapier integration: 0 triggers, 1 action, 0 searches. Once a job is logged as done, Zapier can hand Nudge the customer's mobile number, and Nudge queues a text asking for a review. Nothing starts from Nudge: another app always fires first.
Verified Trustpilot reviews · AI, automation & growth agency
What the Nudge Zapier integration actually does
The Nudge Zapier integration does one thing: it adds a contact to Nudge and puts a review request in the queue for them. The event that decides when that happens lives in another app, the one where you record that a sale, a visit or a job is finished. Zapier carries the phone number across so nobody has to type it twice.
One action, but three useful results depending on where the Zap starts:
A review ask after every closed job. When a technician marks a job as done in your field service tool, Send Review Request adds the customer to Nudge and queues the text. Nobody at the office has to remember.
A review ask after every paid invoice. Start the Zap from your billing or point-of-sale app instead, and the request follows the payment, at the moment the customer is most likely to be pleased.
A clean list built from a spreadsheet. Teams that still log appointments in a sheet can start from a new row: each line with a mobile number becomes a contact and a queued request.
What Zapier does not do with Nudge: it cannot react to anything inside Nudge (no trigger, so you will not hear about a review left or a text delivered), and it cannot look up a contact that already exists (no search). If you want to weigh this against other tools, our Zapier review sets out where it fits.
Zapier vocabulary in one minute
Seven words come back on every line of this page. Here they are in plain English.
- Zap
- The automation you build: one trigger, then one or more actions that run each time the trigger event happens.
- Trigger
- The event in an app that starts the Zap. Nudge has none, so the trigger always comes from another tool you use.
- Action
- What the Zap does once it has started: the step that writes, sends or moves something for you. Here, the review request.
- Task
- The unit Zapier bills: one action your Zap completes successfully. Your plan's allowance is a count of those.
- Polling vs instant
- A polling trigger is checked on a timer. An instant trigger is pushed by the app the moment the event happens.
- Filter
- A step that lets the Zap carry on only when what arrived meets your condition, and stops it otherwise.
- Connection
- Your Nudge account linked to Zapier once, then reused by every step that talks to Nudge. No password to retype.
What a Nudge review request costs on Zapier
Nudge is not a premium app, so it works on the free plan. Zapier counts tasks, and only the Nudge step uses them.
- Free plan100 tasks a month, unlimited Zaps
- Free plan Zap size2 steps: one trigger, one action
- Premium appNo, Nudge runs on the free plan
- CountedEach successful review request
The trigger in the other app never costs a task, however often Zapier checks it for new items. Each review request that goes through to Nudge costs one task, and one that fails costs nothing. The catch is the free plan: it builds Zaps of two steps only, one trigger and one action. Add a filter (say, only customers who paid) and the Zap becomes multi-step, which needs a paid plan. Polling triggers are also checked less often on Free, as the grid below shows.
Connect Nudge to Zapier in 3 steps
- 01
Open your connections
In Zapier, go to Apps, the page that lists every account you have linked. Click + Add connection, type Nudge in the search box of the dialog and pick it from the results.
- 02
Sign in to Nudge
Click Add connection. A new tab opens on Nudge: log in with the account that sends your review requests. You need a Nudge account first, Zapier cannot create one for you.
- 03
Grant access
Approve the access request in that tab. The connection then appears in your list, and every future Nudge step reuses it. If the account belongs to a colleague, make sure yours is allowed to add contacts.
Your first Nudge Zap, step by step
GoalEvery appointment logged as done in a shared Google Sheet sends the customer a review request through Nudge.
- 01
Start the Zap
Start a new Zap in the editor. Pick Google Sheets as the app that starts things, a new row as the trigger, and the sheet where your team logs finished appointments.
- 02
Test the trigger
Run the test. Zapier brings back the three most recent rows of the sheet, so you can pick a real one with a mobile number to map from.
- 03
Add the Nudge action
Add a step below the trigger, choose Nudge as the app and Send Review Request as the event, then select the Nudge connection you created above.
- 04
Map the phone number
Put the column holding the customer's mobile into Mobile Phone Number. It is the one required field, so a row with that cell empty will stop the step.
- 05
Test and publish
Test the Nudge step with your own number first and read what comes back before going further. Then click Publish to switch the Zap on.
Nudge actions on Zapier
Nudge gives you 1 action. For each one: what it does for you, when to reach for it, and what to watch out for.
Send Review Request
ActionIn Zapier“Adds a contact and queues a review request to be sent.”
Creates the customer as a contact in Nudge and lines up a text asking them to review your business. The request is queued rather than fired on the spot, so Nudge decides the send itself.
When the Nudge Zap breaks
Zapier attaches no help article to Nudge, so the failures below come from how Zaps work in general and from what the action itself says.
With a tool that texts real customers, the expensive mistakes are the ones that send too much or to the wrong people. The Zapier troubleshooting guide covers the usual checks when a run fails.
Past customers are never asked
A Zap only reacts to what happens after you switch it on. Customers served before that day stay out of Nudge: reaching them is a separate job.A bulk import floods the queue
Paste a big batch of old rows into the trigger sheet and the trigger returns them all at once. Zapier's flood protection may hold the run back, which is the safer outcome here.One row, one request
On a polling trigger, Zapier remembers what it has already seen. The same row never starts the Zap twice, so a customer is not asked twice for one visit.Rows without a mobile fail
Send Review Request stops when Mobile Phone Number is empty. Each such run errors out, costs no task, and leaves that customer without a request.
Need help automating Nudge with Zapier?
A person reads every message.
