Lemlist Tools

Lemlist is a cold-outreach and sales-engagement platform. Use these tools in a workflow to read your campaigns, add leads to a campaign, and pull campaign activity (opens, clicks, replies) directly from the Lemlist API.

Overview

Operations

Configuration

lemlist_list_campaigns

Calls GET https://api.lemlist.com/api/campaigns.

lemlist_get_campaign

Calls GET https://api.lemlist.com/api/campaigns/{campaignId}.

lemlist_add_lead

Calls POST https://api.lemlist.com/api/campaigns/{campaignId}/leads/{email}. The email is URL-encoded into the path; firstName and lastName are sent in the JSON body only when provided.

lemlist_list_activities

Calls GET https://api.lemlist.com/api/activities.

Outputs

lemlist_list_campaigns

• data (json) — Array of Lemlist campaign objects.
• metadata (json) — List metadata.
  • count (number) — Number of campaigns returned.

lemlist_get_campaign

• data (json) — The Lemlist campaign object.
• metadata (json) — Campaign identifiers.
  • id (string) — Campaign ID.

lemlist_add_lead

• data (json) — The created Lemlist lead object.
• metadata (json) — Lead identifiers.
  • id (string) — Lead ID.

lemlist_list_activities

• data (json) — Array of Lemlist activity objects.
• metadata (json) — List metadata.
  • count (number) — Number of activities returned.

YAML Example

lemlist_1:
  type: lemlist
  name: "Lemlist"
  inputs:
    operation: "lemlist_add_lead"
    campaignId: "cam_abc123def456"
    email: "lead@example.com"
    firstName: "Jane"
    lastName: "Doe"
    apiKey: "{{LEMLIST_API_KEY}}"
  connections:
    outgoing:
      - target: next-block-id

Tips

• Auth is HTTP Basic: Zelaxy builds the Authorization header as Basic base64(":" + apiKey) (empty username, API key as password). You only need to supply apiKey — get it from your Lemlist account under Settings → Integrations → API. Store it as an environment variable and reference it with {{LEMLIST_API_KEY}}.
• For lemlist_add_lead, only campaignId and email are required; firstName and lastName are optional and are omitted from the request body when left blank. The lead's email is placed in the URL path, so it does not need to be globally unique across campaigns.
• The list operations return raw arrays from Lemlist. Use {{lemlist_1.data}} for the array and {{lemlist_1.metadata.count}} for the item count; for the single-object operations use {{lemlist_1.metadata.id}} to grab the created/fetched record ID.