Rooflink Integration in Alivo
How Alivo settings map to Rooflink Customers, Jobs, and Events.
The Rooflink integration connects Alivo to your Rooflink account so booked inspections show up as Customers, Jobs, and calendar Events without double entry. Rooflink always creates Customer and Job records together on booking. This guide covers every setting you can configure and how each one maps to Rooflink objects.
Rooflink Objects Alivo Works With
| Rooflink Object | When Alivo Creates It | What It Holds |
|---|---|---|
| Customer | Booking | Homeowner name, phone, email, address, customer status, lead source |
| Job | Booking (always, with Customer) | Job name, notes, bid type, rep assignment, lead source |
| Event | Booking | Appointment name, start/end times, invitees, link to Job, description |
Rooflink does not support syncing a Contact alone on new lead. Customer and Job are always created as a pair when an appointment is booked.
Connection and Integration Type
API Key
Connect with your Rooflink API key (sent as the X-API-KEY header). Alivo verifies it during setup.
Integration Type
- Both. Creates Rooflink records and reads the Rooflink calendar for availability.
- Calendar Only. Reads calendar only. No Customers, Jobs, or Events are created.
- CRM Only. Creates records but does not read the Rooflink calendar.
Customer Settings
- Customer Status. The lead status applied to the new Customer in Rooflink. Required.
- Customer Notes Template. (Advanced) Customizes the notes Alivo writes on the Customer using template variables.
Rooflink Customers are always created with the Customer record type. There is no separate type selector.
Job Settings
- Bid Type. Sets the Job's bid type: Cash, Insurance, Repair, Finance, or none.
- Job Name Template. (Advanced) Custom Job name. Blank defaults to the homeowner's address.
- Job Notes Template. (Advanced) Custom notes on the Job.
Job host roles (primary rep and secondary owner) are set automatically on every booking. There is no toggle to turn off Job creation.
Event Settings
- Event Name Template. (Advanced) Custom title for the calendar Event.
- Invite Primary Host. Adds the booked event's primary host as an Event owner in Rooflink, or "None" to skip.
- Invite Secondary Hosts. Adds secondary hosts as Event owners.
- Link Event to Job. Associates the Event with the Job record. On by default.
- Event Notes Template. (Advanced) Custom description on the Event.
User Mapping
Map Alivo team members to Rooflink users. Mapped hosts appear as Event invitees and as the Job rep when assigned to a booking.
Calendar Sync
Rooflink uses All Events for calendar blocking. Every Rooflink calendar Event for a mapped user blocks their availability in Alivo. There are no additional filters for Rooflink.
Custom Field Mapping
One built-in field is available:
- Lead Source. Maps Alivo values to Rooflink lead source IDs. You must select at least one option, add notes, and set a fallback default. If nothing else matches, Alivo falls back to a lead source named "Alivo" in Rooflink.
When Data Syncs
| What Happens in Alivo | What Happens in Rooflink |
|---|---|
| Appointment booked | Customer + Job + Event created |
| Appointment rescheduled in Alivo | Event name, times, and description updated |
| Appointment canceled in Alivo | Event updated |
| Host reassigned after booking | Job rep and Event invitees updated |
| Rep checks availability | Rooflink calendar read (no write) |
Changes made only in Rooflink do not automatically sync back to Alivo.
Still have a question this didn't answer? Reach out to our support team support@alivo.ai and we'll be glad to help.