List Activities

lemlist.list_activities
ActionCRM & salesconnection required

Calls the lemlist API with the connection's credentials.

List sequence activities, filtered by type, campaign, lead or date.

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

8 fields, none required. A dotted path is a nested object and name[] an array of objects — the editor renders the same tree.

FieldTypeRequiredDefaultConstraintsExample
type
One activity type, such as emailsReplied, emailsOpened, linkedinInviteAccepted or paused. lemlist keeps this open, so it is free text rather than a list.
stringNo——emailsReplied
campaign_id
Only activities of this campaign. All campaigns when blank.
stringNo———
lead_id
Only activities of this lead.
stringNo———
is_first
Only the first activity of its kind for each lead.
booleanNo———
limit
How many activities to return. lemlist defaults to 100 and caps it there.
numberNo—1–100—
offset
How many activities to skip; raise it by the limit to walk the history.
numberNo—≥ 0—
start_date
Only activities created at or after this ISO 8601 datetime.
stringNo—iso8601 format—
end_date
Only activities created at or before this ISO 8601 datetime.
stringNo—iso8601 format—

Example configuration

Every value below is the contract’s own example or default — nothing invented.

{
  "type": "emailsReplied"
}

Output

One shape.

result

FieldTypeExample
items
The records lemlist returned, unchanged.
array—
returned
How many records are in 'items'.
number—
{
  "items": [],
  "returned": 0
}

See List Activities 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.