Import Amplemarket Lists Into Twain

Mohamed ChahinMay 18, 20264 min read

Bring an Amplemarket lead list into a Twain campaign. Connect once with your API key, pick the list, map the fields — and the research and sequence start running on the leads your team already curates in Amplemarket.

Where to start the import

There are two places to pull Amplemarket leads into Twain. The picker and the field-mapping form are the same in both — what changes is the entry point.

  • Campaign creation. Pick Amplemarket as the lead source while you're setting up a new campaign. The list you choose lands in the new campaign and Twain immediately runs research on the leads.
  • Leads import (existing campaign). Open a campaign you've already built and click Import leads. Useful for topping up an audience, swapping to a different list, or backfilling a campaign that's running low.

The first time you pick Amplemarket on either path, Twain prompts for an API key. After that, the key is remembered for the workspace — every later import skips straight to the list picker.

Connecting Amplemarket

Amplemarket authenticates with a single API key. You generate it in Settings → API Keys inside your Amplemarket workspace, copy it, and paste it into the field Twain shows on the lead-source step.

Paste the API key Amplemarket gave you. Twain validates it before moving on to the list picker.

Two things worth knowing about the key:

  • Twain validates the key before saving it. If the key is wrong or revoked you'll see The key is invalid inline on the field; nothing gets persisted. Once it validates, the key is stored encrypted against your Twain workspace and reused for every subsequent Amplemarket action — list picker, count probes, the lot.
  • Revoking on the Amplemarket side breaks the connection. If you delete the key in Amplemarket, your next list fetch will fail. Twain notices and bounces you back to the key entry form so you can paste a fresh one — no need to disconnect and reconnect manually.

The same key powers both ends of the integration: import (this post) and export (the sequence-finished side of the workflow). One key, both directions.

Lists are the selector

Once the key is validated, Twain shows your Amplemarket lead lists. Pick one. That list — every lead currently in it — is the audience that flows into the campaign.

A few practical notes on lists:

  • The list has to be completed. Amplemarket builds lead lists asynchronously; while a list is still queued or processing it shows up in the picker but is disabled until the build finishes. Refresh once the status flips.
  • Lists cap at 20,000 leads. Twain walks the whole list on import. For most teams that's plenty; if a list is bigger, split it on the Amplemarket side first.
  • Re-imports are deduped. Re-running an import on the same list won't duplicate leads. New entries on the list since the last run come through; everything already in the campaign is skipped.

Map fields to variables

The last step before research kicks off is the mapping form. This is where you wire Amplemarket lead fields to the variables Twain uses for research and sequence generation.

The defaults cover the essentials: work email, first name, last name, LinkedIn URL, job title, company. LinkedIn URL is the one that unlocks the deep-research path — without it Twain can still draft a sequence, but with it the research has a profile to read and the output is noticeably stronger.

Past the defaults, anything stored on the Amplemarket lead is fair game. A few examples of what mapping a custom field gets you:

  • Persona-aware copy. Map a Persona or Department field and Twain can angle the sequence differently for a Head of Engineering versus an AE, on the same campaign, without you writing two campaigns.
  • Stronger research. Map an Industry, Stage, or Last contacted field and the assistant can lean on that context instead of starting from a cold web search.
  • Trigger-aware drafts. Map a recency field — last activity, last touch, deal stage change — and the sequence can reference the actual reason the lead is in scope this week.

The point is the same across every integration: the more you tell Twain at import time, the less generic the output is. Variables you map once stay attached to the lead, so the day-one sequence and the day-fourteen follow-up both work from the same context.

A small detail worth calling out: Twain remembers your mapping across imports against the same Amplemarket account. The first time you map Industry → industry on a list, every later list import in the same workspace defaults to that mapping. You can override it per-list if a particular list uses a different schema, but you won't have to redo the mapping every time.