Short answer: Drop the "Lemlist → Add Lemlist Lead to Campaign" action anywhere in your workflow, map the inputs from upstream nodes, and publish.
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. Example: cam_abc123 |
Email email | string | Required | Email. e.g. "lead@company.com" |
First Name firstName | string | Optional | First Name. e.g. "John" |
Last Name lastName | string | Optional | Last Name. e.g. "Doe" |
Company companyName | string | Optional | Company. e.g. "Acme Inc" |
{"campaignId": "e.g. cam_abc123","email": "lead@company.com","firstName": "John","lastName": "Doe","companyName": "Acme Inc"}
{"_id": "lead123","email": "lead@company.com","firstName": "John","campaignId": "cam_abc123"}
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.
Triggered by anything in the catalog. Free tier available. No credit card.