lemlist

Add leads to campaigns and manage cold outreach in lemlist. In Appbricx, your workflows and server functions call it by name once it is connected.

Connect lemlistFull reference

What you can do

12 actions, each one call from a workflow or a server function. Triggers come from your app: a row changing, a schedule or a webhook.

  • Add Lead To A CampaignaddLeadToACampaign
    Adds a lead to a specific campaign with optional enrichment and lead details.
  • Mark Lead From All Campaign as InterestedmarkLeadFromAllCampaignAsInterested
    Mark a lead as “interested” across all campaigns.
  • Mark Lead From All Campaigns as Not InterestedmarkLeadFromAllCampaignsAsNotInterested
    Mark a lead as “not interested” across all campaigns.
  • Mark Lead From One Campaign as InterestedmarkLeadFromOneCampaignAsInterested
    Mark a lead in a campaign as interested.
  • Mark Lead From One Campaign as Not InterestedmarkLeadFromOneCampaignAsNotInterested
    Mark a lead in a campaign as not interested.
  • Pause Lead From All or Specific CampaignspauseLeadFromAllOrSpecificCampaigns
    Pause a lead’s outreach across all or specific campaigns.
  • Remove Lead from A CampaignremoveLeadFromACampaign
    removes a lead from a specific campaign.
  • Remove Lead From Unsubscribe ListremoveLeadFromUnsubscribeList
    Remove a lead from “unsubscribe” list.
  • Resume Lead From All or Specific CampaignsresumeLeadFromAllOrSpecificCampaigns
    Resume a lead’s outreach across all or specific campaigns.
  • Search LeadsearchLead
    Look up a lead by email and campaign.
  • Unsubscribe a LeadunsubscribeALead
    Unsubscribe a lead from a campaign.
  • Update Lead From CampaignupdateLeadFromCampaign
    Updates a lead in a specific campaign.

Set it up

About two minutes, once per project or once for the whole workspace.

  1. Open Integrations in the builder

    Backend panel, Integrations tab, then lemlist. To connect it for every project, use Workspace settings, Integrations.

  2. Add your credentials

    An API key (or token) from your lemlist account, pasted once. It is stored encrypted and only read on the server when an action runs.

    • API key From lemlist's settings
  3. Call an action

    From a workflow, by integration id and action name. The call answers with success, output and, when it fails, the reason.

    Workflow
    // .workflow.js (native ctx)
export async function run(ctx) {
  const res = await ctx.integrations.invoke("lemlist", "addLeadToACampaign", {
    "campaignId": "<campaignId>",
    "email": "<lead email>"
  });
  if (!res.success) throw new Error(res.error);
  ctx.log.info("lemlist answered", { output: res.output });
}

lemlist and its logo are trademarks of their owner, shown only to identify the service this integration connects to. Their use does not imply endorsement by, or affiliation with, that company.

Connect lemlist once. Every workflow can use it.

Start freeAll integrations