Integration
Connect lemlist to Customer.io
When New Activity fires in lemlist, your agent runs Send transactional email in Customer.io. Describe the whole flow and it is built, tested on every scenario and kept running.
What the catalog holds today. Ask for anything missing and your agent reads the API documentation and adds it.
Build solutions, not workarounds.
What do you want lemlist and Customer.io to do together?
Ask the assistant
Connect your AI client
Give your AI client this address.
https://mcp.apiant.aiOne connection does both: ask your client to act in an app once, or have it build an automation that keeps running. Any client that takes a remote MCP server. Nothing to install. Create your free account, then sign in once in your browser.
Set it up in your client
Claude Code
Run this in the directory you want to work in.
claude mcp add --transport http -s project apiant-ai https://mcp.apiant.aiStart Claude Code there, approve the server, and sign in in the browser page it opens.
Claude Code guide (opens in a new tab)Claude, web and desktop
Open Customize, then Connectors, then Add custom connector, and paste the address. On Team and Enterprise an owner adds it first.
Setup guide (opens in a new tab)Cursor
Add the address to your MCP configuration as a server URL. Cursor signs you in in your browser.
Setup guide (opens in a new tab)Zed
Open Settings, then AI, then MCP Servers, then Add Server, then Add Remote Server.
Setup guide (opens in a new tab)Codex and the ChatGPT desktop app
Open Settings, then MCP servers, then Add server, and choose Streamable HTTP. From the terminal, Codex takes the address with its own add command and then signs you in.
Setup guide (opens in a new tab)Any other MCP client
Paste the address where the client asks for a remote MCP server URL, and name the server apiant-ai where it lets you. APIANT's skills reach the client over the same connection.
Setup guide (opens in a new tab)Example flows
What lemlist can start in Customer.io
When New Activity in lemlist
then Send transactional email in Customer.io
Starting points drawn from the triggers and actions in the catalog today. Describe the flow you need, at any depth, and your agent builds it and tests every scenario before it ships.
Everything your agent can do with lemlist and Customer.io
Triggers and actions 1 trigger · 18 actions
- New Activity
Triggers when an activity has ocurred. It can be an email has been sent, replied to, bounced, or unsubscribed from or v3 new activity like a LinkedIn profile have been visited or a phone call just ended.
- Add Recipient to Unsubscribe List
Add a recipient to the unsubscribe list.
- Mark a Lead From All Campaigns as Interested
Mark a Lead From All Campaigns as Interested.
- Mark a Lead From One Campaign as Interested
Mark a Lead From One Campaign as Interested.
- Remove Lead From Campaign
Remove a Lead from a campaign.
- Remove Lead From Unsubscribe
Remove a Lead from unsubscribe.
- Resume Lead From All or Specific Campaigns
Resume Lead From All or Specific Campaigns.
- Search Lead
Search a lead.
- Update Lead From Campaign
Update Lead From Campaign.
- Create Anonymous Event
Records an event that isn't tied to a known person yet, such as a page view or an action by a visitor. Include an anonymous id to link the event to a person later.
- Create Event
Records an event for a person in Customer.io, which can trigger campaigns or update segments.
- Delete person
Deletes a person from your Customer.io workspace, identified by their id, email address or Customer.io id.
- Get person
Look up a customer's attributes by customer_id.
- List segments
List all manual and data-driven segments in the workspace.
- Merge people
Merges a duplicate person into a primary person. The secondary person's attributes and activity move to the primary person, and the secondary person is deleted.
- Remove people from segment
Removes people from a manual segment in Customer.io. Data-driven segments can't be changed this way.
- Send API-triggered broadcast
Trigger an API-triggered broadcast campaign to send immediately.
- Send transactional email
Send a one-off transactional email via a transactional message template.
- Suppress person
Deletes a person from your Customer.io workspace and suppresses their identifiers so nobody can be added again with the same id, email or phone. Activity attributed to them is redacted.
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.
Each app on its own
Reviews
What our customers say
More from lemlist
lemlist to RefinerRefiner is a customer survey tool for data driven SaaS teams.
lemlist to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
lemlist to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
lemlist to Google SheetsGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
lemlist to Google DriveGoogle Drive is a cloud storage solution for uploading, sharing, and collaborating on files across devices...
lemlist to MailchimpMailchimp marketing automation and email platform.
More into Customer.io
HubSpot to Customer.ioHubSpot is your all-in-one stop for all of your marketing software needs.
Wistia to Customer.ioWistia makes it easy to host, track, and measure video engagement online.
Gmail to Customer.ioGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Questions
lemlist and Customer.io, answered
What can start an automation from lemlist?
Any of lemlist's 1 trigger in the catalog, including New Activity. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Customer.io when something happens in lemlist?
Any of Customer.io's 10 actions, including Create Anonymous Event, Create Event, Send API-triggered broadcast and Send transactional email. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Customer.io to lemlist?
Customer.io has no triggers in the catalog today, so automations start in lemlist. If you need the other direction, ask: your agent reads Customer.io's API documentation and adds it.
Do I have to build a connector for lemlist or Customer.io?
No. Both are in the catalog with their triggers and actions. You describe the automation; your agent builds it, tests every scenario and keeps it running.
Can my AI client use lemlist and Customer.io without building an automation?
Yes. With your AI client connected to APIANT, ask it to do something in either app once and it runs that action on the spot. Ask for an automation and your agent builds it, tests every scenario and keeps it running. One connection covers both.
What happens when something fails?
Your agent works that out for you. It plans the failure paths along with the happy path, then tests every scenario before it ships.
Is there a free plan?
Yes. Every plan includes the agent, including free, and building from your own AI client spends no assistant credits.