ActionLemlistUpdated September 2026
How do I remove a lead from a Lemlist campaign?
Short answer: You can remove lemlist lead in Lemlist by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Lemlist Remove Lemlist Lead action to a workflow, map its 2 inputs from any upstream app, and it runs automatically every time the trigger fires. No code, and a free tier to start.
Inputs
The fields this action accepts.
Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.
| Field | Type | Required | Description |
|---|---|---|---|
Campaign ID campaignId | string | Required | Campaign ID |
Lead Email email | Required | The email address. Used as the recipient or identifier depending on context. |
Sample request
{"campaignId": "{{trigger.campaignId}}","email": "e.g. user@example.com"}
Returns
{"success": true}
Use these fields in downstream nodes for routing, logging, or error handling.
Triggered by
Apps that pair well as the trigger for Remove Lemlist Lead.
Any of these apps can fire this action as part of a workflow.
FAQ
Questions about Remove Lemlist Lead.
What does the Remove Lemlist Lead action do in Lemlist?
Stops sequencing a specific lead. For "they replied to a different channel → stop outbound" coordination workflows.
What inputs does Remove Lemlist Lead require?
Required: Campaign ID, Lead Email. Every input accepts a static value or a variable from any upstream node in your workflow.
Can I use dynamic inputs from earlier workflow nodes?
Yes. Any field on this action can pull values from upstream nodes, whether that's a form response, a trigger payload, an AI output, or a lookup result.
What happens if Lemlist returns an error?
The run history shows the failed step with its input and the error message Lemlist returned, so you can fix the input and run the workflow again. Automatic retries are built into HTTP steps only, where you can also set your own retry count and delay.
Does Remove Lemlist Lead support batch operations?
Run Remove Lemlist Lead inside a loop to process each item in an array. TinyCommand does not throttle calls for you, so for large arrays add a Delay step if you need to stay within Lemlist's rate limits.
More actions
Other Lemlist actions.
Action
Add Lemlist Lead to Campaign
Enrolls a lead in a specific Lemlist sequence with email, name, custom variables. For "enrichment complete → add to nurture campaign" or "lead scored high → enroll in outbound" workflows.
ActionList Lemlist Campaigns
Returns the user's sequence campaigns with name, status, lead counts. Useful for resolving campaign IDs at workflow setup.
ActionList Lemlist Leads in Campaign
Returns paginated leads enrolled in a specific campaign with status. For "audit who's stuck on this step" or for sync workflows that mirror Lemlist state to CRM.