List Lemlist Leads in Campaign: Lemlist action

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
Limit limit	number	Optional	Limit

Sample request

{
  "campaignId": "{{trigger.campaignId}}",
  "limit": "{{trigger.limit}}"
}

Returns

[
  {
    "email": "lead@example.com",
    "status": "interested",
    "lastName": "Doe",
    "firstName": "John",
    "companyName": "Acme Inc"
  }
]

Use these fields in downstream nodes for routing, logging, or error handling.

FAQ

Questions about List Lemlist Leads in Campaign.

What does the List Lemlist Leads in Campaign action do in Lemlist?

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.

What inputs does List Lemlist Leads in Campaign require?

Required: Campaign ID. 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 workflow pauses on the failed node, the error message is captured in the run log, and you can retry the run with one click. Auto-retry policies are configurable per workflow with exponential backoff up to 5 attempts.

Does List Lemlist Leads in Campaign support batch operations?

Yes. Run List Lemlist Leads in Campaign inside a Loop node to process arrays. Tiny Command handles Lemlist's rate limits automatically so you don't have to throttle manually.

More actions