Webhook Events and Update Hover Job flow
Webhook Events and the Update Hover Job Flow
Hover sends webhook events to your Salesforce site whenever something changes on a job. The integration saves each event as a Hover Webhook record (Hover_Webhook__c), and the Update Hover Job flow evaluates it.
Update Hover Job flow
The Update Hover Job flow runs whenever a Hover Webhook record is created. It routes on the record's Event value (and, for some events, its State value) and takes the following actions:
Event (Event__c) | Condition | Action |
|---|---|---|
model-created | — | New in v2.0.0. Creates a Hover Model for the new structure under its Hover Job, then syncs the structure's name, state, and deliverable from Hover |
model-state-changed | — | New in v2.0.0. Updates the Hover Model's state and syncs its name and deliverable. When the state is complete, also retrieves the structure's measurements and writes them to the Hover Model |
job-state-changed | — | Updates the Hover Job's Reconstruction State |
capture-request-state-changed | — | Updates the connect (capture) request status on the Hover Job |
webhook-verification-code | — | Reads the verification code and verifies the webhook |
deliverable-change-request-state-changed | State = complete | Updates the Hover Job's deliverable (for example, when a capture-only job is upgraded to Roof Only or Complete) |
project-management-production-list-created | — | Creates an estimate in Salesforce when the Auto Create Estimate custom setting is on |
project-management-production-list-manual-sync | — | Syncs the estimate into Salesforce and marks it "Synced to Salesforce" in Hover. If the estimate is already locked in Salesforce, the sync is skipped |
inspection-state-changed | State = complete | Retrieves inspection data into Salesforce. Changed in v2.0.0: previously triggered at submitted. |
project-management-signature-request-state-changed | State = signed | Retrieves the signed proposal PDF link and saves it to the Hover Job's Hover Proposal PDF field |
Events not listed here are still saved as Hover Webhook records, but the flow takes no action on them.
What changed in v2.0.0
- Measurements are no longer retrieved when a job reaches
complete. They're retrieved for each structure when its Hover Model reachescomplete. - The
HOVER_Job_Complete__eplatform event is no longer published. To act when measurements arrive, trigger your automation on a Hover Model's State changing tocomplete.
Customizing the flow
Don't edit the Update Hover Job flow's core logic. Any changes you make, including additions, may be overwritten when you upgrade the integration. To add your own behavior, build a separate flow that triggers on the Hover Webhook, Hover Job, or Hover Model object instead.
Troubleshooting webhooks
If a webhook event can't be processed, the integration publishes a Hover Exception platform event (HOVER_Exception__e) with a description of the error instead of failing silently. If you expect a change from Hover that never shows up in Salesforce:
- Check for a Hover Webhook record with the expected Event and Job ID. If there isn't one, Hover didn't reach your site. Check the webhook registration on your Hover Webhook Config record.
- If the record exists, confirm that the guest user of your Salesforce Site and the Hover permission set can access every Apex class whose name starts with
Hover.
Updated about 18 hours ago

