Skip to main content

Setup Guide: JobNimbus via Zapier

How to connect JobNimbus and trigger mail from job or contact data.

A
Written by Adam Rutkowski

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

  1. In JobNimbus, click your profile icon and select Settings.

  2. Open the API tab and click New API key.

  3. Under Description, choose Zapier from the dropdown, and assign an Access Profile with Settings access.

  4. Click Save, then copy the generated key — you'll paste this into Zapier in the next step.

Step 2: Connect JobNimbus inside Zapier

  1. In Zapier, go to My Apps and click Add connection.

  2. Search for JobNimbus and select it.

  3. Paste the API key you copied in Step 1, and click through to authorize.

  4. 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: Refine the trigger with conditions (optional, recommended)

JobNimbus lets you add conditions directly to the automation it created for your Zap, so you don't have to rely on Zapier filters alone:

  1. In JobNimbus, go to Settings > Automations.

  2. Find the automation tied to your Zap (named something like "Zapier trigger").

  3. Open its action menu and select Edit, then + Add Condition.

  4. Add the condition that should gate the mailing — for example, only fire if Status equals a specific completed milestone, or Job Type equals a specific trade.

  5. Save. From now on, the Zap only fires when both the trigger event and your condition are met.

Step 7: Test, then go live

  1. Run Zapier's test step and confirm the sample recipient (or radius-mail pin address) shows up correctly in LettrLabs.

  2. Publish the Zap.

  3. 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.

Did this answer your question?