Lemlist currently provides 2 triggers that can start a workflow and 12 actions a workflow can run. Use those building blocks to move information into the same workspace as the people, records, and next steps it affects.
New Activity
Triggers for each new activity.
Unsubscribed Recipient
Triggers when a recipient unsubscribes.
Mark Lead From One Campaign as Interested
Mark a lead in a campaign as interested.
Mark Lead From One Campaign as Not Interested
Mark a lead in a campaign as not interested.
Mark Lead From All Campaign as Interested
Mark a lead as “interested” across all campaigns.
Mark Lead From All Campaigns as Not Interested
Mark a lead as “not interested” across all campaigns.
Pause Lead From All or Specific Campaigns
Pause a lead’s outreach across all or specific campaigns.
Resume Lead From All or Specific Campaigns
Resume a lead’s outreach across all or specific campaigns.
Remove Lead From Unsubscribe List
Remove a lead from “unsubscribe” list.
Remove Lead from A Campaign
removes a lead from a specific campaign.
Unsubscribe a Lead
Unsubscribe a lead from a campaign.
Add Lead To A Campaign
Adds a lead to a specific campaign with optional enrichment and lead details.
Update Lead From Campaign
Updates a lead in a specific campaign.
Search Lead
Look up a lead by email and campaign.
These recipes are generated from the triggers, actions, and categories currently available for this piece. Use them as starting points, then choose the exact fields, conditions, and records your workflow should update.
Start from a supported Lemlist event, then create or update the appropriate CRM, project, or custom record with the source context preserved.
Starts with
New Activity
Finishes with
Create or update a Coherence record
Use a change in Coherence to run a supported Lemlist action, so the next step follows the record instead of relying on someone to copy it.
Starts with
A Coherence record or workflow changes
Finishes with
Mark Lead From One Campaign as Interested
Combine Lemlist with another integration and Coherence records to move information into the same workspace as the people, records, and next steps it affects.
Starts with
New Activity
Finishes with
Mark Lead From One Campaign as Interested, then preserve the outcome in Coherence
The exact authentication fields depend on Lemlist. The workflow structure stays straightforward:
Authorize the Lemlist account and permissions the workflow needs.
Select one of the current triggers or actions listed above and map its fields.
Run a small test, inspect the result in both systems, and only then enable the workflow.
Explore apps that share a category with Lemlist or provide a complementary trigger or action.
Lemlist currently provides 2 triggers that can start a workflow and 12 actions a workflow can run. Use those building blocks to move information into the same workspace as the people, records, and next steps it affects.
Lemlist currently lists 2 triggers and 12 actions in the integration catalog. The supported list is refreshed from the pieces available in Coherence, so review the capability names on this page before building a workflow.
Yes. A workflow can combine supported Lemlist triggers or actions with Coherence records and other available integrations. The exact flow depends on the authentication, permissions, triggers, and actions exposed by each connected app.
The listed triggers and actions are designed for visual workflows. If the pre-built integration does not expose a capability you need, HTTP and webhook steps can cover APIs that your team is authorized to use.
Start automating in minutes. No credit card required.
