Developer Platform: MCP server availableDeveloper Platform: MCP server available, App SDK from Q4 2026

[ More ]

Lemlist integration for your workflows.

Connect Lemlist to Collabase once and use 14 actions and 2 triggers in your workflows. No code needed, hosted in Switzerland.

Sign-inAn API key
CategoryMore
UpdatedOctober 2026
LicenceOpen source (MIT)
Back to the directory

Lemlist in Collabase

Connect Lemlist to Collabase once and use 14 actions and 2 triggers in your workflows. No code needed, hosted in Switzerland.

How to connect it

  1. Open the integrations in the workspace settings.
  2. Choose Lemlist and connect your account.
  3. Add a trigger or an action to the workflow.
  • In lemlist, click your profile picture (bottom left) and open Settings.
  • Go to Integrations.
  • Click Generate next to API key and copy it. You won't see it again.

[ More ]

Related integrations

All integrations

Tools that often share a workflow.

Questions about Lemlist

What can I automate with Lemlist in Collabase?

Lemlist brings 14 actions and 2 triggers, for example Mark Lead From One Campaign as Interested, Mark Lead From One Campaign as Not Interested, Mark Lead From All Campaign as Interested, Mark Lead From All Campaigns as Not Interested and 10 more. You combine them in a workflow without code and mix them with every other integration.

How do I connect Lemlist to Collabase?

You open the integrations in the workspace settings, choose Lemlist and connect your account once, using an API key. After that all triggers and actions are available in the workflow.

Can Lemlist start a workflow?

Yes. Lemlist provides 2 triggers, for example New Activity and Unsubscribed Recipient. The workflow runs as soon as the event happens.

Does the Lemlist integration cost extra?

No. All integrations are included in every licence, in the Isolated Cloud and in Self-Hosted operation. There is no module price.

Test it against your own content. A proof of concept is ready within days.

We set up an instance with your content and you test it against real workflows. In a first conversation we clarify scope, operating model and timing.