Export Campaign Leads
lemlist.export_campaign_leads
ActionCRM & salesconnection required
Calls the lemlist API with the connection's credentials.
Export a campaign's leads as JSON rows, filtered by their last state.
Connection
- Required
- Yes — the node will not save without one
- Auth type
- API key
- Providers
- lemlist
- Secret shape
- the API key, or {"api_key": "…"}
- Config it needs
- campaign_id
- Resolved by
- config.connection_id, else node.connection_id
Configuration
2 fields, none required. A dotted path is a nested object and name[] an array of objects — the editor renders the same tree.
| Field | Type | Required | Default | Constraints | Example |
|---|---|---|---|---|---|
campaign_id The campaign to act on. Falls back to the connection's default campaign when blank. | string | No | — | — | cam_4HrZbi8xsez4QlrnL |
state Last states to export, comma separated — for example 'contacted,interested'. Use 'all' for every state. | string | No | — | — | interested |
Example configuration
Every value below is the contract’s own example or default — nothing invented.
{
"campaign_id": "cam_4HrZbi8xsez4QlrnL",
"state": "interested"
}Output
One shape.
result
| Field | Type | Example |
|---|---|---|
items The records lemlist returned, unchanged. | array | — |
returned How many records are in 'items'. | number | — |
campaign_id The campaign the call acted on. | string | — |
{
"campaign_id": "",
"items": [],
"returned": 0
}See Export Campaign Leads run in a workflow.
In a technical demo we add the lemlist connection, drop the node on the canvas and let Workflow Health pre-flight it before the first real run.