Before You Start

This guide is intended to walk you through common use cases and configurations for Hover’s Salesforce integration. If you have not followed the installation instructions for the integration and tested the initial connection, please refer to our installation guide.

This integration requires a special installation link and password. If you're interested in using Hover's Salesforce integration, please fill out this form and our Solutions Engineering team can validate if it's the best solution for you.

---

How the integration works

The integration is a two-way connection between Salesforce and Hover:

• Salesforce → Hover. When you create a Hover Job record in Salesforce, the integration creates the matching job (or capture request) in Hover. Changes to the assignee or note on a Hover Job are sent to Hover too.
• Hover → Salesforce. Hover sends webhook events to your Salesforce site. Each event is saved as a Hover Webhook record, and the Update Hover Job flow routes it to the right action. For example, the flow saves a structure's measurements, syncs an estimate, or retrieves a signed agreement.

Every job in Hover can hold one or more structures, such as a house plus a detached garage. Salesforce stores each structure as a Hover Model record under its Hover Job, and each structure gets its own deliverable, reconstruction state, and measurements.

Related guides

Common Workflows and Use Cases

Automatically create a Hover job for a sales rep

The most common use of the integration is to create a Hover Job automatically from another Salesforce object and assign it to the sales rep who will visit the property. The rep then opens the job in the Hover app, captures the property, and the measurements flow back into Salesforce.

We recommend using Salesforce Flow to build this into your existing sales process. This example uses an Opportunity, but the same approach works from any object, such as Lead, Work Order, or Claim.

Step 1: Add a Hover Job lookup to your object

Create a lookup field on Opportunity to Hover Job (for example, Hover_Job__c). The flow fills it in, so reps can open the Hover app and see measurements right from the Opportunity.

Step 2: Build the flow

Create a record-triggered flow on Opportunity that runs when the Opportunity reaches the stage where a site visit is scheduled. The flow should:

1. Create a Hover Job using the mapping below.
2. Update the Opportunity's Hover Job lookup with the new Hover Job's Id.

Here's a sample mapping from an Opportunity to a Hover Job:

If your property address lives in custom fields, map those instead.

The Assignee must be a Hover user. The integration creates the job in Hover under the Assignee's email address, which is what puts it in the rep's Hover app. Make sure every rep has a Hover user with the same email address as their Salesforce user. Set a Backup User Email in Custom Settings so a job is still created if a rep's email doesn't match.

Step 3: Give reps a way to open the Hover app

Add the Hover Deep Link component (hoverDeepLink) to the Opportunity record page in Lightning App Builder. Set its Hover Job ID Field API Name property to the lookup path, for example Hover_Job__r.HOVER_Job_ID__c. The component shows an Open Photo Capture in Hover button that opens the job's Photo Capture flow in the Hover mobile app, including from the Salesforce mobile app. The button works once the Hover Job ID is filled in, which happens right after the job is created in Hover.

The Hover Job's Mobile Capture Link field gives reps the same link as clickable text. You can add it to a layout or include it in a notification to the rep.

What happens next

1. The flow creates the Hover Job, and the integration creates the matching job in Hover, assigned to the rep.
2. At the property, the rep opens the job from the Opportunity and captures it with the Hover app. Hover sends the photos to its 3D reconstruction pipeline to generate measurements and other deliverables.
3. As Hover identifies each structure on the property, the integration creates a Hover Model record for it under the Hover Job.
4. When a structure finishes reconstructing, the integration writes its roof and siding measurements to that structure's Hover Model record.

Sending a capture request to a homeowner instead

The same flow can send a capture request to the homeowner, so they capture the property themselves. Set Send Connect Request to true and fill in Capturing User Name, Capturing User Email, and Capturing User Phone with the homeowner's details. Hover then texts and emails the homeowner instructions for capturing their property. The Assignee still owns the job in Hover. See the Hover Connect Request fields in the Objects and Fields Reference.

Bring measurements back to the original record

Measurements are stored per structure on Hover Model records, not on the Hover Job. To surface them on the originating record (for example, the Opportunity):

• In a flow: Trigger a record-triggered flow when a Hover Model's State changes to complete. Use the model's Hover Job lookup to find the originating record, then copy the measurements you need.
• On the page: Add the Hover Job's Hover Models related list to the originating record's page layout, or link to the Hover Job so reps can open each structure's Hover Model record.

A job with more than one structure has more than one set of measurements. Decide whether your flow should copy each structure separately, total them, or only use the primary structure.

Open the measurements PDF

Add the Hover PDF Link component to the Hover Job or Hover Model record page in Lightning App Builder. On a Hover Model page, it opens that structure's measurements PDF. The button turns on once the structure has finished reconstructing.

Support and Frequently Asked Questions

Does the integration work with suborgs in Hover?

Yes. You can assign jobs to any suborg using the Suborg Assignee field on the Hover Job object. If a job is assigned to a suborg, the assigned user needs a matching email address in Hover and the right permissions in Salesforce. To make sure suborg jobs send their webhook events back to Salesforce, turn on Enable Suborg Access on Job Create in the Custom Settings guide.

Hover jobs or connect requests aren't being created in Hover. How do I fix this?

Check the Sync Status and Last Sync Error fields on the Hover Job first. The most common cause is that the assignee on the Hover Job doesn't have a user with a matching email address in Hover. Find the assignee's email address, log in to Hover, go to your team's settings, and check for a user with the same email.

If there's no match, either create that user in Hover or change the Salesforce assignee's email address to match an existing Hover user. You can also set a Backup User Email in the Custom Settings guide so jobs still get created when the assignee isn't found.

Why is my Hover Job missing measurements?

Measurements are stored on each Hover Model record, not on the Hover Job. Open the job's Hover Models related list and check each structure. A structure's measurements are filled in once its State is complete.

Can I view or edit the integration code?

Yes! The integration is fully open source, and you can view its code under Apex Classes in Salesforce Setup. Hover can't troubleshoot or support changes you make to the integration code, and upgrading to a future version may overwrite your custom code.

I have questions about the integration, or I'm running into issues I can't resolve. Who can I contact?

Please reach out to your main Hover point of contact, your account manager, or [email protected].