Export Twain leads back to HubSpot

Mohamed ChahinMay 4, 20263 min read

Updated

Send the sequence Twain wrote, the lead details, and the research behind them 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 and drafts the messages 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. You map the sequence, the lead details, and the research, including Thesis and Strategy where the mode produced them, to 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 copy for each step, plus email subject lines.
  • Lead details. The person's role, headline, location, and company information.
  • Research. Signals and warnings, with Absent signals, Thesis, and Strategy when the lead's generation mode produces them.

Where to find it

Open the campaign and choose Export, then HubSpot. This opens the field-mapping form; choosing the destination does not send the export.

Choose HubSpot from the campaign's Export menu.

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.

The available fields follow the campaign and its generated leads:

  • Each sequence step has its own content field and, for email, a subject field.
  • Lead includes job title, headline, other roles, location, company info, company size, and website.
  • Research includes Warnings and Signals, plus the deeper outputs available from the generation mode: Absent signals, Thesis, and Strategy. Base does not produce Thesis or Strategy; High produces Thesis; Ultra produces both.

The form also shows how many leads have emails and offers Skip leads with warnings. Check the eligible count and your mappings before clicking Export Leads. Leave a mapping empty when you do not want Twain to write that field.

Map the output you need to HubSpot properties. The form shows the eligible email count before you export.

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.

Example of mapped Twain properties on a HubSpot contact. Your property names and exported fields follow the mappings you choose.

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.