How it works
A Twain workflow is a pipeline: a lead source feeds it, a campaign runs research and writes the sequence, and an export step pushes the finished output to wherever your reps work. The Outreach node sits at the top — it watches one or more tags in your Outreach workspace and pulls anything new it sees, on its own, forever.
The trigger is the tag. Apply a tag to a prospect in Outreach and that's what wakes the workflow up. Twain polls the tag every minute, picks up prospects that weren't there last time, runs them through the rest of the steps, and notifies the channel you've wired up when each one is ready.
Two practical points before the screenshots:
- You apply the tag, Twain handles the rest. Twain reads tags, it doesn't create them. Your existing Outreach tagging hygiene — territory, persona, intent signal, hand-raisers, whatever you use — becomes the queue.
- Tags are also the off-switch. Remove the tag from a prospect in Outreach and they stop being a candidate for that workflow. They don't get retro-removed from a campaign already running, but they're out of the new-prospect queue.
Pick the tags that trigger the workflow
The first step in the workflow builder is the Outreach trigger. Open the picker, search for the tag, click it. You can pick more than one — Twain treats them as an OR: any new prospect carrying any of the selected tags will flow through.
A couple of things to know about the picker:
- The counts are live from Outreach. They reflect prospects with that tag at the moment you opened the picker. They're a sanity check, not a frozen number.
- You can change the selection later. Twain re-uses the new tag set the next time it polls. Prospects already mid-flight finish on the rules they entered with.
Add to a campaign with research and sequence
The next workflow step is the campaign each new prospect should drop into. Pick from your drafts, decide whether the workflow should run a fresh sequence generation per prospect, and decide whether to run the expanded research pass.
The two toggles cost credits — one per generated sequence, one per expanded research — so you can tune the cost-per-lead by deciding which of the two are worth the spend for this audience. Both default on, which is what most teams keep for an audience worth the workflow setup in the first place.
A note worth calling out: the campaign you pick is itself a Twain construct. If it has a different lead source attached, that source is ignored for prospects that come in through this workflow — the workflow is the source of truth for the import once it's wired up. The campaign provides the agent, the persona, the sequence structure, and the credits, not the audience.
Export onward
The last step is where the finished output goes. The export node connects to the same destinations Twain supports anywhere else — Apollo, HeyReach, HubSpot, Instantly, La Growth Machine, Lemlist, Outreach, Salesforce. Pick the one your reps will work the lead in and map the sequence steps to the right fields on the other side.
A common pattern with Outreach-triggered workflows is to export back into Outreach — different sequence template, but the same workspace your reps already live in. That way the tag-to-tag round trip stays inside one tool from the rep's perspective: they tag a prospect in Outreach, and a few minutes later that prospect shows up in Outreach again with a Twain-generated sequence attached, ready to launch.
You don't have to export to Outreach, of course. Plenty of teams import from Outreach and export to HubSpot (so marketing keeps a sequenced touchpoint in the CRM record), or export to Salesforce (so the activity rolls up against the opportunity), or to Lemlist / Instantly (if Outreach is the source of truth but a different tool handles delivery). Pick whatever matches the actual rep workflow.
Putting it together
The end result is a workflow that runs on its own. New prospect gets tagged in Outreach → Twain notices on the next poll → adds them to the campaign → runs research → writes the sequence → exports to wherever you pointed the last step → notifies you when it's done.
Once it's active, the only thing the rep does is tag prospects in Outreach. Twain handles the import, the research, the writing, and the delivery. The workflow log is where you go to see what ran and when — useful when you're tuning the campaign or debugging a tag that shouldn't have matched.
For the import side of the same integration — campaign creation, one-off leads import, and how the tag picker behaves — see Import Outreach Prospects Into Twain.