Send LossScout leads to your CRM

LossScout sends new leads, lead updates and your team's claim activity to any system that accepts webhooks. Use n8n or Zapier to reach HubSpot, Salesforce, Pipedrive, Close and restoration platforms, or point it at your own software.

Overview

A webhook is a web address that LossScout sends a message to whenever something happens, such as a new lead in your counties or a claim moving to a new stage. Each message carries the lead's address, property details and a link back to LossScout, and can include owner contact details with their Do Not Call status.

1. Get a webhook URL from n8n, Zapier or your own system.
2. In LossScout, go to Company → Integrations, add the URL and choose what to send. Owners and admins can manage integrations.
3. Press Send test event to check the connection.

Integrations are included on every LossScout plan.

• n8n
• Zapier
• HubSpot
• Salesforce
• Pipedrive
• Close
• JobNimbus
• ServiceTitan
• Xcelerate
• DASH
• Encircle
• PSA
• Restoration Manager
• Any webhook

LossScout sends directly to n8n, Zapier or your own webhook. To get leads into HubSpot, Salesforce, Pipedrive, Close or a restoration platform, use an n8n workflow or a Zap to pass them on.

n8n

1. Add a Webhook node, set it to receive POST requests, and copy its production URL.
2. Activate the workflow, then add the URL on the Integrations page in LossScout.
3. Press Send test event and check the workflow's executions.
4. Route each kind of message to your CRM's node or an HTTP Request node.

Self-hosted n8n must be reachable from the internet over HTTPS.

Zapier

1. Create a Zap with Webhooks by Zapier as the trigger and Catch Hook as the event.
2. Copy the webhook URL Zapier shows and add it on the Integrations page in LossScout.
3. Press Send test event, then Test trigger in Zapier.
4. Add an action for your CRM, for example creating a deal in HubSpot, and map the lead's address, details and link to your CRM's fields.

Other systems

Any service that gives you an HTTPS URL to receive JSON works, including Make, Pipedream, Power Automate and your own server.

What you can send

Choose what each webhook receives. Lead messages can also be limited to certain tiers and counties.

• New leads in your counties, as they come in.
• Lead updates: address confirmed, verified on scene, owner contact found, or priority changed.
• Closed leads: merged with another report of the same fire, rejected or closed.
• Your team's claims: claimed, moved to a new stage, won or lost.
• Send to CRM: owners and admins can push any claim, with its photos and notes, into your CRM at any step.

Security and reliability

• Every message is signed with a secret that's unique to your webhook, so your system can check it came from LossScout.
• Messages that can't be delivered are retried automatically for up to 3 days.
• If a webhook keeps failing, it's switched off and your Company page shows a warning.
• The Integrations page shows recent messages, what was sent and the result, with a button to send any of them again.

Requirements

• The URL must start with https://, use the standard port (443) and be reachable on the public internet.
• Redirects aren't followed, so use the final URL.
• Respond within 10 seconds.
• Each company can have up to 10 webhooks.