Send review requests automatically from JobNimbus
JobNimbus connects natively to ReviewNudger: when a job reaches the status you choose in JobNimbus, the event can create one neutral Google review request by SMS or email, subject to your sending rules — automatically, with no middleware in between.
14-day free trial · card required · then $29/mo per location · cancel anytime
Trial: up to 50 SMS attempts from your approved toll-free number or, when the sending conditions are met and one is available, a ReviewNudger number during carrier review. See pricing for sending limits.
How it works
- 1Connect JobNimbus to ReviewNudger with an API key you create in JobNimbus (Settings › Integration › API) — no password sharing, no OAuth screen, no partner approval. ReviewNudger then gives you a webhook URL to paste into one JobNimbus automation: when a job is modified and its status becomes your completed or paid status, JobNimbus calls that URL.
- 2ReviewNudger reads the job and its primary contact through the API, applies your sending rules, and can send one neutral Google review request by SMS or email after the delay you choose — the evening the roof is done, or the morning after final payment. Because your automation picks the status, it works with whatever workflow names you already use.
- 3Each job asks once, however many times its status changes afterwards, and jobs with no reachable primary contact are recorded and skipped rather than guessed. Every send is tracked with delivery status, opt-outs, and review click-through.
Why a native connection beats middleware
The same four guarantees on every native integration — because they come from the platform, not the connector.
No middleware account or per-task fees
The connection runs directly between your account and ReviewNudger. There is no third-party automation account to maintain and no per-task metering on your review requests.
No manual field mapping
ReviewNudger already knows the provider's payload. Customer name, phone, and email resolve automatically — there are no field mappings to build or quietly break later.
Built-in duplicate protection
Every incoming event is deduplicated before any message goes out, so provider retries and replays can never double-text a customer.
Opt-out compliance handled
STOP replies and email unsubscribes are recorded per customer and honored automatically on every future trigger.
Set up the JobNimbus integration
- 1Start a ReviewNudger trial and finish the short signup.
- 2In JobNimbus, open Settings › Integration › API, click New API Key, type ReviewNudger as the description, choose an access profile with Full and Settings access, and copy the key.
- 3Paste the key into ReviewNudger under Settings › Integrations › JobNimbus. ReviewNudger shows you a webhook URL.
- 4In JobNimbus, add an automation: Event based, record Job, action Modified, condition "Status is your completed or paid status" with "Only if Status is modified", then a Webhook action with the URL.
- 5Move a real job to that status to confirm the trigger end to end.
Related resources
Useful next steps for choosing a trigger, setting up the request, and putting the workflow into practice.
Frequently asked questions
Do I need a Zapier account to connect JobNimbus?
No. The JobNimbus integration is native: you connect it directly inside ReviewNudger, with no middleware account, no per-task automation fees, and no field mapping to maintain.
What exactly triggers a review request?
Each time a job reaches the status you choose in JobNimbus, ReviewNudger records the event and evaluates it against your per-location send delay, cooldown, contact, and channel rules. One matching event can create one review-request journey by SMS or email.
Can a retry or duplicate webhook double-text a customer?
No. Every incoming event is deduplicated before any message is sent, and each event can create at most one review request. Provider retries and replays collapse onto the same request instead of sending twice.
What about customers who opt out?
SMS recipients can reply STOP at any time and email recipients can unsubscribe. Opt-outs are recorded per customer and honored across every future JobNimbus-triggered event.
Which JobNimbus plans work with this, and does it use up an integration slot?
JobNimbus lists API & Webhooks as unlimited on every plan, so the connection itself is not plan-gated. Essentials caps active automations at 10 and integrations at 2, and Pro at 30 and 5; ReviewNudger uses one automation and one API key. If JobNimbus counts named API keys against the integration cap, an Essentials account may need to retire an unused key first.
Why does ReviewNudger need an API key if the automation already sends a webhook?
The Job webhook names the primary contact but does not include their email or phone, so ReviewNudger reads the contact through the API before sending. The key is stored encrypted and used only for that read; nothing is written back to JobNimbus.
Questions before you start? Email support@reviewnudger.com and a human will answer.
Make review requests part of your routine.
Set up in about 10 minutes. Requests go out after each paid job, follow-ups run on their own, and every review lands in one inbox.
$0 today · card required · no charge until your 14-day trial ends · $29 a month per location after that