Skip to content
Documentation
Contact
← Back to documentation
Technical Reference

Lemlist

Lemlist integration for Flows360 workflows.

CategoryOther
Authenticationcustom
Version0.1.10
Published scopes0 published scopes
Last updatedSeptember 19, 2026

Overview

Connect Lemlist with Flows360

Lemlist integration for Flows360 workflows.

Use the Lemlist connector to include its declared actions and events in Flows360 workflows without duplicating the integration logic inside each consuming system. This pinned connector version currently exposes 13 actions and 2 triggers.

Available actions

  • Mark Lead From One Campaign as Interested
  • Mark Lead From One Campaign as Not Interested
  • Mark Lead From All Campaign as Interested
  • Mark Lead From All Campaigns as Not Interested
  • Pause Lead From All or Specific Campaigns
  • Resume Lead From All or Specific Campaigns
  • Remove Lead From Unsubscribe List
  • Remove Lead from A Campaign
  • Plus 5 additional declared actions.

Available triggers

  • New Activity
  • Unsubscribed Recipient

The capability list above is generated from the exact reviewed connector package so the public description stays aligned with the version Flows360 operates.

Technical guide

Technical reference

Package identity

  • Connector: Lemlist
  • Package: @activepieces/piece-lemlist@0.1.10
  • Exact artifact digest: sha256:006162e7c2cccdd2a3d7cdb0b18b313f9d19d238a4b42795dece332f776fdf25
  • Runtime: Activepieces-compatible deterministic worker
  • Source: the exact reviewed Activepieces source

Authentication

SECRET TEXT. Connection values are tenant-specific and remain in the consuming Studio instance; CDK stores definitions and field metadata, not customer credential values.

Action contracts

  • Mark Lead From One Campaign as Interested (markLeadFromOneCampaignAsInterested), Mark a lead in a campaign as interested. Classification: read.
  • Mark Lead From One Campaign as Not Interested (markLeadFromOneCampaignAsNotInterested), Mark a lead in a campaign as not interested. Classification: read.
  • Mark Lead From All Campaign as Interested (markLeadFromAllCampaignAsInterested), Mark a lead as “interested” across all campaigns. Classification: read.
  • Mark Lead From All Campaigns as Not Interested (markLeadFromAllCampaignsAsNotInterested), Mark a lead as “not interested” across all campaigns. Classification: read.
  • Pause Lead From All or Specific Campaigns (pauseLeadFromAllOrSpecificCampaigns), Pause a lead’s outreach across all or specific campaigns. Classification: read.
  • Resume Lead From All or Specific Campaigns (resumeLeadFromAllOrSpecificCampaigns), Resume a lead’s outreach across all or specific campaigns. Classification: read.
  • Remove Lead From Unsubscribe List (removeLeadFromUnsubscribeList), Remove a lead from “unsubscribe” list. Classification: read.
  • Remove Lead from A Campaign (removeLeadFromACampaign), removes a lead from a specific campaign. Classification: read.
  • Unsubscribe a Lead (unsubscribeALead), Unsubscribe a lead from a campaign. Classification: read.
  • Add Lead To A Campaign (addLeadToACampaign), Adds a lead to a specific campaign with optional enrichment and lead details. Classification: read.
  • Add Custom Variables on Lead (addCustomVariablesOnLead), Add new custom variables to a lead. Classification: read.
  • Update Lead From Campaign (updateLeadFromCampaign), Updates a lead in a specific campaign. Classification: read.
  • Search Lead (searchLead), Look up a lead by email and campaign. Classification: read.

Trigger contracts

  • New Activity, webhook.
  • Unsubscribed Recipient, webhook.

Verification

Deterministic execution evidence is recorded for the pinned artifact, including 1 exercised action entrypoint and 0 exercised trigger entrypoints.

Capability summary

Authenticationcustom
Supported objects15
Supported actions13
Triggers2

Authentication

Authentication method: custom

Authentication profiles

connection · custom
  • Lemlist API Key Required · protected credential

Supported objects

ObjectReadWriteNotes
Mark Lead From One Campaign as Interested Yes No Mark a lead in a campaign as interested.
Mark Lead From One Campaign as Not Interested Yes No Mark a lead in a campaign as not interested.
Mark Lead From All Campaign as Interested Yes No Mark a lead as u201cinterestedu201d across all campaigns.
Mark Lead From All Campaigns as Not Interested Yes No Mark a lead as u201cnot interestedu201d across all campaigns.
Pause Lead From All or Specific Campaigns Yes No Pause a leadu2019s outreach across all or specific campaigns.
Resume Lead From All or Specific Campaigns Yes No Resume a leadu2019s outreach across all or specific campaigns.
Remove Lead From Unsubscribe List Yes No Remove a lead from u201cunsubscribeu201d list.
Remove Lead from A Campaign Yes No removes a lead from a specific campaign.
Unsubscribe a Lead Yes No Unsubscribe a lead from a campaign.
Add Lead To A Campaign Yes No Adds a lead to a specific campaign with optional enrichment and lead details.
Add Custom Variables on Lead Yes No Add new custom variables to a lead.
Update Lead From Campaign Yes No Updates a lead in a specific campaign.
Search Lead Yes No Look up a lead by email and campaign.
New Activity Yes No webhook trigger declared by the pinned package.
Unsubscribed Recipient Yes No webhook trigger declared by the pinned package.

Supported actions

Mark Lead From One Campaign as Interested · Read

Mark a lead in a campaign as interested.

mark_lead_from_one_campaign_as_interested · Risk: low · Retry: safe

Inputs

  • campaignId · string · Required, Select a campaign
  • email · string · Required, The email of the lead to mark as interested.
Mark Lead From One Campaign as Not Interested · Read

Mark a lead in a campaign as not interested.

mark_lead_from_one_campaign_as_not_interested · Risk: low · Retry: safe

Inputs

  • campaignId · string · Required, Select a campaign
  • email · string · Required, The email of the lead to mark as not interested.
Mark Lead From All Campaign as Interested · Read

Mark a lead as u201cinterestedu201d across all campaigns.

mark_lead_from_all_campaign_as_interested · Risk: low · Retry: safe

Inputs

  • email · string · Required, The email of the lead to mark as interested.
Mark Lead From All Campaigns as Not Interested · Read

Mark a lead as u201cnot interestedu201d across all campaigns.

mark_lead_from_all_campaigns_as_not_interested · Risk: low · Retry: safe

Inputs

  • email · string · Required, The email of the lead to mark as not interested.
Pause Lead From All or Specific Campaigns · Read

Pause a leadu2019s outreach across all or specific campaigns.

pause_lead_from_all_or_specific_campaigns · Risk: low · Retry: safe

Inputs

  • campaignId · string · Optional, Select a campaign (optional)
  • email · string · Required, The email of the lead to pause.
Resume Lead From All or Specific Campaigns · Read

Resume a leadu2019s outreach across all or specific campaigns.

resume_lead_from_all_or_specific_campaigns · Risk: low · Retry: safe

Inputs

  • campaignId · string · Optional, Select a campaign (optional)
  • email · string · Required, The email of the lead to resume.
Remove Lead From Unsubscribe List · Read

Remove a lead from u201cunsubscribeu201d list.

remove_lead_from_unsubscribe_list · Risk: low · Retry: safe

Inputs

  • email · string · Required, The email of the lead to remove from the unsubscribe list.
Remove Lead from A Campaign · Read

removes a lead from a specific campaign.

remove_lead_from_acampaign · Risk: low · Retry: safe

Inputs

  • campaignId · string · Required, Select a campaign
  • email · string · Required, The email of the lead to remove.
Unsubscribe a Lead · Read

Unsubscribe a lead from a campaign.

unsubscribe_alead · Risk: low · Retry: safe

Inputs

  • campaignId · string · Required, Select a campaign
  • email · string · Required, The email of the lead to unsubscribe.
Add Lead To A Campaign · Read

Adds a lead to a specific campaign with optional enrichment and lead details.

add_lead_to_acampaign · Risk: low · Retry: safe

Inputs

  • campaignId · string · Required, Select a campaign
  • email · string · Required, The email of the lead to add
  • firstName · string · Optional
  • lastName · string · Optional
  • picture · string · Optional
  • phone · string · Optional
  • linkedinUrl · string · Optional
  • companyName · string · Optional
  • companyDomain · string · Optional
  • icebreaker · string · Optional
  • jobTitle · string · Optional
  • deduplicate · boolean · Optional, Avoid adding the lead if it already exists in any campaign
  • linkedinEnrichment · boolean · Optional, Run LinkedIn enrichment for this lead
  • findEmail · boolean · Optional, Try to find a verified email for this lead
  • verifyEmail · boolean · Optional, Verify the leadu2019s email using debounce
  • findPhone · boolean · Optional, Try to find a phone number for this lead
Add Custom Variables on Lead · Read

Add new custom variables to a lead.

add_custom_variables_on_lead · Risk: low · Retry: safe

Inputs

  • leadId · string · Required, The unique identifier of the lead (e.g. lea_8xJSc7sV7ggpiVnXe). Available as the _id field returned by the Add Lead To A Campaign and Search Lead actions.
  • customVariables · object · Required, New custom variables to create on the lead. Each key is the variable name and each value is its content. Names must not match an existing default or custom variable.
Update Lead From Campaign · Read

Updates a lead in a specific campaign.

update_lead_from_campaign · Risk: low · Retry: safe

Inputs

  • campaignId · string · Required, Select a campaign
  • email · string · Required, The email of the lead to update.
  • firstName · string · Optional
  • lastName · string · Optional
  • picture · string · Optional
  • phone · string · Optional
  • linkedinUrl · string · Optional
  • companyName · string · Optional
  • companyDomain · string · Optional
  • icebreaker · string · Optional
  • jobTitle · string · Optional
Search Lead · Read

Look up a lead by email and campaign.

search_lead · Risk: low · Retry: safe

Inputs

  • campaignId · string · Optional, Select a campaign (optional)
  • email · string · Required, The email of the lead to look up

Triggers

New Activity · Webhook

Triggers for each new activity.

Unsubscribed Recipient · Webhook

Triggers when a recipient unsubscribes.

Setup

Setup

  1. Add the Lemlist connector to the workflow in the target Flows360 Studio instance.
  2. Create or select the tenant-specific connection required by the connector. Connection secrets remain in the Studio connection boundary and are not copied into CDK documentation.
  3. Provide the connection fields declared by the pinned package:
  • No provider credential fields are declared by the pinned package.
  1. Select the required action or trigger and complete its declared input fields. Required and optional inputs are defined by the exact package schema.
  2. Test the workflow in the appropriate environment before enabling production scheduling or event delivery.

Limitations

Limitations and operational notes

  • This content describes @activepieces/piece-lemlist@0.1.10; provider behaviour can change independently and should be revalidated when the provider or connector version changes.
  • Only the 13 actions and 2 triggers declared by this pinned package are represented here.
  • Tenant credentials and connection values are not stored in the public connector record.
  • Provider-side permissions, account entitlements, quotas and rate limits remain subject to the connected provider account and are not inferred when the package does not declare them.
  • Deterministic execution evidence is recorded for the pinned artifact, including 1 exercised action entrypoint and 0 exercised trigger entrypoints.

Troubleshooting

Why canu2019t the connector authenticate?

Check the tenant connection in Studio and confirm every required Lemlist connection field is present. Re-authorise OAuth-based connections if the provider token or consent has expired. Do not place credential values in CDK content or logs.

Why is an action or trigger unavailable?

Confirm that the workflow is using @activepieces/piece-lemlist@0.1.10 and compare the requested capability with the declared action and trigger list for this version. A capability that is not declared by the pinned package should not be presented as supported.

What should I check after a provider-side change?

Revalidate authentication, required fields, action/trigger behaviour and provider documentation before publishing refreshed connector content or moving a new package version into production.

github.com