Lemlist: Get Lead Activity

Getting the full activity thread for a specific Lemlist lead — sent messages, opens, clicks, and replies.

Tool ID: lemlist_get_lead_activity

Run this action

Use the TypeScript SDK for a single call. Put ctx.tools.execute(...) inside a Play when the call should be durable, scheduled, or run across a CSV.

import { Deepline } from 'deepline';

const deepline = await Deepline.connect();
const result = await deepline.tools.execute(
  'lemlist_get_lead_activity',
  {
    "lead_id": "lead_123"
  },
);

console.log(result.toolResponse.raw);

CLI

deepline tools execute lemlist_get_lead_activity --input '{
  "lead_id": "lead_123"
}' --json

Example response

The SDK exposes this shape at result.toolResponse.raw. Values below are representative.

{
  "data": [
    {
      "id": "id_123",
      "type": "example",
      "createdAt": "2026-01-15T12:00:00Z"
    }
  ]
}

Use deepline tools get lemlist_get_lead_activity --json for the latest machine-readable contract.

Input reference

Get all activities for a specific lead — full conversation thread including sent messages, opens, clicks, and replies.

Name	Type	Required	Default	Details
`payload.lead_id`	`string`	Yes	—	Lemlist lead ID to get activities for Minimum length: 1.
`payload.limit`	`integer`	No	`50`	Max number of activities to return Minimum: 1. Maximum: 100.

Output reference

Standard tool result payload.

Name	Type	Required	Default	Details
`result.data`	`array`	Yes	—	Array of activity objects for this lead, ordered by date
`result.data[].id`	`string`	Yes	—	Unique activity ID
`result.data[]._id`	`string`	No	—	Legacy Lemlist activity ID field
`result.data[].type`	`string`	Yes	—	Activity type (e.g. linkedinReplied, emailsReplied)
`result.data[].text`	`string`	No	—	Full reply content for LinkedIn messages
`result.data[].messagePreview`	`string`	No	—	Truncated reply preview for email messages
`result.data[].subject`	`string`	No	—	Email subject line
`result.data[].leadId`	`string`	No	—	Lemlist lead ID
`result.data[].leadFirstName`	`string`	No	—	Lead first name
`result.data[].leadLastName`	`string`	No	—	Lead last name
`result.data[].leadEmail`	`string`	No	—	Lead email address
`result.data[].firstName`	`string`	No	—	Lead first name (alternate field)
`result.data[].lastName`	`string`	No	—	Lead last name (alternate field)
`result.data[].email`	`string`	No	—	Lead email (alternate field)
`result.data[].fromEmail`	`string`	No	—	Email address the reply came from
`result.data[].jobTitle`	`string`	No	—	Lead job title
`result.data[].companyDomain`	`string`	No	—	Lead company domain
`result.data[].latest_org`	`string`	No	—	Lead company name
`result.data[].linkedinUrl`	`string`	No	—	Lead LinkedIn profile URL
`result.data[].campaignId`	`string`	No	—	Campaign ID this activity belongs to
`result.data[].campaignName`	`string`	No	—	Campaign name
`result.data[].sendUserName`	`string`	No	—	Name of the rep who sent the original message
`result.data[].sendUserEmail`	`string`	No	—	Email of the sending rep
`result.data[].sendUserId`	`string`	No	—	Lemlist user ID of the sending rep
`result.data[].sequenceStep`	`number`	No	—	Which step in the sequence triggered this activity
`result.data[].totalSequenceStep`	`number`	No	—	Total steps in the sequence
`result.data[].sequenceId`	`string`	No	—	Sequence ID
`result.data[].emailTemplateId`	`string`	No	—	Email template ID used
`result.data[].emailTemplateName`	`string`	No	—	Email template name used
`result.data[].isFirst`	`boolean`	No	—	Whether this is the first reply from this lead
`result.data[].stopped`	`boolean`	No	—	Whether the sequence was stopped after this activity
`result.data[].bot`	`boolean`	No	—	Whether this was detected as a bot reply
`result.data[].aiLeadInterestScore`	`number`	No	—	Lemlist AI-scored interest level (0-1). Higher = more interested.
`result.data[].createdAt`	`string`	Yes	—	ISO 8601 timestamp of when the activity occurred
`result.data[].relatedSentAt`	`string`	No	—	ISO 8601 timestamp of when the original message was sent
`result.data[].contactId`	`string`	No	—	Lemlist contact ID
`result.data[].teamId`	`string`	No	—	Lemlist team ID
`result.meta`	`object`	No	—	Additional response metadata (status, paging).

Deepline cost

Pricing model: fixed (per call).
Estimated Deepline credits: 0 per pricing unit.
Provider-native pricing may still exist outside Deepline credit billing.

Get started

Build and automate

Common workflows

Data and integrations

Reference

Lemlist: Get Lead Activity

Run this action

CLI

Example response

Input reference

Output reference

Deepline cost

​Run this action

​CLI

​Example response

​Input reference

​Output reference

​Deepline cost

​Related documentation

Run this action

CLI

Example response

Input reference

Output reference

Deepline cost

Related documentation