Integrations
Does Roccai integrate with HubSpot?
Yes. Roccai connects to HubSpot with a private app access token and creates or updates contacts as enriched leads are captured. You map each Roccai field to a HubSpot property, so the answers behind a lead — including the options they rejected — land on the contact record itself rather than in a note nobody reads.
How the HubSpot connection works
Your sales team opens a HubSpot contact and sees what the person wants — not just that an email address appeared.
The connection needs one credential: a private app access token from your HubSpot account. Paste it into the HubSpot integration in Roccai, choose which campaigns should feed it, and pair each Roccai source field with the HubSpot property it should write to.
From then on, every enriched lead creates a contact or updates the matching one. Because the answers go into real HubSpot properties, they behave like any other contact data: filterable in lists, usable in workflows, visible on the record, and reportable.
HubSpot integration at a glance
| How it works | |
|---|---|
| What you need | A HubSpot private app access token |
| What Roccai creates | A contact — created, or updated where one already matches |
| Where the answers land | HubSpot properties you choose in the mapping table |
| Scoping | Per campaign — you pick which campaigns feed HubSpot |
| Timing | On guide submission, in real time |
| Optional extras | The decisions layer (every answer, including rejected options) and an AI summary |
What you can do with it
Build active lists on stated preference instead of inferred behaviour — everyone who said yes to one category and no to another is a list, not a guess.
Give sales the profile before the first call. The rejected options are usually the more useful half of a discovery conversation, and they are on the record before anyone picks up the phone.
Trigger existing HubSpot workflows off an enriched lead, so follow-up starts while the person is still on the site.
Attribute by channel: the campaign a guide was shared under travels with the lead, so fair leads, newsletter leads and paid-social leads stay distinguishable in HubSpot.
Frequently asked questions
How do I connect Roccai to HubSpot?
Create a private app in HubSpot, copy its access token into the HubSpot integration in Roccai, select the campaigns that should feed it, and map each Roccai field to a HubSpot property. No developer and no custom code needed.
Does Roccai create new HubSpot contacts or only update existing ones?
Both. Roccai creates a contact when the email address is new and updates the existing contact when it already exists in your portal, so a returning visitor enriches their own record rather than creating a duplicate.
Can I write Roccai guide answers to custom HubSpot properties?
Yes. The integration has a mapping table where you pair each Roccai source field with the HubSpot property it should write to — standard or custom. You are never forced to adopt Roccai's own field names.
Can I send only some campaigns to HubSpot?
Yes. Every integration is scoped to the campaigns you select. One guide running across a newsletter, a paid ad and an in-store screen can send only the campaigns you choose to HubSpot and route the rest elsewhere.
Does Roccai send preference data to HubSpot, or just the email address?
Both, if you want them. Alongside the contact fields, Roccai can send the decisions layer — every question the guide asked, the option chosen and the options rejected — plus an optional plain-language AI summary of the session.
Other Roccai integrations
Roccai also connects natively to Ortto, Mailchimp, Klaviyo, ActiveCampaign and Zapier & custom webhook. For the full list, the data that flows and the payload reference, see all Roccai integrations.
See it writing to your HubSpot