What does Karumi send to HubSpot after a demo?
Short answer
After a demo, Karumi finds the visitor's HubSpot contact by email, or creates it, and fills Karumi properties: a summary, an intent score from 0 to 5, whether they asked to talk to your team, the full transcript, a recording link, the session type and whether a demo happened. You can map more fields, and recap emails are logged on the contact's timeline.
When a demo ends, Karumi finds the visitor's contact in HubSpot by email, or creates it, and fills a set of Karumi properties on it: a summary of the conversation, an intent score from 0 to 5, whether they asked to talk to your team, the full transcript and a link to the recording. If Karumi sends the visitor a recap email, that email shows up on the contact's timeline too.
Your rep opens the contact and knows what happened in the demo without watching it. Your workflows can act on it the moment it lands.
This article lists every field Karumi writes, shows what a contact looks like after a demo, and explains how to set it up.
Which fields does Karumi fill in HubSpot?
These are the contact properties Karumi writes after a demo. The first time it syncs, Karumi creates the ones that don't exist yet in your portal, inside the Contact information group, so you don't have to build them by hand.
| HubSpot property | What it holds | Written by default |
|---|---|---|
| Email (email) | The visitor's email. Karumi uses it to find the contact | Yes |
| Karumi Summary (karumi_summary) | A short written summary of the demo: what they wanted, what they saw, what they asked | Yes |
| Karumi Intent Rate (karumi_intent_rate) | A score from 0 to 5. A 5 is a hot lead, the lowest scores are visits that barely started | Yes |
| Karumi Asked Team To Contact (karumi_asked_team_to_contact) | Yes when the visitor asked for someone from your team to get in touch during the demo | Yes |
| Karumi Transcript (karumi_transcript) | The full conversation, word for word, cut at 60,000 characters | Yes |
| Karumi Video Link (karumi_video_link) | A link to the session in Karumi, with the recording, transcript and insights | Yes |
| Karumi Session ID (karumi_session_id) | The session's ID, to match the contact with the session in Karumi | Yes |
| Karumi Session Type (karumi_session_type) | demo_call for a video demo, chat for a chat | Yes |
| Karumi Demo Started (karumi_demo_started) | true when the visit reached a demo, false for a chat that never became one | Yes |
| Website (website) | The domain of the visitor's email, skipped for Gmail and other free providers | Yes |
| Message (message) | A copy of the summary, unless you map this field to something else | Yes |
| Karumi Audience Name, ID and URL | The audience (campaign link) the visitor came through | When mapped |
| Karumi Chat CTAs Clicked / Skipped | Which chat buttons the visitor clicked or dismissed, like "book a demo" | When mapped |
| Karumi Recap Email Sent At / Subject | When the recap email went out, and its subject line | When a recap is sent |
The email address is the key. A visit with no email (no form filled in, nothing shared in the conversation) isn't synced, because there is no contact to match.
What else can I send to HubSpot?
The table above is the default. You can also map other things Karumi knows about the session to any contact property in your portal, standard or custom:
- What happened in the demo. Which goals the visitor reached, how much they talked, which chat buttons they clicked, whether a chat turned into a video demo.
- Where they came from. Audience, country, city and device.
- Who they are. Job title, seniority, LinkedIn profile, company name, industry and headcount, when the visitor's company is enriched.
- What they told you. Answers to the form on your start page, field by field.
- What you asked Karumi to look for. Custom insights you define, like "current tool", "team size" or "main use case". Karumi pulls the answer from the conversation and writes it to the property you choose.
So if your sales team already works from a "Competitor" property, Karumi can fill it from what the buyer said in the demo instead of a rep typing it in after a call.
Does Karumi create new contacts or only update existing ones?
You choose. There are two settings, and both are on by default:
- Create contacts. If no contact has that email, Karumi creates one.
- Update existing contacts. If the contact already exists, Karumi writes the Karumi fields on it.
Karumi only writes the fields in the table and the ones you mapped. Lifecycle stage, owner, deals and everything else in the record stay as they are.
When does the data reach HubSpot?
After the session ends and Karumi has analyzed it. The analysis is what produces the summary, the intent score and the answer to "did they ask to talk to the team?", so the sync waits for it. The contact is updated in one write, which means a workflow never sees a half-filled record.
How does the recap email show up in HubSpot?
If you use Karumi's recap email, the email Karumi sends the visitor after the demo, Karumi logs it on the contact in two ways:
- On the timeline, as an email sent to the contact, with the subject and body. Your rep sees exactly what the buyer received. It is logged as outgoing, so HubSpot doesn't mistake it for a reply from the buyer.
- As two properties, Karumi Recap Email Sent At and Karumi Recap Email Subject. A workflow can start when a date property is filled and wait a set time after it, which is much harder to do from a timeline entry. These two are what you build automation on. For example: three days after the recap, if the contact hasn't booked a meeting, send a reminder.
What can I build with these fields in HubSpot?
A few workflows teams set up in the first week:
- Route hot leads. If Karumi Intent Rate is 4 or more and Karumi Asked Team To Contact is Yes, create a task for the contact owner and notify them.
- Nurture the ones who left early. If Karumi Demo Started is false, or the intent rate is 1 or 2, enroll the contact in a nurture sequence instead of handing it to sales.
- Measure each campaign. Map the audience name and build a report of demos and hot leads per campaign link.
- Prepare the call. Put Karumi Summary on the contact's sidebar so the rep reads it before dialing.
Does Karumi read from HubSpot too?
Yes, if you allow it. Before a demo starts, Karumi can look up the visitor's contact and give the agent the fields you allow, such as company, lifecycle stage or open deals. The agent then knows if it's talking to a new prospect or a customer of two years, and opens the conversation accordingly.
Karumi can also read the contact owner, so the Slack alert for a hot demo tags the rep who owns that contact instead of a channel where nobody picks it up.
How to connect HubSpot to Karumi
- In HubSpot, go to Settings › Development › Keys › Service keys and create a key with read and write access to
crm.objects.contactsandcrm.schemas.contacts. - In Karumi, open Integrations, choose HubSpot and paste the key. Test the connection.
- Let Karumi set up its properties. If the key is missing the schema scopes, Karumi tells you which ones.
- Choose whether to create new contacts, update existing ones, or both.
- Map any extra fields you want, then run a test demo with your own email and open your contact in HubSpot.
You can see the HubSpot integration and the other CRMs Karumi works with, like Salesforce and Attio, on our integrations page.
FAQ
What does Karumi send to HubSpot after a demo?
A summary, an intent score from 0 to 5, whether the visitor asked to talk to your team, the full transcript, a link to the recording, the session type and whether a demo happened. All of them land as properties on the visitor's contact, matched by email.
Which HubSpot object does Karumi write to?
The contact. It also logs the recap email as an email activity on that contact. It doesn't create or edit deals or companies.
Do I need to create the Karumi properties in HubSpot myself?
No. Karumi creates them the first time it syncs, as long as your key has the crm.schemas.contacts write scope.
Will Karumi overwrite my contact data?
It only writes the Karumi properties, plus Website and Message as listed above, and any field you mapped yourself. Nothing else on the record changes.
What happens if the visitor didn't leave an email?
Nothing is sent. Karumi needs an email to find or create the contact. The session is still saved in Karumi with its recording, transcript and summary.
Can I choose which HubSpot fields Karumi fills?
Yes. You can map any session data, form answer or custom insight to any contact property, and turn off the ones you don't want.
How long is the transcript in HubSpot?
Up to 60,000 characters, which covers most demos. Longer conversations are cut, and the full version stays in Karumi behind the video link.
Does it work with chat conversations too?
Yes. Chats sync the same way. Karumi Session Type says chat, and Karumi Demo Started tells you if the chat turned into a demo.
Does Karumi also work with Salesforce?
Yes. Karumi connects to Salesforce, Attio and other CRMs as well. This article covers HubSpot only.
