Objects and Field References
Objects and Fields Reference
The integration adds several custom objects to your Salesforce org. This guide covers the four core objects that handle the webhook connection, incoming events, jobs, and structures.
The integration also installs objects for estimates and inspections: Hover Estimates (Hover_Material_List__c), Estimate Line Items (Hover_Estimate_Line_Item__c), Adjustments (Hover_Adjustment__c), and Hover Inspections (Hover_Inspection__c). Those are covered in their own guides.
Hover Webhook Config (Hover_Webhook_Config__c)
Hover_Webhook_Config__c)This object connects Hover's webhooks to Salesforce. You only use it during setup. When you create a record, it registers your Digital Experience site (set up during installation) as a webhook in Hover. It then listens for Hover's first webhook event, reads the verification code, and verifies the webhook so the integration can start receiving events.
| Field Name | Description | Notes |
|---|---|---|
| Hover Webhook Config Name | The name of your webhook | |
| URL | Your webhook's URL | The base URL should match your Digital Experience site |
| Content Type | Content type of the webhook | Used to create the webhook in Hover. Should always be json |
| Hover Webhook ID | The ID of the webhook in Hover | |
| Verification Code | Code used to verify the webhook in Hover | Fills in automatically after the record is created |
Hover Webhook (Hover_Webhook__c)
Hover_Webhook__c)Each record is one raw webhook event sent by Hover. Every event Hover sends is saved here, and the Update Hover Job flow evaluates each one. See Webhook Events and the Update Hover Job Flow for how each event is handled. For the full list of webhook events, see Hover Webhook Events.
| Field Name | Description |
|---|---|
| Hover Job Name | Always "webhook" |
| Content Available | Static value (always 1/true) |
| Event | The event type |
| Hover Job | Lookup to the related Hover Job |
| Job Estimated Hours to Completion | Hover's processing time estimate |
| Job External Identifier | The job's external ID in Hover (typically the Hover Job record Id) |
| Job ID | Hover's job ID |
| Model ID | New in v2.0.0. Hover's ID for the structure (model) referenced by a model event |
| Capture Request ID | New in v2.0.0. Hover's ID for the capture request referenced by the event |
| Request | The full webhook event, in JSON |
| State | The event's state (depends on the event type) |
| Webhook ID | Hover's webhook ID |
| Verification Code | Verification code from the webhook-verification-code event |
| Hover Material List ID | ID of the estimate referenced by the event |
| Hover Inspection ID | ID of the inspection referenced by an inspection event |
| Hover Proposal ID | ID of the proposal referenced by a signature request event |
Hover Job (HOVER_Job__c)
HOVER_Job__c)Holds the data for one Hover job or capture request. When you create a Hover Job, the integration creates a matching job in Hover that waits for photo capture. Once the property is captured, Hover identifies each structure, and the integration creates a Hover Model record for each one under the Hover Job.
Fields for job and capture request creation:
| Field Name | Salesforce Field Name | Description | Notes |
|---|---|---|---|
| Hover Job Name | Name | Job name | |
| Hover Job ID | HOVER_Job_ID__c | Job ID in Hover | |
| Location Line 1 | Location_Line_1__c | Primary address line | Required |
| Location Line 2 | Location_Line_2__c | Secondary address line | |
| City | location_city__c | Property city | |
| State (Region) | location_region__c | Property state | |
| Postal Code | location_postal_code__c | ZIP code | |
| Country | location_country__c | Country | |
| Deliverable | Deliverable_ID__c | Deliverable requested for the job | Required |
| Assignee | Assignee__c | Salesforce user who owns the job in Hover (User lookup) | User must have a matching email in Hover |
| Suborg Assignee | Suborg_Assignee__c | Hover suborg user | Suborg structure only |
| Suborg Assignee ID | Suborg_Assignee_ID__c | Suborg user's ID | Suborg structure only |
| Customer Email | customer_email__c | Homeowner email | |
| Customer Phone | customer_phone__c | Homeowner phone |
Fields for Hover Connect Requests:
| Field Name | Salesforce Field Name | Description | Notes |
|---|---|---|---|
| Send Connect Request | Send_Connect_Request__c | Whether to send a connect request | True = connect request; false = job creation |
| Capturing User Name | Capturing_User_Name__c | Person capturing the property | Required for a capture request |
| Capturing User Phone | Capturing_User_Phone__c | Capturing user's phone number | Required for a capture request |
| Capturing User Email | Capturing_User_Email__c | Capturing user's email | Required for a capture request |
| Capture Request ID | Capture_Request_ID__c | Connect request ID | Filled in when the request is created |
| Connect Status | Connect_Status__c | Request state | Updated when the request is created or changes |
| Connect Identifier | Connect_Identifier__c | Unique identifier in the capture request link | |
| Connect Link | Connect_Link__c | Full capture request link | Can be resent to homeowners |
Status and sync fields:
| Field Name | Salesforce Field Name | Description |
|---|---|---|
| Reconstruction State | State__c | The job's state in Hover's processing pipeline. Renamed from "State" in v2.0.0. |
| Sync Status | Sync_Status__c | Result of the last push to Hover: Synced, Push Failed, Assignment Failed, or Backfilled |
| Last Sync Error | Last_Sync_Error__c | The status code and response from Hover when a push fails |
Other fields worth noting:
| Field Name | Salesforce Field Name | Description |
|---|---|---|
| Mobile Capture Link | Mobile_Capture_Link__c | Link that opens the job's Photo Capture flow in the Hover mobile app, including from the Salesforce mobile app |
| Hover Deep Link | Hover_Deep_Link__c | Link that opens the job's Photo Capture flow in the Hover mobile app |
| Hover Proposal PDF | Hover_Proposal_PDF__c | Link to the signed proposal PDF, filled in once the proposal is signed |
| Hover Note | Hover_Note__c | Note text to create or update on the job in Hover |
| Hover Note ID | Hover_Note_ID__c | ID of the note in Hover, filled in after the note is created |
| Parent Org ID | Parent_Org_ID__c | Parent org ID, set at creation when suborg sharing is turned on |
Measurement fields on Hover Job: The roof and siding measurement fields on Hover Job are no longer updated as of v2.0.0. Measurements are stored per structure on Hover Model.
Hover Model (Hover_Model__c)
Hover_Model__c)New in v2.0.0. Each record is one structure (model) on a Hover job, such as a house or a detached garage. A Hover Job can have several Hover Models, listed in its Hover Models related list. The integration creates and updates Hover Models automatically from Hover's model webhook events. You don't need to create them yourself.
| Field Name | Salesforce Field Name | Description |
|---|---|---|
| Hover Model Name | Name | The structure's name in Hover |
| Hover Job | Hover_Job__c | Lookup to the parent Hover Job |
| Hover Model ID | Hover_Model_ID__c | The structure's ID in Hover |
| State | State__c | The structure's reconstruction state in Hover. Measurements fill in once this is complete |
| Deliverable | Deliverable__c | The structure's deliverable. In Hover, deliverables are set per structure, not per job |
| Failure Reason | Failure_Reason__c | Hover's reason the structure needs attention. Can be filled in even when the state is complete |
Each Hover Model also holds the full set of roof and siding measurement fields for its structure. A Roof Only structure fills in only the roof fields.
Updated about 18 hours ago