Skip to content

Integrations

HubSpot Loss Runs With LossRunReports

LossRunReports works with HubSpot through file export and import plus our REST API. Export companies from HubSpot, map the columns once and send loss run requests. Summaries download as PDF or XLSX, and Agency and Enterprise plans add webhooks and a REST API to update HubSpot records automatically.

Webhook payload with the loss summary totals sent from LossRunReports to an agency management system
Underwriter reviewing a five-year loss summary chart and claims table on a monitor, carrier loss runs stacked on the desk

What moves between HubSpot and LossRunReports

LossRunReports connects to your CRM by export file with saved column mappings, plus our REST API and webhooks. It is not a certified partner app or a native connector.

Company import from a HubSpot export with saved column mappings for client name, FEIN, lines of coverage, policy numbers, prior carriers and expiration dates

Webhooks when a loss run arrives or a summary is ready

REST API for claim totals and loss ratio to write into company properties

PDF and XLSX summaries for the company record

Set up HubSpot loss run requests

  1. 1

    Export companies

    Export a HubSpot company view with the policy columns to CSV or XLSX.

  2. 2

    Map columns

    Match client name, FEIN, lines, policy numbers, prior carriers and expiration dates once.

  3. 3

    Send requests

    Request loss runs for the companies up for renewal.

  4. 4

    Update HubSpot

    Attach the PDF summary, or use webhooks and the REST API on Agency and Enterprise to update properties.

Columns LossRunReports maps

Map them once. The mapping is saved and reused for every later export.

FieldUsed for
Client nameNamed insured on the request and the letter of authority
FEINMatching at the carrier, especially for workers comp
Lines of coverageWhich loss runs to request
Policy numbersEvery term the carrier must report
Prior carriersWhere each request is sent
Expiration datesRenewal queue and request timing

After import, requests follow the process in how to request loss runs, and every reply is read and reconciled by the loss run software.

From request to summary

Request center
Ridgeline Freight LLC
CarrierStatusLast action
Northfield MutualCA 4471902ReceivedOct 4
Keystone CasualtyGLP 0088213Follow-up 2 sentOct 9
Granite State CompWC 2215560AcknowledgedOct 7
Bayline SpecialtyPKG 771045SentOct 10
Crestmark IndemnityUMB 30981Draftedn/a
Letter of authority signed by D. Alvarez, Oct 1Attached to all 5
Five-year loss summary
Ridgeline Freight LLC
9.7%
2021
48.4%
2022
15.2%
2023
43.4%
2024
22%
2025

5-yr loss ratio

27.7%

Frequency

2.4 / yr

Open reserves

$61,500

HubSpot loss run questions

Is this a HubSpot marketplace app?

No. LossRunReports connects through exports, our REST API and webhooks.

Can HubSpot workflows start a loss run request?

Yes, a workflow can call our REST API on Agency and Enterprise plans to start a request.

Where are policy numbers stored in HubSpot?

Wherever your team keeps them, usually custom company properties. Include them in the export.

See your own loss run read in under a minute

Upload one carrier report or use our sample. No account needed for the first read.