Sync Flivara proposals to HubSpot deals — keep your CRM always up to date.
Connect Flivara to HubSpot and eliminate double-entry between your proposal tool and CRM. Proposal events automatically update HubSpot deal stages, contact records, and activity timelines so your sales data is always accurate.
In Flivara, go to Settings → Integrations → HubSpot and click "Connect HubSpot". You will be redirected to HubSpot's OAuth authorization page. Select the correct HubSpot portal from the dropdown and click "Connect App".
You need HubSpot Super Admin or CRM Administrator permissions to install the Flivara integration.
After connecting, map your HubSpot deal stages to Flivara proposal statuses. Recommended: Proposal Sent → "Proposal Presented", Proposal Viewed → "Decision Maker Bought-In", Proposal Accepted → "Closed Won", Proposal Expired → "Closed Lost".
Choose whether Flivara should create new HubSpot contacts and companies from client intake data, or only update existing records. Set the matching logic: match by email address (recommended) or by company domain.
Enable automatic deal amount syncing. When a proposal is accepted, Flivara updates the HubSpot deal "Amount" property with the final accepted proposal value, keeping your pipeline revenue accurate without manual updates.
Toggle which Flivara events are logged to the HubSpot deal and contact timeline: proposal created, sent, viewed, signed, and payment received. Each logged event includes a timestamp and a link back to the proposal in Flivara.
In HubSpot, build workflows triggered by the "Proposal Signed" deal property set by Flivara. Common use cases: auto-enrol new clients in an onboarding email sequence, notify the account manager via HubSpot task, or update the contact lifecycle stage to "Customer".
A sales rep sends a Flivara proposal to a HubSpot contact in the "Proposal Requested" pipeline stage.
Flivara instantly moves the HubSpot deal to "Proposal Presented". When the client opens the proposal, it advances to "Decision Maker Engaged". On signing, it moves to "Closed Won" and triggers the onboarding workflow — all automatically.
A new lead completes the Flivara client intake form with their contact details and company information.
Flivara creates a new HubSpot contact and company, a deal in the "New Lead" stage, and logs the intake responses to the contact timeline — giving the sales team full context before their first call.
A VP of Sales reviews the HubSpot pipeline for the month-end forecast.
All deal amounts reflect exactly what was quoted in Flivara. No discrepancy between the proposal tool and CRM. Closed Won deals show the final accepted value including any upsells the client toggled in the proposal.
Verify the stage mapping is configured for the correct HubSpot pipeline. Flivara maps to a single default pipeline — if you have multiple pipelines, confirm the correct one is selected in Settings → Integrations → HubSpot → Pipeline Mapping.
Duplicates occur when the matching logic cannot find an existing record. This usually happens if the client email differs from what's in HubSpot. Enable "Match by Company Domain" as a secondary lookup to reduce duplicates.
Activity logging only applies to proposals created or updated after the integration was connected. Flivara does not back-fill historical data. Send a new test proposal to trigger the first sync event.
Confirm that the Flivara property "Proposal Status" exists on the HubSpot Deal object — it is created automatically when Flivara first syncs a deal. In HubSpot's workflow editor, make sure the trigger condition reads "Proposal Status is equal to Signed" (exact match).
