Skip to main content

Connect Twain to Amplemarket

Everything for using Twain with Amplemarket: import lead lists into a Twain campaign, and export leads with Twain's copy back into an Amplemarket sequence via dynamic fields.

Twain connects to Amplemarket in both directions: pull a lead list into a Twain campaign for research and sequence writing, and push the finished leads with their copy back into an Amplemarket sequence. Both use the same API key.


Import: pull Amplemarket lists into Twain

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 queued or processing appear 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.


Export: push leads and Twain's copy into an Amplemarket sequence

The mechanic in one sentence: in Twain's export dialog you give each step's copy a variable name (e.g. email_1), and in the Amplemarket sequence step you write that same name inside double curly braces ({{email_1}}). The braces are just Amplemarket's placeholder syntax — the name between them must be character-for-character identical to the name in Twain.

Step 1: Build the sequence in Amplemarket

  • Create a sequence in Amplemarket and add your steps. Instead of message text, insert placeholders for Twain's copy, e.g. {{subject_1}} in the subject line, {{email_1}} as the email body and {{linkedin_2}} in a LinkedIn step.

  • Placeholder names may only contain lowercase letters, numbers and underscores, and they are case-sensitive: {{linkedin_2}} works, {{LinkedIn_2}} will not be filled.

  • Keep the sequence empty — don't add contacts. Contacts that are already in the sequence never receive Twain's content, and as long as any contact is missing the placeholder fields, Amplemarket blocks saving the steps.

Step 2: Launch the sequence, then pause it

  • Launch the sequence (this works with no contacts in it), then pause it immediately. While paused, nothing is sent.

  • Twain's export dialog only lists sequences that are active or paused — draft sequences don't show up there.

Step 3: Export from Twain

  • In Twain, open the campaign with messaging ready to go.

  • Click Export (or Export Leads), then choose Amplemarket. Twain reuses the API key from the import setup; if you never connected, you'll be asked for one.

  • Pick your sequence. For each step, the dialog shows a custom variable name — this is the name your Amplemarket placeholder has to use. Easiest path: type the names exactly as they appear in your sequence, just without the braces (sequence uses {{email_1}} → variable name email_1).

  • Careful with spelling: Twain converts variable names to lowercase with underscores on export. A variable named Subject 1 in the dialog arrives in Amplemarket as subject_1 — so {{subject_1}} in the sequence is correct, {{Subject 1}} is not even valid syntax.

  • If your sequence contains an email step, every exported lead needs an email address — Amplemarket rejects the export otherwise. For LinkedIn-only sequences, a LinkedIn URL per lead is enough.

  • Click Export Leads.

Step 4: Verify and launch in Amplemarket

  • Open the sequence in Amplemarket and use the Preview in each step to page through your contacts. You should see each lead's personalized subject, email body and LinkedIn message rendered in place of the placeholders.

  • Check that paragraphs and line breaks look right, add your signature settings, and only then set the sequence to active.

💡 Export tips

  • If the export fails or leads come back skipped, the first thing to check is always the names: open a lead that did arrive in Amplemarket and look at its data fields — those are the exact names your placeholders must reference.

  • Leads that are already in the sequence are skipped automatically — Amplemarket never creates duplicates within a sequence.

  • Re-exporting doesn't update leads that already exist in the sequence, and leads you removed from a sequence can't be added to it again. To send updated content, use a fresh sequence.

  • Keep the sequence paused until the preview looks right for a few leads.

Did this answer your question?