Export Twain Leads Back To HubSpot

Mohamed ChahinMay 4, 20265 min readWatch tutorial

Send the message Twain wrote, the research it ran, and any custom variables straight back to the HubSpot contact, so SDRs and AEs work from the same context without bouncing between tools.

Why export to HubSpot

Twain does the research, drafts the messages, and builds custom variables for every lead. None of that is useful if it lives in a separate tool from the one your reps actually open every morning.

The HubSpot export pushes the work onto the contact record. Each step of the sequence, the research summary, the warnings, and any campaign-specific variables you define all become HubSpot properties. From that point on, SDRs and AEs see the same context Twain saw, in the place they already work. No copy-paste, no second tab, no "where did the email go?".

A short list of what's worth exporting:

  • Sequence steps. The actual copy Twain wrote for each touch (Step 1 through Step 5), plus the subject line.
  • Research. The deep-research summary that justified the message, so reps know why this lead, not just what to send.
  • Warnings. Mismatch flags Twain raised (wrong company size, wrong geo, wrong persona) so reps can spot risky exports before they hit send.
  • Custom variables. Anything you map to a HubSpot property: insights, challenge, focus, anything you want the rep to glance at before reaching out.

Where to find it

Open the campaign, switch to Sequence or Research, and click Export Leads at the top right. HubSpot is one of the destinations in the dropdown, alongside Google Sheets, Outreach, Apollo, and the rest of the integrations you've already connected.

Export Leads. HubSpot sits in the same dropdown as every other downstream tool.

The export is scoped to the leads currently visible in that campaign. Filter the list first if you only want to push a subset.

What gets exported

Picking HubSpot opens a mapping form. Every Twain field on the left lines up with a HubSpot property on the right. You decide which Twain output writes to which HubSpot field, and you can leave any field empty to skip it.

Export data form. Map each Twain output to a HubSpot property, leave the rest blank.

The form is grouped the way the data is grouped in Twain:

  • Sequence. Each step of the email sequence and the subject line.
  • Research. The research summary and the warnings Twain raised on the lead.
  • Lead. Per-lead variables (insights, challenge, focus, anything you set up for this campaign).

Re-exporting overwrites the previous values. If you export the same lead twice, the new run replaces whatever was on the HubSpot properties before. Treat HubSpot as the live mirror, not the archive. Whatever Twain saw on the most recent export is what the rep sees in the CRM.

How it lands in HubSpot

On the HubSpot side, every mapped field shows up as a property on the contact. Open the lead in HubSpot, click All Properties, and you'll see the full sequence, the research, and the warnings sitting next to the standard CRM fields.

HubSpot side. Twain properties on the contact, ready to read or pipe into a workflow.

From here, two things become possible.

First, your reps stop context-switching. The next email is right there on the record. So is the reasoning behind it. So is the warning if the lead doesn't fit the campaign.

Second, the data is now native to HubSpot, which means HubSpot workflows, lists, and reports can use it. Build a list of leads where Warning Twain is non-empty. Trigger a Slack ping when Twain Step 1 is set. Filter dashboards by Twain Research length. Once the data is in HubSpot, it behaves like any other property on the contact.