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 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. Generate it in Settings → API Keys inside your Amplemarket workspace, then 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 — nothing gets persisted. Once it validates, the key is stored encrypted against your Twain workspace and reused for every subsequent Amplemarket action.
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.
Picking a list
Once the key is validated, Twain shows your Amplemarket lead lists. Pick one — every lead currently in that list flows into the campaign.
A few things to keep in mind:
The list has to be completed. Lists that are still
queuedorprocessingappear in the picker but are disabled until the build finishes. Refresh once the status flips.Lists cap at 20,000 leads. If a list is bigger, split it on the Amplemarket side first.
Re-imports are deduped. Running the same list again won't create duplicates. New entries since the last run come through; leads already in the campaign are skipped.
Mapping fields to variables
The last step before research starts is field mapping — wiring 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 most important one — without it Twain can still draft a sequence, but with it the research has a real profile to work from and the output is noticeably stronger.
Beyond the defaults, any field stored on the Amplemarket lead is fair game. A few examples:
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.
Stronger research. Map Industry, Stage, or Last contacted 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.
Twain remembers your mapping across imports against the same Amplemarket account. The first time you map a field, every later import in the same workspace defaults to that mapping. You can override it per list if a particular list uses a different schema.