JobNimbus connects to LettrLabs through Zapier. If you haven't set up the LettrLabs side of Zapier yet, start with Setup Guide: Zapier first; this guide picks up from there and focuses on the JobNimbus-specific pieces.
Before you start
A LettrLabs API key and an Integration Order created for Zapier (see Setup Guide: Zapier, Steps 1–2, if you haven't done this yet).
A JobNimbus user with access to Settings, to generate an API key for Zapier.
Knowing which JobNimbus event should trigger the mailing: a new Contact, or a Job being created/updated (e.g., marked Completed), are the two most common starting points.
Step 1: Generate a JobNimbus API key for Zapier
In JobNimbus, click your profile icon and select Settings.
Open the API tab and click New API key.
Under Description, choose Zapier from the dropdown, and assign an Access Profile with Settings access.
Click Save, then copy the generated key — you'll paste this into Zapier in the next step.
Step 2: Connect JobNimbus inside Zapier
In Zapier, go to My Apps and click Add connection.
Search for JobNimbus and select it.
Paste the API key you copied in Step 1, and click through to authorize.
Once connected, this JobNimbus account is available to any future Zap.
Step 3: Choose your JobNimbus trigger
JobNimbus's Zapier integration supports two entities as triggers:
Contact Created, Modified, or Deleted — fires on Contact-level changes. Use this for customer-facing follow-up: thank-yous, review requests, referral asks.
Job Created, Modified, or Deleted — fires on Job-level changes, including status/milestone updates. Use this for anything tied to the job itself rather than the customer relationship — most notably, job-completion neighbor mail.
Step 4: Add a LettrLabs action
Add Recipient to Integration Order — sends the Contact's name and mailing address into your Integration Order. This is the right choice for customer-facing mail.
Mail Recipients Around an Address (Radius Mail) — sends a batch of neighbors around a Job's site address, rather than mailing the customer. This is the more common pattern for JobNimbus customers.
Add Recipient to Address Book — for building a reusable list rather than an immediate send.
Step 5: Map your JobNimbus fields
For Contact-based mail: map Contact first/last name (or Display Name) and the Contact's address fields.
For Job-based Radius Mail: map the Job's site address — not the Contact's own billing/mailing address, which may be a different location.
Step 6: Filter in Zapier, not in JobNimbus (recommended)
Keep the JobNimbus trigger itself broad — Job Updated, Contact Created, whatever the base event is — and add a Filter by Zapier step right after the trigger to gate exactly when the mailing should continue (for example, only continue if Status equals a specific completed milestone, or Job Type equals a specific trade).
Why filter here instead of in JobNimbus: JobNimbus's Settings > Automations screen typically requires admin access to edit. If your filtering logic lives there, any future change — a renamed status, a new condition — means looping in whoever manages JobNimbus settings. A Filter by Zapier step keeps that logic visible and editable by whoever owns the Zap instead.
Only add a condition directly in JobNimbus (Settings > Automations, find the automation tied to your Zap, Edit > + Add Condition) for something a Zapier filter step genuinely can't express.
Step 7: Test, then go live
Run Zapier's test step and confirm the sample recipient (or radius-mail pin address) shows up correctly in LettrLabs.
Publish the Zap.
In LettrLabs, switch the automation to Active.
Want help picking your first JobNimbus trigger, or scoping a job-completion radius campaign? Reach out to our team.