Skip to main content
The HubSpot integration connects your Scanova account to a HubSpot portal via OAuth, then walks you through a guided wizard that maps a form or QR code’s submissions to a HubSpot CRM object — Contact, Company, Deal, or Ticket — so every submission becomes a HubSpot record automatically.

​
Prerequisites

  • A HubSpot account with permission to authorize new app connections for the portal.
  • A Scanova plan that includes the HubSpot integration. Without it, connecting returns a “Your plan does not include HubSpot integration” error.
  • At least one Form-builder form or QR code with a submission source (Custom Form, Feedback, RSVP, Real Estate inquiry, or Restaurant feedback) already set up, since the wizard needs something to sync from.

​
Setting up a connection

HubSpot opens as its own full page (not a side panel), because the wizard needs the room.
1

Open the HubSpot integration

From Integrations, select Add Integration, then find the HubSpot card and select Setup.
2

Connect HubSpot

Select Connect HubSpot. You’re redirected to HubSpot to authorize Scanova, then returned to the wizard. A green banner shows the connected portal ID once authorization succeeds.
3

Choose what to sync

Pick the submission source type: Forms (any Form-builder form), Custom Form Component, Feedback Form (Feedback QR Code), RSVP Form Component, Inquiry Form (Real Estate QR Code), or Feedback Form (Restaurant QR Code).
4

Select the source

Depending on the type chosen, search for and select the specific form or QR code whose submissions should sync.
5

Choose the HubSpot action

Select which HubSpot object each submission should create: Create Contact, Create Company, Create Deal, or Create Ticket.
6

Map fields

Match your source’s fields to HubSpot properties. HubSpot’s featured properties for the chosen object are pre-listed; use Add a field to map additional properties from the full catalog. Incompatible mappings are blocked inline — for example, a HubSpot number property can’t be mapped to a text field, and a date property can’t be mapped to a non-date field.
A mapping the wizard doesn’t flag as invalid but that still can’t be coerced to the HubSpot property’s type is silently dropped at sync time rather than causing an error — the inline validation exists specifically to catch this before it happens.
7

Review, test, and complete

Name the connection (used later to identify it in Active Connections), review the mapping summary, and optionally select Send test to push one sample record to HubSpot and confirm it arrives before selecting Complete setup.

​
Managing the connection

  • Disconnect (in the connected banner) stops syncing for the whole portal — every HubSpot connection tied to it stops sending data.
  • Editing an existing connection from Active Connections reopens the same 5-step wizard, prefilled.

​
What data flows where

Each time the configured form or QR code receives a new submission, Scanova sends the mapped field values to HubSpot as a new record of the chosen object type (Contact, Company, Deal, or Ticket) in the connected portal.
  • Slack — another OAuth-connected integration with its own named-rule builder.
  • Webhooks — a generic alternative if you need submission data somewhere HubSpot doesn’t cover.
  • Form management — the API behind the Forms sources this wizard syncs from.
  • Lead list management — the API behind the legacy Lead List sync sources.