Skip to main content
Use this guide if your team already sends with lemlist, or if you want your agent to connect to the sequencer with OAuth instead of an API key. lemlist sends the campaign from your mailboxes. AgentLinkOps keeps the prospect and confirms the link. Each lemlist lead carries its AgentLinkOps watch id, so outcomes come back to the right prospect. Starting from nothing? Hunter costs less and finds addresses too.

​
What it costs

From lemlist’s pricing page, checked October 20, 2026: the Email plan starts at $69 a month, or $55 a month billed yearly. That price covers 50,000 emails a month, unlimited senders, the API and the lemlist MCP server. The plan card says unlimited users while the pricing FAQ says pricing depends on users, so check the price for your team. Enrichment credits cost extra. lemlist offers a 14-day free trial. AgentLinkOps checks come from your workspace allowance as in the default guide.

​
Before you start

  • AgentLinkOps connected to your agent, with prospects saved as in step 1 of the default guide.
  • A lemlist account with your sending mailbox connected.
  • lemlist connected to your agent. Add https://app.lemlist.com/mcp as a remote MCP server and sign in with OAuth. Leave “lemlist” out of the connector’s name; lemlist rejects OAuth clients whose name contains it. An agent can use an API key from its environment instead.

​
1. Create the campaign

Create the campaign in lemlist with a short first email and a few follow-ups. Keep the volume low: backlink pitches go to one editor at a time. lemlist stops the sequence for a lead who replies Check that the campaign is set to stop on reply.

​
2. Add each prospect as a lead

Your agent adds each prospect with lemlist’s Create Lead in Campaign endpoint. Any extra field in the request becomes a lemlist custom variable, so send the AgentLinkOps watch id as aloWatchId:
This endpoint only creates. If the lead is already in the campaign, lemlist returns LEAD_ALREADY_IN_CAMPAIGN; update that lead instead of adding it again. Add deduplicate=true to refuse a lead that is already in another campaign. One lead carries one watch id. If the same editor covers two of your prospect pages, pitch both in one email and record the second page’s outcome by hand. Have your agent personalize each lead’s first step, review the messages, then launch the leads yourself.

​
3. Bring outcomes back once a day

Your agent reads the campaign’s activities since its last run (GET /api/activities with version=v2, campaignId and minDate), page by page. Each activity includes its lead, with your watch id at lead.variables.aloWatchId. The agent updates that watch with update_link_watch: Marking a lead interested is not a win. When the editor says the link is up, run the check in step 4. lemlist activities carry the whole lead record, and replies can include message text. Bring back the status and date only: no subjects, bodies, reply text or addresses. Follow the rule in the default guide: never move a status backwards. Updating an outcome never starts a check.
lemlist webhooks send the same activity types as they happen. Set a secret when you create the webhook; lemlist returns it in each delivery’s JSON body, so your receiver can reject requests without it. It works as a shared password; lemlist doesn’t sign deliveries. Ignore a delivery whose activity _id you’ve already applied. Keep the daily read to catch anything a webhook missed.
When an editor says the link is live, run the check from step 4 of the default guide. Only a check that finds your link makes the prospect won.

​
What we haven’t tested

We wrote this guide from lemlist’s public developer documentation on October 20, 2026. We haven’t run it end to end in a live lemlist account. Three points to confirm in your own account:
  • That the lead inside each activity includes your aloWatchId variable.
  • That your campaign stops on reply, as described above.
  • The exact names of lemlist’s MCP tools. Ask your agent to list them.
If the variable doesn’t come through, export the campaign’s leads by state from lemlist, as CSV or JSON. Find each lead’s watch in your own records, then record its status in AgentLinkOps.