Lemlist n8n integrationAutomate Lemlist with n8n.

Returns the activity feed of the account, one item per recorded action: an open, a reply, an accepted invite, a failed send. The readable counterpart of the trigger, for workflows that look backwards.

• Return All: on, n8n walks every page of the feed; off, it stops at Limit.
• Type (in the Filters collection): narrows the feed to one activity type, with the same 47 values as the trigger.
• Campaign Name or ID and Lead ID: scope the feed to one campaign or one prospect.
• Is First: keeps only the first occurrence of each activity.

Lists the campaigns of the account with their identifiers. Most teams use it as the first step of a loop, since almost every other operation needs a campaign ID rather than a campaign name.

• Return All: enabled, every campaign comes back page after page; disabled, Limit caps the list.
• Version (in Filters): targets a specific API version when your account needs it.

Pulls the performance figures of one campaign over a date window. Four fields are required here, more than anywhere else in the node, because the API needs an unambiguous period.

• Campaign Name or ID: the campaign to measure, picked from the list or passed as {{ $json.campaignId }} from the previous node.
• Start Date and End Date: the window boundaries, in the format shown by the placeholder (e.g. 2024-09-03 00:00:00Z).
• Timezone: the zone the window is read in, such as Europe/Paris. Skip it and the run fails, since the field is required.

Retrieves the result of an enrichment that already ran. Enrichment is asynchronous: the enrich operations start the job, this one collects what came back, so it usually sits after a Wait node.

• Enrichment ID: the identifier of the enrichment to retrieve, normally taken from the output of the operation that launched it with an expression like {{ $json.id }}.

Launches an enrichment on a lead that already exists in Lemlist, using the data attached to it. The four toggles decide what the job looks for, and each one is a separate search.

• Lead ID: the identifier of the lead to enrich, required, usually coming from a previous node.
• Find Email and Verify Email: look for a professional address, then check it before it is used in a sequence.
• Find Phone: adds a phone number to the record.
• LinkedIn Enrichment: completes the profile from LinkedIn.

Same enrichment engine, but on a person who is not yet a lead in a campaign. Nothing is required: you describe the person with whatever you have, and the operation works from there.

• Email, First Name, Last Name (in Additional Fields): the identity you start from.
• LinkedIn Url: often the most reliable single input.
• Company Name and Company Domain: the employer side, which helps when several people share a name.
• Find Email, Verify Email, Find Phone, LinkedIn Enrichment: the four searches to run.

Adds a prospect to a campaign, which is where the sequence starts for that person. The lead and its personalization fields are created in the same call.

• Campaign Name or ID: the campaign the lead is created under, required, from the dropdown or an expression.
• Email: the address of the lead, in the form name@email.com.
• Deduplicate (in Additional Fields): blocks the insert if the address already exists in another campaign.
• First Name, Company Name, Job Title, Icebreaker: the variables your templates use.
• Find Email, Verify Email, Find Phone: enrich on the way in.

Removes a prospect from a campaign. The sequence stops for that person and the record leaves the campaign, which is stronger than an unsubscribe and not reversible from the workflow.

• Campaign Name or ID: the campaign the lead is removed from, required, because the same address can exist in several campaigns.
• Email: the address to delete, passed as {{ $json.email }} when it comes from a CRM or a form.

Fetches a single prospect and its fields as Lemlist stores them. Handy as a guard clause: check what is already there before writing anything.

• Email: the address of the lead to retrieve. The field is not marked required, so an empty value makes the operation run without the filter you expected. Set it explicitly, most often from the trigger payload.

Stops the sequence for a prospect inside one campaign while keeping the record in place, unlike the delete operation. This is the polite exit, and the one to use when a reply says no.

• Campaign Name or ID: the campaign to unsubscribe the lead from, required; a lead present in three campaigns needs three calls.
• Email: the address concerned, generally read from the event that triggered the workflow.

Returns the team attached to the credential, with its identifier and its settings as the API exposes them. No parameter to fill: the API key already says which team it belongs to.

Reads the credit balance of the team, exactly as the API reports it. No parameter to fill: the response reflects whatever plan and usage the account currently has.

Puts an address on the account wide unsubscribe list. Broader than unsubscribing a lead from one campaign: the address is excluded going forward, whichever campaign tries to reach it.

• Email: the address to add to the unsubscribes, in the form name@email.com, usually taken from the event payload.

Takes an address back off the unsubscribe list, which makes it reachable again by future campaigns. Rare, deliberate, and worth logging somewhere your team can audit.

• Email: the address to delete from the unsubscribes. Nothing else is asked, so an expression pointing at the wrong field removes the wrong person.

Exports the addresses currently on the unsubscribe list. The reference list when you need to reconcile Lemlist with a CRM or a newsletter tool.

• Return All: on, the whole list comes back page by page; off, Limit decides how many addresses you get.