The short answer
Partly. JobNimbus automations can start on a job status change. With Engage, its paid texting add-on, you can build your own review request setup. But there’s no built-in Google review ask, no follow-ups, and no review tracking. ReviewNudger plugs into that same automation. Add one Job › Modified › "Status is Complete" → Webhook rule. Every finished job then sends the homeowner one text or email with a one-tap Google review link.
Why roofing and exterior contractors undershoot on reviews
A roofing company finishes a $14,000 job. The homeowner is relieved and grateful for exactly one evening. Then the crew is on to the next house. The JobNimbus job moves to Complete or Paid, and the invoice goes out. Nobody asks for the review, because asking is a separate task nobody owns. Contractors with 300 Google reviews aren’t 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 what you need: the job, its status, and the main contact with email and phone. Its automation builder can react to a status change. JobNimbus has a webhook action on every plan. What it lacks is a way to ask for reviews. Doing it yourself means building email templates and paying for Engage to text. You still get no follow-ups, no opt-out handling, and no view of which requests became reviews.
How the status-change trigger works
Create a JobNimbus API key and paste it into ReviewNudger. You get back a unique webhook address. In JobNimbus, add one automation: Job › Modified › "Status is" your completed or paid status → Webhook action with that address. You pick the status from your own pipeline: Complete, Paid in Full, Closed Won, whatever you call it. So it fits how your office already works.
When the automation runs, ReviewNudger reads the job and its main contact again through the API. The webhook itself carries only a hint. Then your sending rules apply. After the delay you choose, like an hour after the crew leaves or that evening, the homeowner gets one review request by text or email. It has 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. Your connection panel shows how many.
Every finished job gets the same ask. Picking only the homeowners you expect to be happy is review gating. That breaks Google policy and the FTC consumer-review rule. The public Google link is always on the landing page. An unhappy homeowner can send private feedback from the same place.
What changes after a month
Contractors who ask every homeowner by text soon after the job turn a large share of those requests into reviews. A crew finishing a dozen jobs a week adds new Google reviews every month. Automatic follow-ups reach homeowners who meant to review but forgot. Every new review lands in one inbox with an AI reply suggestion. You get an alert the moment a 1- or 2-star review lands, so you can respond before the next prospect reads it.
