Once JobNimbus is connected (see the Setup Guide above), the interesting decisions are which JobNimbus moment to mail off of, and whether you're mailing the customer themselves or the neighborhood around a job — the same Contact-vs-Job distinction that shapes most JobNimbus automations.
Two entities, two very different use cases
Contact-based mail: sends a card to the actual JobNimbus Contact — the homeowner or customer. Use this for anything relationship-facing: thank-yous, review requests, referral asks, or a welcome card the moment a new lead comes in.
Job-based Radius Mail: sends cards to other addresses near the job site, not the customer. This is neighbor marketing — "we just finished a roof on your street" — built off the Job's site address.
Pick your JobNimbus trigger (Contact vs. Job) to match which of these you're building.
Job-completion neighbor campaigns (Radius Mail)
Trigger on Job Modified, and use the condition builder to narrow to the specific status/milestone that represents "job complete" in your JobNimbus setup — this varies company to company, so confirm your team's actual "done" status rather than assuming it's literally named "Completed."
If your card creative or offer is trade-specific, add a second condition on Job Type so, for example, only roofing jobs trigger the roofing-specific mailer.
Set a radius that matches how visible the job realistically is from the street — tighter for interior-only work, wider for full exterior replacements.
Contact-based follow-up
New-lead welcome card: trigger on Contact Created to send a card the moment a new lead enters JobNimbus.
Post-completion thank-you / review request: trigger on Contact Modified, gated by a condition tied to the linked job reaching a completed status, and send a thank-you card with a review link a few days after the crew wraps up.
Referral ask: trigger on a billing/invoice-related status change if your JobNimbus setup tracks that, and time a referral offer to when satisfaction is typically highest.
Filter in Zapier, not in JobNimbus
Build your JobNimbus trigger (or the automation feeding your Zap) broad and permissive — for example, just Job Modified, with no extra condition — rather than encoding your exact "should this mail" logic inside JobNimbus's own condition builder. Do that filtering with a Filter by Zapier step in the Zap itself instead.
This is the reverse of what feels natural, but it holds up better over time: JobNimbus's Automations screen usually requires admin access to edit, so if your mailing logic lives there, changing a status name or adding a new condition means looping in whoever manages JobNimbus settings. Keeping the filter in Zapier means whoever owns the Zap can see and adjust exactly what's gating a mailing, without needing JobNimbus admin access.
Reserve a JobNimbus-side condition for anything Zapier's filter step genuinely can't express — not as your default first move. And if you'd rather that logic live inside LettrLabs itself instead of Zapier, the Native Webhook Setup path supports Inbound Filters directly on the webhook connection.
Mind the sync cadence
Zapier triggers off JobNimbus data on its own schedule, not necessarily the instant a status changes inside JobNimbus. Build in a buffer for time-sensitive plays, and check your Zap history if a fast neighbor mailer seems to be missing the newest jobs.
Preview before you commit spend
Always use LettrLabs' recipient preview before a Radius Mail automation goes active. It's easy to under- or over-scope a Job-based trigger and end up mailing a much larger, or smaller, set of neighbors than intended.
Conversion tracking is a different use case
If you're building a webhook to feed LettrLabs' Conversion tracking (attribution) rather than a mailing, the Contact-vs-Job decision above doesn't apply the same way — use Job, not Estimate, as your trigger. JobNimbus's Estimate object doesn't carry the customer's name, address, phone, or email, so a "Signature Status is Fully Signed" condition on an Estimate trigger won't give LettrLabs enough to match the conversion back to a mailed recipient. See JobNimbus: Native Webhook Setup for the full walkthrough of wiring this correctly.
Want help picking a first JobNimbus trigger to test? Reach out to our team — we're happy to help you scope a first campaign and card design.