Use HubSpot Conversation History In Twain

Mohamed ChahinMay 3, 20265 min readWatch tutorial

Your team has been talking to these prospects for months. Twain can read what HubSpot already has on them (emails, calls, notes, meetings) and use it to write the next message, so follow-ups pick up where the thread left off instead of starting cold.

Preview

Nolan Ong
GTM Engineer @ Korus GTM: Your Partner in Allbound GTM Orchestration🎵 Scalable Outbound Growth
Warning
The lead's company size (1-10 employees) is below Twain's target of companies with at least 25 employees
Insights
Clay alumnus, AI GTM orchestration, automates 80% sales tasks. Nolan Ong's past participation in Clay Bootcamp shows he understands Clay, a platform for lead generation. Korus GTM uses an "AI tech stack" and offers fully outsourced solutions to clients to reduce operational costs. Korus GTM specializes in "Allbound GTM Orchestration" to unify fragmented data and drive predictable revenue growth.
Challenge
Integrating disparate GTM tools and systems. Given Nolan's role as a GTM Engineer, they most likely encounter difficulties in integrating disparate Go-to-Market tools and systems. Each tool often has its own API, data structures, and limitations, making it complex to create seamless and robust data flows for automated workflows and personalized outreach campaigns.
Tasks
Implement and optimize GTM tech infrastructure. Given Nolan's title as GTM Engineer at Korus GTM, a company focused on orchestrating Go-to-Market strategies, they are most likely responsible for designing, implementing, and optimizing the technical aspects of marketing and sales automation workflows.
Focus
Configuring and integrating GTM tech stacks. Given Nolan's role as a GTM Engineer at Korus GTM and the company's core offering of building and managing GTM engines, a significant portion of their work involves configuring and connecting various sales and marketing technology platforms to create cohesive and automated workflows for client campaigns.
Career
Nolan Ong transitioned into a GTM Engineer role at Korus GTM in February 2025, after founding Noc Marketing for over two years. This career change followed their participation in the Clay Bootcamp in late 2024 to early 2025.
Company
Korus GTM — Korus GTM helps businesses orchestrate their Go-to-Market (GTM) strategy. The company transforms fragmented efforts and data into a unified system to drive predictable revenue growth. Korus GTM specializes in building and managing GTM engines.
Size
1-10
Website
korusgtm.com
Job title
GTM Engineer
Location
Malaysia
History
Replied to a follow-up email 12 days ago asking how Twain handles research for Clay-enriched lists. Booked a discovery call 1 month ago — walked through the Allbound engine Korus is building for clients. Forwarded a Korus teammate (Head of Ops) into the thread 5 weeks ago to evaluate the integration story. Asked about pricing tiers for agencies running multi-tenant outbound 2 months ago.

Where to enable it

Conversation history is opt-in. There's no global switch. You turn it on in the place where you actually need it.

  • Campaign creation. The HubSpot import step has an Import conversation history toggle right next to the field-mapping options. Flip it on and every lead in that campaign comes in with their HubSpot timeline.
  • Standalone leads import. Same toggle, on the modal you use to add HubSpot contacts to an existing campaign. Use it when you want to backfill context without rebuilding the campaign.
  • Workflows. HubSpot nodes (HubSpot Import and HubSpot Sync) have the same toggle. Once it's on, every workflow run pulls fresh history.
Campaign creation. The toggle sits on the HubSpot leads step.
Standalone leads import. Backfill an existing campaign with the same toggle.
Workflow node. Set the toggle once, every run uses it.

For workflows, treat the toggle as a setting, not a one-off action. Whatever you save on the node is what every future run uses, including scheduled and trigger-based runs nobody is watching in real time. Change your mind later, edit the node once, and every run after that picks up the new behaviour.

The first time you turn the toggle on, Twain checks the HubSpot permissions already on your connection. If anything is missing, you'll be asked to reconnect HubSpot and approve the extra access. Until that's done, conversation history is paused for that integration and nothing partial is brought in.

How to validate it

Once a lead is imported with conversation history on, the result lands directly on the lead score card (the same component shown in the Preview above). Look for the History row near the bottom.

  • A filled-in History row means Twain read the contact's HubSpot timeline and the assistant will use it on the next draft. Hover the row to expand the full summary. Each line is one event, most recent first.
  • An empty History row usually means one of three things: the contact has no HubSpot activity yet, the toggle was off when the lead was imported, or the HubSpot connection is missing the extra access we asked for above. Re-importing after flipping the toggle on (or reconnecting HubSpot) fills the row in.

The fastest way to confirm everything is wired up before launching a campaign: import five test leads with conversation history on, open the lead score card for each, and check the History row reflects what your team actually has in HubSpot.

What data we collect

Twain reads the four kinds of HubSpot activity that count as conversation, and turns them into a short summary the assistant can use. Nothing is written back to HubSpot. The summary stays private to your Twain workspace.

  • Emails. Both sides of the thread, so the assistant knows which messages came from your team and which came from the prospect.
  • Calls. What the call was about, the outcome, and when it happened.
  • Meetings. Agenda, notes, and outcome.
  • Notes. Free-form context your reps captured outside of email or calls.

We pull the most recent activity for each type, sort by recency, and turn it into the bulleted summary you see in the History row. A prospect's reply counts the same as your team's outreach. Both belong in the timeline.

Lifecycle stage changes, system-generated workflow events, and other non-conversational HubSpot activity are left out on purpose. They add noise without helping the assistant write a better message.