lemlist

Reach for lemlist to run multi-channel outbound campaigns (email + LinkedIn invites/DMs) end to end, and to source from its people database. It owns the full campaign lifecycle: create, sequence, add leads, monitor.

Capabilities

Guidance

• Gate activation behind enrichment/verification: only push validated contacts.
• Always resolve campaign IDs via lemlist_list_campaigns before any write.
• Add leads in batches of 10–25, then re-check lemlist_get_campaign_stats.
• Delays are in days, not seconds: delay: 2 = 2 days. Passing 172800 triggers a > 1500 days error.
• Pause the campaign before adding or updating sequence steps. lemlist_create_campaign returns state: "running" — no parameter on that endpoint creates a draft, so a brand-new campaign is not automatically safe to edit.
• Building sequence steps needs no enablement beyond a live lemlist connection — there is no per-step-type permission to switch on: while the campaign is paused or draft it sends nothing, so once the cadence is confirmed, adding steps to it — including message-bearing ones (linkedinInvite notes, linkedinSend and email bodies) — is not separately gated. lemlist_start_campaign is the call that starts sending. On a campaign that is actually sending, a step change goes live to the leads already enrolled: pause it first.
• Mutations return a web_url: always review in the lemlist UI before starting a campaign.

add_to_campaign adds one lead per call with top-level fields (no contacts:[…] array). Custom merge variables like {{personalization}} go in variables: they're set per-lead after creation, since lemlist rejects unknown names as standard lead fields.

hyreflow tools execute lemlist add_lead_to_campaign \
  --payload '{"campaign_id":"cam_abc","linkedin_url":"https://linkedin.com/in/ada","payload":{"firstName":"Ada"},"variables":{"personalization":"Loved your talk on compilers"}}'