# JobNimbus (/integrations/crm-recipes/jobnimbus) ## Overview [#overview] JobNimbus can send a contact or a job to LettrLabs when a JobNimbus automation runs. LettrLabs then mails the contact, or the homes near the job. You can send JobNimbus records in two ways: * A **webhook action** in a JobNimbus automation sends each record to a LettrLabs webhook. * A **Zap** reads JobNimbus and sends each record to LettrLabs. Use a contact to mail the customer, for example a thank-you card. Use a job to mail the neighbors of the job, with [Radius Mail](/integrations/webhooks/radius-mail). ## Before you begin [#before-you-begin] * Access to **Settings** in JobNimbus. * A LettrLabs webhook with an API key. See [The LettrLabs part of each recipe](/integrations/crm-recipes#the-lettrlabs-part-of-each-recipe). ## Send JobNimbus records with an automation [#send-jobnimbus-records-with-an-automation] In JobNimbus, go to **Settings** > **Automation**, and click **Add Automation**. For the trigger type, choose **Events Based**. Select the record type and the event, for example **Job** and **Modified**. Click **Add Action**, and choose **Webhook**. Paste the LettrLabs webhook URL. Turn on **Auth**. Set the auth key to `X-API-KEY`, and the auth value to your LettrLabs API key. Save the automation. Then change one test record so that the automation runs. You're done when the test record shows on the **History** tab of the **Inbound webhooks** page. Then make the campaign, and set the webhook to **Active**. Keep the JobNimbus trigger broad, for example any job change. Choose which records mail with the filters of the LettrLabs campaign. See [Fields and filters](/integrations/webhooks/map-and-filter). ## The JobNimbus field names [#the-jobnimbus-field-names] JobNimbus sends its own field names. Match them to the mail fields in the campaign. | Record | Fields that JobNimbus sends | | ------- | --------------------------------------------------------------------------------------------------- | | Contact | `first_name`, `last_name`, `address_line1`, `address_line2`, `city`, `state_text`, `zip`, `company` | | Job | `address_line1`, `address_line2`, `city`, `state_text`, `zip`, `status_name` | The state is in `state_text`, not in `state`. For Radius Mail, match the address of the job, not the address of the contact. ## Send JobNimbus records with Zapier [#send-jobnimbus-records-with-zapier] In JobNimbus, click your profile icon, then click **Settings**. Open the **API** tab, and click **New API key**. Choose **Zapier** as the description, and copy the key. In Zapier, connect **JobNimbus** with that key. Connect Zapier to LettrLabs. See [Connect Zapier](/integrations/zapier#connect-zapier). Start a Zap with the JobNimbus trigger for a contact or a job. Add a **Filter by Zapier** step, for example to continue only when the status of the job is your completed status. Add the **LettrLabs** app as the action. Pick your Zapier campaign, and map the name and address fields. Test the Zap, then publish it. You're done when the test record shows in your Zapier campaign in LettrLabs. ## FAQ [#faq] An estimate holds no name or address. LettrLabs cannot mail it. Send the job instead. Match the `state_text` field to **State**. JobNimbus has no `state` field. Check that the auth key is `X-API-KEY`, and check the key. See [Webhook history](/integrations/webhooks/webhook-history). ## Related [#related]