Jobber Integration in Alivo
How Alivo settings map to Jobber Clients, Jobs, Visits, Requests, and Assessments.
The Jobber integration connects Alivo to your Jobber account through a secure OAuth sign-in (no API key to copy and paste). When someone books through Alivo, the right Jobber Client and scheduled work object are created automatically. This guide covers every setting and how each one maps to Jobber objects.
Jobber Objects Alivo Works With
Jobber has two appointment flows. You choose which one Alivo uses during setup.
| Jobber Object | When Alivo Creates It | What It Holds |
|---|---|---|
| Client | New lead (optional) or booking | Name, phone, email |
| Job | Booking (Job + Visit flow) | Work order linked to the Client |
| Visit | Booking (Job + Visit flow) | Scheduled appointment with start/end times and assigned team member |
| Request | Booking (Request + Assessment flow) | Service request linked to the Client |
| Assessment | Booking (Request + Assessment flow) | Scheduled assessment with start/end times and assigned team member |
Connection and Integration Type
OAuth Connect
Instead of an API key, you connect Jobber by signing in through Jobber's authorization screen. Alivo stores the connection securely and refreshes it automatically. If the connection expires, reconnect from the Integrations page.
Integration Type
- Both. Creates Jobber records and reads the Jobber calendar for availability.
- Calendar Only. Reads calendar only. No Clients, Jobs, or Visits are created.
- CRM Only. Creates records but does not read the Jobber calendar.
Configuration Settings
- Create appointments with. Choose your Jobber workflow:
- Job + Visit (default). Alivo creates a Job and schedules a Visit on it.
- Request + Assessment. Alivo creates a Request and schedules an Assessment on it.
- Sync contacts on every new lead. Creates or updates a Jobber Client as soon as a lead arrives, before any booking. No Job, Visit, Request, or Assessment is created until an appointment is booked.
Jobber Clients are always created with the Client record type. There is no custom field mapping step for Jobber in Alivo.
User Mapping
Map Alivo team members to Jobber team members. The mapped host is assigned to the Visit or Assessment when an appointment is booked.
Calendar Sync (Busy Time Blocking)
When Integration Type includes calendar reading, choose which Jobber scheduled items block a team member's availability:
- Visits. Scheduled visits on Jobs block availability.
- Assessments. Scheduled assessments on Requests block availability.
- Tasks. Jobber Tasks block availability.
At least one type must be selected. All three are on by default.
When Data Syncs
| What Happens in Alivo | What Happens in Jobber |
|---|---|
| New lead (sync on new lead is on) | Client created or matched by phone/email |
| Lead details enriched after arrival | Client name and email updated |
| Appointment booked (Job + Visit) | Client → Job → Visit scheduled and assigned |
| Appointment booked (Request + Assessment) | Client → Request → Assessment scheduled and assigned |
| Appointment canceled in Alivo | Visit or Assessment deleted |
| Appointment rescheduled in Alivo | Visit or Assessment start/end times updated |
| Host reassigned after booking | Visit or Assessment assignment updated |
Good to know: Pick the appointment flow that matches how your team already works in Jobber. If your estimators schedule Visits on Jobs, use Job + Visit. If they work from Requests and Assessments, use that flow instead.
Still have a question this didn't answer? Reach out to our support team support@alivo.ai and we'll be glad to help.