Direct mail on autopilot for JobNimbus.
Paste one JobNimbus API key and Mailr goes to work: jobs reaching a status fire postcards into the right neighborhoods, landing-page leads land in JobNimbus as contacts, and approved estimates stop that home getting mail.
CONNECTED · API KEY
- Jobs inJobNimbus activity fires campaigns automatically
- Mail out1-of-1 cards to the homes that matter
- Leads backCaptured leads write into JobNimbus instantly
HOW IT CONNECTS
Three steps, and the first one’s the hardest.
01
Connect
Paste an API key from JobNimbus → Settings → API — validated live against your account before it saves, so a typo can't half-connect.
02
Confirm
A 3-step confirm-only wizard shows real field samples from your own JobNimbus account — you see your actual data before anything runs.
03
Run
Reactivation, automations, and Auto Follow-Up are live immediately.


WHAT FLOWS BOTH WAYS
Deep, not decorative. Four things run on the connection.
Part of Mailr’s 63 native trigger events across 12 CRMs — with revenue synced back so the attribution dashboard can put a dollar figure on every campaign.
Fire mail off real JobNimbus activity — 2 native events, each filtered by custom fields: “only Completed jobs over $15k in the Roofing workflow.”
Mailr imports your past jobs and contacts from JobNimbus — by workflow and status, or since a date — then mails the nearest neighbors of every one. The contacts source remails your whole book, not just addresses with a finished job.
Landing-page leads are created as JobNimbus contacts at capture time — in the workflow and status you pick, “Mailr” as the lead source, the details as a note, deduped by email. Every lead deep-links straight to the contact in JobNimbus.
The moment an estimate is approved in JobNimbus, that customer is removed from future mailing audiences. You never pay to advertise to someone you already closed.
- HourlyJobNimbus has no webhooks, so Mailr sweeps every hour
- Attribution window180 days, last touch: the most recent mail to that address gets the credit
- View in JobNimbusEvery lead and deal in Mailr links straight to its record
JOBNIMBUS TRIGGER EVENTS
Mail that fires itself off JobNimbus activity.
JobNimbus has no outbound webhooks, so Mailr sweeps your account every hour and fires anything new. Every event is deduped, so a re-sweep can never double-mail. Every event takes custom-field filters like “only Completed jobs over $15k in the Roofing workflow.”
+ custom-field filters on every event

QUESTIONS
The questions JobNimbus shops ask.
- What do I need to connect JobNimbus?
- An API key from JobNimbus → Settings → API. Mailr checks it against your account before saving, then a 3-step confirm wizard shows real field samples from your own jobs.
- Which job statuses can fire mail?
- Any status in any workflow — Mailr reads your workflows live, so “Job reaches Completed in the Roofing workflow” is a dropdown, not a config file. Add custom-field filters on top.
- What does Mailr write back into JobNimbus?
- Captured leads, as contacts with the “Mailr” lead source and a note. Everything else is read-only: jobs and estimates power triggers, Reactivation, and revenue attribution.
- How fast do triggers fire?
- JobNimbus has no outbound webhooks, so Mailr sweeps your account every hour and fires anything new — deduped, so a re-sweep can never double-mail.
THE REST OF THE HAND
Not on JobNimbus? Yours is here too.
Their Home.
Your Work.
Connect your CRM, pick a neighborhood, and put a 1-of-1 card in every mailbox that matters. First campaign out the door in an afternoon.
No subscriptions · No minimum order size
