JobNimbus Integration in Alivo
How each setting maps to JobNimbus Contacts, Jobs, and Tasks.
The JobNimbus integration lets Alivo create and update Contacts, Jobs, and Tasks in your JobNimbus account automatically. Instead of copying lead details after every call or booking, Alivo pushes them straight into JobNimbus using the record types and settings you choose during setup. This guide walks through every configuration option and explains how it maps to JobNimbus objects.
JobNimbus Objects Alivo Works With
| JobNimbus Object | When Alivo Creates It | What It Holds |
|---|---|---|
| Contact | New lead (optional) or booking | Name, phone, email, address, owners, Lead Source, contact custom fields |
| Job | Booking (if Create Job is on) | Job type, status, name, address, sales rep, dates, job custom fields |
| Task | Every booking | Appointment title, start/end times, linked Contact and Job, task owners |
Connection and Integration Type
API Key
Connect with your JobNimbus API key from JobNimbus Settings → API. Alivo verifies the key during setup.
Integration Type
- Both. Creates JobNimbus records and reads the JobNimbus calendar to block availability.
- Calendar Only. Reads calendar only. No Contacts, Jobs, or Tasks are created.
- CRM Only. Creates records in JobNimbus but does not read the calendar for scheduling.
Contact Settings
- Contact Record Type. The JobNimbus contact type Alivo uses when creating Contacts. Required.
- Contact Status. The status applied to new Contacts.
- Sync contacts on every new lead. Creates or updates a Contact as soon as a lead arrives, before any booking.
- Sync cancellations and reschedules from JobNimbus. When on, Alivo listens for changes to Tasks in JobNimbus and updates the matching Alivo appointment. You will see a webhook URL to paste into JobNimbus after saving.
Advanced Contact Options
- Contact Name Template. Controls how the Contact name is formatted using variables like first name and address.
- Host Role / Secondary Host Role. Assigns the booked event's primary or secondary host as a Contact owner in JobNimbus.
- Update Existing Contact. When a matching Contact is found by phone or email, Alivo updates notes, address, and owners instead of skipping it.
- Contact Notes Template. Customizes the notes Alivo writes on the Contact. Leave blank for the default compiled notes.
Job Settings
- Create Job. When on (default), Alivo creates a Job on every booking. When off, only a Contact and Task are created.
- Job Type. The JobNimbus record type for new Jobs. Required when Create Job is on.
- Job Status. The status applied to new Jobs.
Advanced Job Options
- Job Name Template. Custom name for the Job. Blank uses the JobNimbus default.
- Host Role. Assigns the event host as sales rep, owner, or both on the Job.
- Secondary Host Role. Assigns the secondary host as an owner on the Job.
- Link Job to Contact. Associates the Job with the Contact record.
- Add Dates to Job. Writes the appointment start and end dates onto the Job record.
- Job Notes Template. Customizes notes on the Job.
Task Settings
- Task Type. The JobNimbus task type for booked appointments. Required.
Advanced Task Options
- Task Name Template. Custom title for the Task.
- Host Role / Secondary Host Role. Assigns hosts as Task owners.
- Link Task to Contact. Associates the Task with the Contact.
- Link Task to Job. Associates the Task with the Job (when a Job exists).
- Task Notes Template. Custom description on the Task. Blank means no description.
User Mapping
Map Alivo team members to JobNimbus users. Mapped users become Contact owners, Job sales reps/owners, and Task owners depending on your Host Role settings. Mapped users' JobNimbus calendars are also read for availability.
Calendar Sync (Busy Time Blocking)
Choose which JobNimbus calendar items block a rep's availability in Alivo:
- All Events. Blocks on Jobs, Tasks, Material Orders, and Work Orders.
- Jobs, Tasks, Material Orders, Work Orders. Toggle each type individually. At least one must be on.
- Include all-day tasks. Sub-option under Tasks. When off, all-day Tasks do not block availability.
Custom Field Mappings
Three built-in choice fields map Alivo values to JobNimbus fields:
- Lead Source. Written to
source_nameon Contacts and Jobs. Required during setup. - Job Type. Written to the Job's
record_type_name. - Job Status. Written to the Job's
status_name. Options are filtered by the Job Types you selected.
You can also map JobNimbus Contact Custom Fields and Job Custom Fields (text, number, choice, and boolean types) to Alivo audience fields. Required JobNimbus choice fields need a fallback default in Alivo.
When Data Syncs
| What Happens in Alivo | What Happens in JobNimbus |
|---|---|
| New lead (sync on new lead is on) | Contact created or updated |
| Appointment booked | Contact + Job (optional) + Task created |
| Appointment rescheduled or canceled in Alivo | Task title, dates, and description updated |
| Task deleted or rescheduled in JobNimbus (inbound sync on) | Matching Alivo appointment canceled or rescheduled |
| Host reassigned after booking | Task owners updated |
Keep in mind: JobNimbus is the most configurable native integration in Alivo. The Contact, Job, and Task tabs give you fine control over record types, ownership, linking, and naming. Start with the defaults and adjust once you see how records land in JobNimbus.
Still have a question this didn't answer? Reach out to our support team support@alivo.ai and we'll be glad to help.