Leap Integration in Alivo
How Alivo settings map to Leap Customers, Jobs, Stages, and Appointments.
The Leap integration (also known as JobProgress) connects Alivo to your Leap account so booked inspections create Customers, Jobs, and Appointments in Leap automatically. Leap is built for roofing, siding, and remodeling contractors, and Alivo maps directly to its Customer-Job-Appointment model. This guide explains every setting and how it maps to Leap objects.
Leap Objects Alivo Works With
| Leap Object | When Alivo Creates It | What It Holds |
|---|---|---|
| Customer | New lead (optional) or booking | Name, phone, email, address, notes, residential/commercial flag |
| Job | Booking (if Create a Job is on) | Trade, description, linked to Customer |
| Stage | Booking (if Default Stage is set) | Workflow stage applied to the Job after creation |
| Appointment | Every booking | Title, times, location, assigned user, linked Customer and Job |
Connection and Integration Type
API Key
Connect with your Leap API key from Partner Account → API Keys in Leap.
Integration Type
- Both. Creates Leap records and reads the Leap calendar for availability.
- Calendar Only. Reads calendar only. No Customers, Jobs, or Appointments are created.
- CRM Only. Creates records but does not read the Leap calendar.
Configuration Settings
- Create a Job in Leap. When on (default), Alivo creates a Job on every booking. When off, only a Customer and Appointment are created.
- Trade. The Leap trade applied to new Jobs (for example, Roofing). Required when Create a Job is on. Pulled from your Leap company's trade list.
- Default Stage (optional). A Leap workflow stage applied to the Job immediately after creation (for example, "Lead" or "Appointment Set").
- Sync contacts on every new lead. Creates or updates a Leap Customer as soon as a lead arrives, before any booking.
User Mapping
Map Alivo team members to Leap users. The mapped host is assigned as the Appointment's user_id when an inspection is booked.
Calendar Sync
Leap uses All Events for calendar blocking. All non-completed Appointments for mapped Leap users block their availability in Alivo. There are no per-type filters like Jobber.
Custom Field Mappings
The Custom Fields step offers five mapping types. Here is what each one does during sync:
| Mapping in Alivo | Leap Field | Applied During Sync? |
|---|---|---|
| Contact Type (Residential / Commercial) | is_commercial on Customer |
Yes |
| Lead Source | referred_by_type |
No (configured in UI, not written during sync) |
| Job Type | Trades | No (use the Configuration Trade dropdown instead) |
| Job Status | Workflow stages | No (use Configuration Default Stage instead) |
| Work Type | Work types | No |
Any audience custom field values that are not mapped to a specific Leap field are compiled into the Customer note along with the conversation summary and a link back to Alivo.
When Data Syncs
| What Happens in Alivo | What Happens in Leap |
|---|---|
| New lead (sync on new lead is on) | Customer created or matched |
| Lead details enriched after arrival | Customer name, phone, and email updated |
| Appointment booked | Customer → Job (optional) → Stage (optional) → Appointment created and assigned |
| Appointment canceled in Alivo | Appointment title annotated with cancel reason |
| Appointment rescheduled in Alivo | Appointment times updated, title annotated |
| Host reassigned after booking | Appointment user assignment updated |
Keep in mind: For Leap, the Configuration Trade and Default Stage dropdowns control Job creation. The Job Type and Job Status options in the Custom Fields step are for reference and organization in Alivo but do not drive the sync. Use Contact Type if you need Residential vs. Commercial set on the Customer.
Still have a question this didn't answer? Reach out to our support team support@alivo.ai and we'll be glad to help.