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.
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. |
{"campaignId": "{{trigger.campaignId}}","email": "e.g. user@example.com"}
{"success": true}
Use these fields in downstream nodes for routing, logging, or error handling.
Any of these apps can fire this action as part of a workflow.