Integration
Connect lemlist to Commonsku
When New Activity fires in lemlist, your agent runs Add client contact in Commonsku. 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 Commonsku 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 Commonsku
When New Activity in lemlist
then Add client contact in Commonsku
When New Activity in lemlist
then Update contact in Commonsku
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 Commonsku
Triggers and actions 1 trigger · 30 actions
Trigger
New ActivityTriggers 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.
Action
Add Recipient to Unsubscribe ListAdd a recipient to the unsubscribe list.
Action
Mark a Lead From All Campaigns as InterestedMark a Lead From All Campaigns as Interested.
Action
Mark a Lead From One Campaign as InterestedMark a Lead From One Campaign as Interested.
Action
Remove Lead From CampaignRemove a Lead from a campaign.
Action
Remove Lead From UnsubscribeRemove a Lead from unsubscribe.
Action
Resume Lead From All or Specific CampaignsResume Lead From All or Specific Campaigns.
Action
Search LeadSearch a lead.
Action
Update Lead From CampaignUpdate Lead From Campaign.
Action
Add clientCreates a new client in commonsku.
Action
Add client addressCreates a new address in a client's address book and returns the created address.
Action
Add client contactCreates a contact for a commonsku client and returns the new contact.
Action
Add projectCreates a new project for an existing client in commonsku.
Action
Add tagCreates a tag in your commonsku company, or returns the existing tag if one with the same label already exists.
Action
Delete clientDeletes a client from commonsku by ID, along with all of its contacts and addresses, and returns the deleted client.
Action
Find products by keywordReturns the products whose name, supplier code or tag match a keyword, optionally narrowed by supplier, division, tag, owner or net price.
Action
Get clientReturns the details of a single Commonsku client, including its terms, industry, status and tags. An error occurs if the client is not found.
Action
Get invoiceReturns a single invoice, including its customer, billing and shipping details, line items and totals. An error occurs if the invoice is not found.
Action
Get productReturns the full details of a single product by its ID, including its colors, sizes, imprints, images, SKUs, costs and prices. An error occurs if the product is not found.
Action
Get projectReturns the details of a single commonsku project by its ID.
Action
List client contactsReturns the contacts associated with a commonsku client, including names, email, department and phone numbers.
Action
List clientsReturns the clients in your commonsku account, optionally filtered by customer number, client name, credit hold status or last-updated date.
Action
List invoicesReturns invoices in your commonsku account, optionally filtered by status, customer, numbers or dates.
Action
List productsReturns products in your commonsku account, optionally filtered by keyword, supplier, division, tag or price, or by a special mode such as popular or recently used products.
Action
List projectsReturns the projects in your commonsku account, optionally filtered by client, dates or project number.
Action
List purchase ordersReturns the purchase orders in your commonsku account, optionally filtered by status, client, order numbers, dates or tracking number.
Action
List sales ordersReturns the sales orders in your commonsku account, optionally filtered by status, client, numbers and date ranges.
Action
List tagsReturns the tags defined in your commonsku company, optionally limited to one record, one record type, or a label search.
Action
Update clientUpdates an existing commonsku client's name, payment terms, industry, rep, website, status, credit hold and tags.
Action
Update contactUpdates an existing client contact's name, email or department in commonsku.
Action
Update productUpdates an existing product in commonsku. Only the fields you fill in are changed.
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 Commonsku
HubSpot to CommonskuHubSpot is your all-in-one stop for all of your marketing software needs.
Salesforce to CommonskuSalesforce is a leading enterprise customer relationship management (CRM) platform.
Slack to CommonskuSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Google Sheets to CommonskuGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Gmail to CommonskuGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to CommonskuGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
lemlist and Commonsku, 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 Commonsku when something happens in lemlist?
Any of Commonsku's 22 actions, including Update client, Update contact, Update product and Add client. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Commonsku to lemlist?
Commonsku has no triggers in the catalog today, so automations start in lemlist. If you need the other direction, ask: your agent reads Commonsku's API documentation and adds it.
Do I have to build a connector for lemlist or Commonsku?
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 Commonsku 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.