The short answer
Partly. JobNimbus automations can trigger on a job status change, and with Engage (its paid texting add-on) you can hand-build a review-request workflow — but there is no built-in Google review ask, no follow-up sequence, and no review tracking. ReviewNudger plugs into that same automation: one Job › Modified › "Status is Complete" → Webhook rule, and every completed job sends the homeowner one neutral text or email with a one-tap Google review link.
Why roofing and exterior contractors undershoot on reviews
A roofing company completes a $14,000 job, the homeowner is relieved and grateful for exactly one evening, and then the crew is on the next house. The JobNimbus job moves to Complete or Paid, the invoice goes out — and nobody asks for the review, because asking is a separate task nobody owns. Contractors with 300 Google reviews are not doing better work than contractors with 30; they have a system that asks every homeowner at the right moment without anyone remembering.
JobNimbus gives you the raw material: the job, its status, and the primary contact with email and phone. Its automation builder can react to a status change, and JobNimbus has a webhook action on every plan. What it does not have is a review-request product — the DIY route means building email templates, paying for Engage to text, and still having no follow-ups, no opt-out handling, and no view of which requests became reviews.
How the status-change trigger works
You create a JobNimbus API key, paste it into ReviewNudger, and get back a unique webhook address. In JobNimbus you add one automation: Job › Modified › "Status is" your completed or paid status → Webhook action with that address. Your own workflow names the trigger — Complete, Paid in Full, Closed Won, whatever your pipeline calls it — so it fits how your office already works.
When the automation fires, ReviewNudger re-reads the job and its primary contact through the API (the webhook itself carries only a hint), applies your sending rules, and after the delay you choose — an hour after the crew leaves, or that evening — sends the homeowner one neutral review request by text or email with a one-tap link to your Google review form. Later status changes on the same job never ask again; a job whose contact has no email or phone is recorded and skipped, and your connection panel shows how many.
Every completed job gets the same ask. Picking only the homeowners you expect to be happy is review gating, which violates Google policy and the FTC consumer-review rule; the public Google link is always on the landing page, and an unhappy homeowner can send private feedback from the same place.
What changes after a month
Contractors asking every homeowner by text shortly after completion typically turn around a third of requests into reviews. A crew completing 12 jobs a week adds roughly 15 Google reviews a month — with automatic follow-ups for the homeowners who meant to but forgot, one inbox for every new review with an AI reply suggestion, and an alert the moment a 1- or 2-star review lands so you can respond before the next prospect reads it.
Frequently asked questions
Which JobNimbus plans work, and does it use an integration slot?
API keys and the automation webhook action are available on every JobNimbus tier. JobNimbus caps active integrations on lower tiers; ReviewNudger is one integration. Check your plan's integration limit if you already run several.
Why does ReviewNudger need an API key if the automation already sends a webhook?
JobNimbus's automation webhook is a bare URL with no signature and a thin, loosely documented payload, so ReviewNudger treats it as a hint only and re-reads the job and contact through the API before sending anything. That is what makes the request accurate and keeps a mis-fired automation from texting the wrong person.
What if a job bounces between statuses?
ReviewNudger keys the review request on the job, so a job that re-enters the trigger status — or moves Complete → Invoiced → Paid — asks the homeowner once, not once per change.
Can we keep our existing JobNimbus email automations?
Yes. The webhook automation sits alongside anything else you have built; ReviewNudger only reacts to the one rule you create and never writes back to JobNimbus.