Skip to main content
Connecting JobNimbus lets your jobs start postcard campaigns around the job address as they move through your workflow, and credits the money back to the campaign that earned it. Postcard leads flow the other way into JobNimbus as contacts.

What you get

  • Triggers — two JobNimbus events can start a campaign: A job reaches a status you pick (the workflow and status dropdowns load live from your account, so you see your own status names — Mailr defaults to a “Completed”-stage status), and Estimate approved. You choose the event on each automation.
  • Revenue tracking — revenue books when an estimate is approved. Mailr’s wizard says it plainly: “Revenue books when an estimate is approved.” Job completion never books revenue.
  • Lead delivery — when someone scans your postcard and fills in the landing page, Mailr creates a contact in JobNimbus in the workflow and status you chose in the wizard, with the “Mailr” lead source where Mailr is able to create it. Leads are matched by email so a resubmitted form doesn’t make a duplicate, and extra answers go into a Note activity.
The connected panel sums it up: “Working out of the box: Mailr leads sync into JobNimbus as contacts (with the ‘Mailr’ lead source), new-contact attribution and estimate-approved revenue tracking are on, and campaigns fire when jobs reach statuses you pick on each automation. Job addresses come straight from JobNimbus — review setup to adjust where leads land.”

Connect JobNimbus

1

In Mailr, open Automations

Go to Campaigns → Automations in the Mailr app and find JobNimbus under CRM Connection. Clicking a tile only opens its panel — nothing starts connecting until you press the Connect button inside. Only the workspace owner can connect a CRM.
2

Create an API key in JobNimbus

In JobNimbus, go to Settings → API and create a key. You need an admin access profile to see that screen.
3

Paste the key in Mailr

Press Connect JobNimbus and paste the key. Mailr checks it against your account before saving, so a bad key never saves.
The tile switches to Connected and the 3-step setup wizard opens: Leads → Job address → Tracking.

How syncing works

JobNimbus is checked hourly. JobNimbus has no way to push events the moment they happen, so a campaign can be queued up to an hour after a job changes status. That’s the honest line Mailr shows in the app, and it applies to jobs, estimates and contacts alike. Automated campaigns use a design you’ve already approved and are reviewed by Mailr before anything mails.
The first sync starts the clock the moment you connect. Jobs and estimates that already reached your chosen status before you connected will never trigger a campaign. To test, move a fresh job into that status after connecting, then wait for the next hourly check.

Disconnect or reconnect

Disconnecting shows a confirmation titled “Disconnect JobNimbus?”: “Lead sync and campaign triggers through this connection will stop, and the stored credentials are deleted. Your settings are kept, so reconnecting later picks up where you left off.” Your campaign history, leads and results are never deleted, and reconnecting keeps your field mappings, job-address choice and attribution window.
Mailr can’t revoke the key inside JobNimbus. If you want it fully dead, delete it in JobNimbus → Settings → API as well.

Notes & limits

  • Revenue only books for estimates whose status is Approved or Signed. If your team uses a different word for “sold” — “Won”, say, or “Accepted” — revenue will never book. Rename your status or add an Approved status so the sale is recognized.
  • Contacts and jobs without an address are skipped. Mailr can’t mail a neighborhood it can’t locate. Skipped records are counted in the sync summary rather than silently dropped.
  • If you import past work to mail older customers, Mailr pulls recent jobs in a status you choose, or recent contacts.
  • Leads Mailr delivered into JobNimbus never trigger campaigns of their own.
Still stuck? See Troubleshooting connections or contact support.