// connections

lemlist

Let agents run lemlist campaigns, sequences and leads, contacts, the inbox, activity history, stats and webhooks through superagnt_. Connects with a lemlist API key.

30 mcp tools70 operationsvendor sync

rest: https://api.superagnt.com/v1/connections/lemlist plus the vendor's own path, with your superagnt_ API key as Authorization: Bearer.
mcp: Tools named connection_lemlist_* on https://mcp.superagnt.com/mcp, served once the account is connected.
billing: lemlist bills your own account. Calls cost no superagnt_ data credits.
rate limit: 10 requests a second, 600 a minute: the vendor's ceiling as the registry records it, for sizing bursts. Your plan's own limit is on Connections.
vendor docs: https://developer.lemlist.com
sync: Can copy 6 tables into your workspace database and keep them fresh: the tables.

The lemlist connection lets an agent run multichannel cold outreach on the lemlist team you already prospect from. It builds campaigns with their sequences and schedules, adds and runs leads, keeps contacts, companies, contact lists and notes in order, reads the full activity history (every send, open, click, reply, bounce and LinkedIn action), works the inbox (read threads, send emails and LinkedIn messages, label conversations), manages unsubscribes and tasks, pulls campaign stats and registers webhooks.

one team per connection

A lemlist API key belongs to exactly one lemlist team and there is no team selector, so a connection acts in that team. Each superagnt_ workspace holds one lemlist connection.

Setup

Create an API key. In lemlist open Settings → Team → Integrations and generate an API key. lemlist shows it once, so copy it then. lemlist rate-limits per key, across every tool using it, so a key made just for superagnt_ keeps that budget to itself.
Connect lemlist. In the superagnt app open Integrations, pick lemlist, paste the key and press Connect.

Plans and limits

lemlist allows 20 requests every 2 seconds per API key, shared with everything else using the key, a lemlist sync included. A lemlist 429 reaches you as RATE_LIMITED (HTTP 429): back off and retry. See Connection failures.
findEmail, findPhone, verifyEmail and linkedinEnrichment on add_campaign_lead spend lemlist credits. get_team_credits shows what is left.
launch_lead needs lemlist's emailPro plan or higher.

Things to know

lemlist answers some unknown or undefined resources with HTTP 200. Read the body, not only the status, before reporting what you found.
Activity types are spelled exactly: email types are plural (emailsReplied, emailsBounced) and invites are linkedinInvite*. An unknown type is refused with a 400.
add_campaign_lead never updates a lead: lemlist refuses a contact already in the campaign with LEAD_ALREADY_IN_CAMPAIGN and writes nothing. Change an existing lead with update_campaign_lead.
create_contact_note pushes the note to the team's connected CRM, like a note written in the lemlist app.
delete_contact also deletes the contact's leads, opportunities, list memberships, inbox conversations and activities in lemlist. Nothing is deleted in a connected CRM.
The connection's tools and operations do not cover connecting or disconnecting email accounts and enrichment providers, lemlist's people and company database, enrichment outside add_campaign_lead, lemwarm, signal agents, deliverability alerts, message templates and snippets, WhatsApp and SMS sends outside a sequence, CRM imports, or the custom-variable endpoints that take variable names as query keys.

Leads and contacts

A contact (ctc_...) is the CRM record: identity, company, custom fields, lists and notes. list_contacts, get_contact and upsert_contact work on contacts, and upserting one adds it to no campaign. A custom field must exist in list_fields before upsert_contact can write it.
A lead (lea_...) is that contact's membership in one campaign, with its own state (contacted, interested, paused). add_campaign_lead creates one, with custom variables as extra top-level fields, and the campaign's sequence runs for it once the lead is launched (at once when the campaign auto-reviews). Over MCP, send custom variables and custom fields through connection_lemlist_add_campaign_lead and connection_lemlist_upsert_contact: the grouped tools ignore fields they do not declare.
remove_campaign_lead unsubscribes a lead from its campaign, which stops its sequence. Pass action: "remove" to delete the lead instead.

The `version` argument

get_team, list_campaigns, get_lead and list_activities take a required version argument whose only value is v2. Without it lemlist answers its deprecated v1 shape, so superagnt_ refuses a call that leaves it out (over REST, a 400 VALIDATION_ERROR).

Pagination and history

list_campaigns, list_activities and list_unsubscribes page with offset + limit (at most 100 per page). list_contacts and list_companies page with offset + limit (at most 500).
search_tasks pages with page + limit (at most 100), and page * limit must stay at or under 10,000, so narrow long walks by due or completion date.
list_campaign_leads returns at most 500 leads (limit, default 100) with no paging. To read a whole campaign in one call, use export_campaign_leads with format: "json" (the default is CSV) and state: "all".
The activity history is the change feed. No lemlist record carries an updated-at date, but list_activities keeps the full history and filters on creation time (minDate / maxDate, unix seconds or ISO 8601), type, campaign and lead. On a long walk, narrow maxDate so offsets stay small.
list_inbox_conversations needs a userId, so walk the team's users from get_team to cover the whole inbox. Reading a thread with get_conversation_messages does not mark it read.

Permissions

Each operation starts with a default level. A deployed agent pauses for a person's approval before an Ask or Always ask operation and runs an Act operation straight away. A person can change any level per tool, for one agent or for the whole workspace: see Permissions.

Always ask: starting or pausing a campaign, adding a lead to a campaign, resuming or launching a lead, sending an email or a LinkedIn message, and every delete: sequence steps, schedules, campaign leads (remove_campaign_lead, unsubscribe included), contacts, companies, webhooks and entries on the unsubscribe list.
Ask: adding or changing a sequence step, which goes out to real people on a campaign with leads, and creating a webhook, which sends lemlist events to another address.
Act: every other operation.

Examples

List running campaigns

list running campaignsbash

curl "https://api.superagnt.com/v1/connections/lemlist/campaigns?version=v2&status=running&limit=100" \
  -H "Authorization: Bearer $AGNTDATA_API_KEY"

Read the replies since a date

email replies since a datebash

curl "https://api.superagnt.com/v1/connections/lemlist/activities?version=v2&type=emailsReplied&minDate=2026-10-01T00:00:00Z&limit=100" \
  -H "Authorization: Bearer $AGNTDATA_API_KEY"

Export every lead of a campaign

export every leadbash

curl "https://api.superagnt.com/v1/connections/lemlist/v2/campaigns/$CAMPAIGN_ID/export/leads?format=json&state=all" \
  -H "Authorization: Bearer $AGNTDATA_API_KEY"

Snapshot stats for several campaigns

stats for two campaignsbash

curl -X POST "https://api.superagnt.com/v1/connections/lemlist/v2/campaigns/stats/batch" \
  -H "Authorization: Bearer $AGNTDATA_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "campaignIds": ["cam_aaa", "cam_bbb"],
    "startDate": "2026-10-01T00:00:00.000Z",
    "endDate": "2026-10-07T23:59:59.999Z"
  }'

Add a lead with a custom variable

add a leadbash

curl -X POST "https://api.superagnt.com/v1/connections/lemlist/campaigns/$CAMPAIGN_ID/leads/" \
  -H "Authorization: Bearer $AGNTDATA_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "email": "ada@example.com",
    "firstName": "Ada",
    "companyName": "Analytical Engines",
    "icebreaker": "Saw the engine launch",
    "painPoint": "manual follow-ups"
  }'

painPoint is a custom variable: any extra top-level string field becomes one.

Receiving lemlist webhooks

Create a webhook with create_webhook for one event type, or leave type out to receive every event, team-wide or for one campaign (campaignId). Point it at a superagnt_ inbound webhook endpoint to trigger an agent. lemlist does not sign its deliveries, so leave the endpoint's signature verification off and keep its URL secret. A few rules from lemlist:

A target URL can be registered once per team, whatever its type or campaign. Give each subscription its own URL (a query-string variant works).
A team holds at most 200 webhooks, disabled ones included.
The optional secret comes back as a secret field in the body of every delivery. It is a shared value to compare, not a signature, and it cannot be read back or changed: delete and recreate the webhook to rotate it.
lemlist disables, but never deletes, a webhook whose endpoint answers 404 or 410 or does not resolve. list_webhooks shows disabled and disabledReason. A webhook cannot be switched back on, so delete it and create it again once the endpoint is back.

Sync

A lemlist sync copies your team's campaigns, sequence steps, campaign leads, activity, unsubscribes and daily campaign stats into your workspace database. Turn it on from the Sync panel on the lemlist connection page in the superagnt app. The panel previews the rows and webhook events against your plan before anything is created. agnt_sync_catalog lists every table and column. How syncs work in general: Vendor sync.

How updates arrive. The sync registers its own lemlist webhooks, one for each event type and never with a secret, for email and LinkedIn replies, accepted LinkedIn invites, interested and not-interested marks, bounces and unsubscribes. Each of these deliveries makes the sync pull the latest activity and re-read the campaign it names with its leads, and an unsubscribe also refreshes the unsubscribe list. Sends, opens and clicks arrive by polling, because every delivery counts toward your webhook events: switch any of them to a webhook in Customize. If lemlist disables one of the sync's webhooks, the sync deletes it and registers it again.

Scope and limits.

The one filter is campaigns. It narrows every table except unsubscribes, which cover the whole team.
With a campaign filter, each event type gets one webhook per selected campaign while that stays at or under 50 webhooks (seven campaigns with the default events). Past that the webhooks are team-wide: other campaigns' deliveries still count toward your webhook events before the sync drops them, and the preview warns you.
A lemlist team holds at most 200 webhooks, disabled ones included. At the cap the sync says so and polls instead.
lemlist's 20 requests per 2 seconds are shared by everything using the key, so the sync keeps to 12 and leaves the rest to your agents and other tools.
The sync only reads, apart from managing its own webhooks, and never marks anything read in lemlist.

08// sync tables

What a lemlist sync copies

A sync copies these tables into your workspace database and keeps them fresh, so an agent reads local rows instead of calling lemlist on every run. Turn tables on and off from the Sync panel on the connection. Every table also carries _raw, _hash, _synced_at and _deleted_at. How syncs work: Vendor sync.

beta

The lemlist sync is built from lemlist's API documentation and has not been verified against a live lemlist account yet. A field the documentation does not show stays in each row's _raw column.

Table	What it holds	Default
`lemlist_campaigns` Campaigns	Every campaign in the team with its status, re-read every hour; campaigns lemlist no longer returns are marked deleted.	on
`lemlist_sequence_steps` Sequence steps	Each campaign's sequence steps (email, LinkedIn and other steps, with conditional branches), re-read daily with the campaigns.	on
`lemlist_campaign_leads` Campaign leads	One row per lead in each campaign with its latest state, read from the campaign export: running and paused campaigns every hour, every campaign nightly, and a campaign as soon as a webhook names it.	on
`lemlist_activities` Activities	Every campaign activity (sends, opens, clicks, replies, LinkedIn steps, bounces, unsubscribes), one row each. Kept for 90 days by default.	on
`lemlist_unsubscribes` Unsubscribes	Unsubscribed addresses at campaign, team or global scope, re-read daily.	on
`lemlist_campaign_daily_stats` Campaign daily stats	Per campaign and day (UTC): messages sent, opens, clicks, replies, bounces and interested leads. Days with no activity are not stored. The last 7 days are re-read daily because counts land late. Kept for 90 days by default.	on

09// mcp tools

30 tools, one per resource and risk

MCP servers and agents on the grouped surface list lemlist as these tools. Each takes an action, and the ones that work across record types an object. Every operation also keeps its own per-operation name, in the next table, which works on every server. How grouping works: Grouped tools.

Tool	Risk	Actions
`connection_lemlist_team_read` Read the lemlist team Read the team this key belongs to (one key is one team) with its members' user ids, the members sending for campaigns, the remaining credits, one member's mailboxes and LinkedIn account, or the contact and company fields.	read	teamsenderscreditsuserfields
`connection_lemlist_campaigns_read` Read lemlist campaigns List campaigns or get one, run the checks lemlist makes before a campaign can launch, read a campaign's sequences and steps (the ids connection_lemlist_sequence_steps_write takes), or read one campaign's stats over a date range. Stats of many campaigns at once: connection_lemlist_analytics_read.	read	listgetlaunch_checkssequencesstats
`connection_lemlist_campaigns_write` Create and run lemlist campaigns Create a draft campaign, change its settings and senders, copy one, or start or pause it. Starting sends the campaign's steps to every launched lead on its schedule, to real people: run launch_checks on connection_lemlist_campaigns_read first. Leave autoReview off unless the person asked for auto-launch: with it on, every lead added later launches at once.	write	createupdateduplicatestartpause
`connection_lemlist_sequence_steps_write` Add and edit lemlist sequence steps Add a step to a campaign sequence (an email, a LinkedIn action, a call, a manual task, a condition, a WhatsApp or SMS message, an API call, or a move to another campaign), or change one. On a campaign with leads, a new or changed step reaches every lead that has not passed it yet, so it goes out to real people. Sequence and step ids: connection_lemlist_campaigns_read action "sequences".	write	addupdate
`connection_lemlist_sequence_steps_delete` Delete a lemlist sequence step Delete a step from a campaign sequence. It cannot be restored.	destructive	delete
`connection_lemlist_schedules_read` Read lemlist sending schedules Read the sending schedules (active weekdays, hours, timezone, seconds between sends): list them, get one, or list the ones attached to a campaign.	read	listgetfor_campaign
`connection_lemlist_schedules_write` Manage lemlist sending schedules Create a sending schedule, change one (every campaign using it follows the new days and hours), or attach one to a campaign so the campaign sends on its days and hours.	write	createupdateattach
`connection_lemlist_schedules_delete` Delete a lemlist sending schedule Delete a sending schedule.	destructive	delete
`connection_lemlist_campaign_leads_read` Read lemlist campaign leads Get a lead (a person's membership in one campaign) by email or id, list up to 500 of a campaign's leads, or export every lead of a campaign in one call.	read	getlistexport
`connection_lemlist_campaign_leads_write` Add and run lemlist campaign leads Add a person to a campaign as a new lead, update a lead, pause, resume or launch it, or mark it interested or not. A launched or resumed lead gets the sequence, sent to a real person, and a lead added to an auto-review campaign launches at once. findEmail, findPhone, verifyEmail and linkedinEnrichment on add spend lemlist credits. Removing or unsubscribing a lead: connection_lemlist_remove_campaign_lead.	write	addupdatepauseresumelaunchmark_interestedmark_not_interested
`connection_lemlist_contacts_read` Read lemlist contacts Look contacts up by ids, emails or connected-CRM ids, search and list them, get one with its campaigns and unsubscribe state, or read its notes. A contact is the CRM record; a lead is that contact's membership in one campaign.	read	listgetnotes
`connection_lemlist_contacts_write` Add and update lemlist contacts Create a contact or update the one matching its email or LinkedIn URL (it joins no campaign), or write a note on a contact, which is pushed to the team's connected CRM. Custom fields must exist first: connection_lemlist_team_read action "fields".	write	upsertadd_note
`connection_lemlist_contacts_delete` Delete a lemlist contact Delete a contact and, with it, its leads, opportunities, list memberships, inbox conversations and activities in lemlist. Nothing is deleted in a connected CRM.	destructive	delete
`connection_lemlist_contact_lists_read` Read lemlist contact lists List the team's static and dynamic contact lists, newest first, optionally by name. A list's contacts: connection_lemlist_contacts_read action "list" with listId.	read	list
`connection_lemlist_contact_lists_write` Create a lemlist contact list Create a static contact list. Adding contacts to a list or removing them: connection_lemlist_update_contact_list_members.	write	create
`connection_lemlist_companies_read` Read lemlist companies Look companies up by ids, domains or connected-CRM ids, list and search them, or get one by id.	read	listget
`connection_lemlist_companies_write` Add and update lemlist companies Create a company or update the one matching its domain or LinkedIn URL. Custom fields must exist first: connection_lemlist_team_read action "fields".	write	upsert
`connection_lemlist_companies_delete` Delete a lemlist company Delete a company in lemlist; nothing is deleted in a connected CRM. With contacts attached it is refused unless force is true, which detaches them first. The user behind the key needs the "Delete companies" permission.	destructive	delete
`connection_lemlist_analytics_read` Read lemlist stats and activity Read the stats of up to 100 campaigns in one call over a date range, or the team's activity history: every send, open, click, reply, bounce, LinkedIn action, call, task and lifecycle event. One campaign's stats: connection_lemlist_campaigns_read action "stats".	read	stats_batchactivities
`connection_lemlist_inbox_read` Read the lemlist inbox Read one member's inbox conversations with their messages, the message thread with a contact across channels (reading it does not mark it read), or the team's inbox labels.	read	conversationsmessageslabels
`connection_lemlist_inbox_write` Label lemlist conversations Add labels to the conversation with a contact, or replace its labels (appendLabels false). Nothing is sent: connection_lemlist_inbox_send sends.	write	set_labels
`connection_lemlist_inbox_send` Send a lemlist email or LinkedIn message Send an email or a LinkedIn message right away, from a team member's mailbox or LinkedIn account. It reaches a real person, so get the user's sign-off first; on a deployed agent, a send asks for approval by default. The sender's ids come from connection_lemlist_team_read action "user".	write	emaillinkedin
`connection_lemlist_unsubscribes_read` Read the lemlist unsubscribe list List the emails unsubscribed from the team or a campaign, check one address, list every unsubscribed value (emails, domains, LinkedIn URLs, phone numbers), or check whether a contact is do-not-contact.	read	listgetvaluescontact_status
`connection_lemlist_unsubscribes_write` Unsubscribe people in lemlist Add an email address or domain to the team's unsubscribe list so no campaign contacts it again, or mark a contact do-not-contact for the whole team. Taking an address off the list: connection_lemlist_unsubscribes_delete.	write	addcontact
`connection_lemlist_unsubscribes_delete` Remove from the lemlist unsubscribe list Remove an email address from the team's unsubscribe list, so campaigns can contact it again.	destructive	remove
`connection_lemlist_tasks_read` Search lemlist tasks Search the team's tasks (calls, manual steps, LinkedIn and email tasks) by contact, company, lead, campaign, assignee, channel, status, title, due date or completion date.	read	search
`connection_lemlist_tasks_write` Create and update lemlist tasks Create a task about a contact, company or lead for a team member with a due date, or change one or mark it done. A task's drafted message is not sent until a person completes the task in lemlist.	write	createupdate
`connection_lemlist_webhooks_read` Read lemlist webhooks List the team's webhooks with their URL, event type, campaign scope, and whether lemlist disabled them: it disables, but never deletes, a webhook whose endpoint answers 404 or 410 or does not resolve.	read	list
`connection_lemlist_webhooks_write` Create a lemlist webhook Register a URL that lemlist POSTs events to. A URL can be registered once per team, whatever its type or campaign, and a team holds at most 200 webhooks, disabled ones included. secret comes back as a field in every delivery's body (a shared value, not a signature) and cannot be changed: delete and recreate the webhook to rotate it.	write	create
`connection_lemlist_webhooks_delete` Delete a lemlist webhook Delete a webhook; lemlist stops sending events to its URL.	destructive	delete

10// operations

All 70 operations

Each operation is a REST path under https://api.superagnt.com/v1/connections/lemlist and an MCP tool. The per-operation tool name is the one permissions, approvals and usage records use.

Operation	MCP tool
GET`/team` Get Team	`connection_lemlist_get_team`grouped: `connection_lemlist_team_read`, action `team`
GET`/team/senders` Get Team Senders	`connection_lemlist_list_team_senders`grouped: `connection_lemlist_team_read`, action `senders`
GET`/team/credits` Get Team Credits	`connection_lemlist_get_team_credits`grouped: `connection_lemlist_team_read`, action `credits`
GET`/users/{userId}` Get User	`connection_lemlist_get_user`grouped: `connection_lemlist_team_read`, action `user`
GET`/fields` List Fields	`connection_lemlist_list_fields`grouped: `connection_lemlist_team_read`, action `fields`
GET`/campaigns` Get Many Campaigns	`connection_lemlist_list_campaigns`grouped: `connection_lemlist_campaigns_read`, action `list`
POST`/campaigns` Create Campaign	`connection_lemlist_create_campaign`grouped: `connection_lemlist_campaigns_write`, action `create`
GET`/campaigns/{campaignId}` Get Campaign	`connection_lemlist_get_campaign`grouped: `connection_lemlist_campaigns_read`, action `get`
PATCH`/campaigns/{campaignId}` Update Campaign	`connection_lemlist_update_campaign`grouped: `connection_lemlist_campaigns_write`, action `update`
POST`/campaigns/{campaignId}/start` Start Campaign	`connection_lemlist_start_campaign`grouped: `connection_lemlist_campaigns_write`, action `start`
POST`/campaigns/{campaignId}/pause` Pause Campaign	`connection_lemlist_pause_campaign`grouped: `connection_lemlist_campaigns_write`, action `pause`
POST`/campaigns/{campaignId}/duplicate` Duplicate Campaign	`connection_lemlist_duplicate_campaign`grouped: `connection_lemlist_campaigns_write`, action `duplicate`
GET`/campaigns/{campaignId}/statutes` Get Campaign Statutes	`connection_lemlist_get_campaign_statutes`grouped: `connection_lemlist_campaigns_read`, action `launch_checks`
GET`/v2/campaigns/{campaignId}/stats` Get Campaign Stats	`connection_lemlist_get_campaign_stats`grouped: `connection_lemlist_campaigns_read`, action `stats`
POST`/v2/campaigns/stats/batch` Get Batch Campaign Stats	`connection_lemlist_get_campaign_stats_batch`grouped: `connection_lemlist_analytics_read`, action `stats_batch`
GET`/v2/campaigns/{campaignId}/export/leads` Export Campaign Leads	`connection_lemlist_export_campaign_leads`grouped: `connection_lemlist_campaign_leads_read`, action `export`
GET`/campaigns/{campaignId}/sequences` Get Campaign Sequences	`connection_lemlist_get_campaign_sequences`grouped: `connection_lemlist_campaigns_read`, action `sequences`
POST`/sequences/{sequenceId}/steps` Add Step to Sequence	`connection_lemlist_add_sequence_step`grouped: `connection_lemlist_sequence_steps_write`, action `add`
PATCH`/sequences/{sequenceId}/steps/{stepId}` Update Sequence Step	`connection_lemlist_update_sequence_step`grouped: `connection_lemlist_sequence_steps_write`, action `update`
DELETE`/sequences/{sequenceId}/steps/{stepId}` Delete Sequence Step	`connection_lemlist_delete_sequence_step`grouped: `connection_lemlist_sequence_steps_delete`, action `delete`
GET`/schedules` Get Many Schedules	`connection_lemlist_list_schedules`grouped: `connection_lemlist_schedules_read`, action `list`
POST`/schedules` Create Schedule	`connection_lemlist_create_schedule`grouped: `connection_lemlist_schedules_write`, action `create`
GET`/schedules/{scheduleId}` Get Schedule	`connection_lemlist_get_schedule`grouped: `connection_lemlist_schedules_read`, action `get`
PATCH`/schedules/{scheduleId}` Update Schedule	`connection_lemlist_update_schedule`grouped: `connection_lemlist_schedules_write`, action `update`
DELETE`/schedules/{scheduleId}` Delete Schedule	`connection_lemlist_delete_schedule`grouped: `connection_lemlist_schedules_delete`, action `delete`
GET`/campaigns/{campaignId}/schedules/` Get Campaign Schedules	`connection_lemlist_list_campaign_schedules`grouped: `connection_lemlist_schedules_read`, action `for_campaign`
POST`/campaigns/{campaignId}/schedules/{scheduleId}` Associate Schedule with Campaign	`connection_lemlist_set_campaign_schedule`grouped: `connection_lemlist_schedules_write`, action `attach`
GET`/leads` Get Lead by Email or ID	`connection_lemlist_get_lead`grouped: `connection_lemlist_campaign_leads_read`, action `get`
GET`/campaigns/{campaignId}/leads/` Get Campaign Leads	`connection_lemlist_list_campaign_leads`grouped: `connection_lemlist_campaign_leads_read`, action `list`
POST`/campaigns/{campaignId}/leads/` Create Lead in Campaign	`connection_lemlist_add_campaign_lead`grouped: `connection_lemlist_campaign_leads_write`, action `add`
PATCH`/campaigns/{campaignId}/leads/{leadId}` Update Lead in a Campaign	`connection_lemlist_update_campaign_lead`grouped: `connection_lemlist_campaign_leads_write`, action `update`
DELETE`/campaigns/{campaignId}/leads/{leadId}` Delete or Unsubscribe Lead	`connection_lemlist_remove_campaign_lead`grouped servers list it under this name
POST`/leads/pause/{leadId}` Pause Lead	`connection_lemlist_pause_lead`grouped: `connection_lemlist_campaign_leads_write`, action `pause`
POST`/leads/start/{leadId}` Resume Paused Lead	`connection_lemlist_resume_lead`grouped: `connection_lemlist_campaign_leads_write`, action `resume`
POST`/leads/review/{leadId}` Launch Lead	`connection_lemlist_launch_lead`grouped: `connection_lemlist_campaign_leads_write`, action `launch`
POST`/campaigns/{campaignId}/leads/{leadIdOrEmail}/interested` Mark Lead as Interested in Campaign	`connection_lemlist_mark_campaign_lead_interested`grouped: `connection_lemlist_campaign_leads_write`, action `mark_interested`
POST`/campaigns/{campaignId}/leads/{leadIdOrEmail}/notinterested` Mark Lead as Not Interested in Campaign	`connection_lemlist_mark_campaign_lead_not_interested`grouped: `connection_lemlist_campaign_leads_write`, action `mark_not_interested`
GET`/contacts` Get Many Contacts	`connection_lemlist_list_contacts`grouped: `connection_lemlist_contacts_read`, action `list`
POST`/contacts` Add and update contact	`connection_lemlist_upsert_contact`grouped: `connection_lemlist_contacts_write`, action `upsert`
GET`/contacts/{idOrEmail}` Get Contact	`connection_lemlist_get_contact`grouped: `connection_lemlist_contacts_read`, action `get`
DELETE`/contacts/{idOrEmail}` Delete Contact	`connection_lemlist_delete_contact`grouped: `connection_lemlist_contacts_delete`, action `delete`
GET`/contacts/{idOrEmail}/notes` Get Contact Notes	`connection_lemlist_list_contact_notes`grouped: `connection_lemlist_contacts_read`, action `notes`
POST`/contacts/{idOrEmail}/notes` Create Contact Note	`connection_lemlist_create_contact_note`grouped: `connection_lemlist_contacts_write`, action `add_note`
GET`/contacts/lists` Get Contact Lists	`connection_lemlist_list_contact_lists`grouped: `connection_lemlist_contact_lists_read`, action `list`
POST`/contacts/lists` Create Contact List	`connection_lemlist_create_contact_list`grouped: `connection_lemlist_contact_lists_write`, action `create`
POST`/contacts/lists/{listId}/entities` Add or Remove Contacts in a List	`connection_lemlist_update_contact_list_members`grouped servers list it under this name
GET`/companies` Get Many Companies	`connection_lemlist_list_companies`grouped: `connection_lemlist_companies_read`, action `list`
POST`/companies` Add and update company	`connection_lemlist_upsert_company`grouped: `connection_lemlist_companies_write`, action `upsert`
GET`/companies/{companyId}` Get Company	`connection_lemlist_get_company`grouped: `connection_lemlist_companies_read`, action `get`
DELETE`/companies/{companyId}` Delete Company	`connection_lemlist_delete_company`grouped: `connection_lemlist_companies_delete`, action `delete`
GET`/activities` Get Many Activities	`connection_lemlist_list_activities`grouped: `connection_lemlist_analytics_read`, action `activities`
GET`/inbox` Get Many Inboxes	`connection_lemlist_list_inbox_conversations`grouped: `connection_lemlist_inbox_read`, action `conversations`
GET`/inbox/{contactId}` Get Contact Messages	`connection_lemlist_get_conversation_messages`grouped: `connection_lemlist_inbox_read`, action `messages`
POST`/inbox/email` Send Email	`connection_lemlist_send_email`grouped: `connection_lemlist_inbox_send`, action `email`
POST`/inbox/linkedin` Send LinkedIn Message	`connection_lemlist_send_linkedin_message`grouped: `connection_lemlist_inbox_send`, action `linkedin`
GET`/inbox/labels` Get Many Labels	`connection_lemlist_list_inbox_labels`grouped: `connection_lemlist_inbox_read`, action `labels`
POST`/inbox/conversations/labels/{contactId}` Attach Labels to Conversations	`connection_lemlist_set_conversation_labels`grouped: `connection_lemlist_inbox_write`, action `set_labels`
GET`/unsubscribes` Get Many Unsubscribes	`connection_lemlist_list_unsubscribes`grouped: `connection_lemlist_unsubscribes_read`, action `list`
GET`/unsubscribes/{email}` Get Unsubscribe by Email	`connection_lemlist_get_unsubscribe`grouped: `connection_lemlist_unsubscribes_read`, action `get`
POST`/unsubscribes/{email}` Add Unsubscribe Email or Domain	`connection_lemlist_add_unsubscribe`grouped: `connection_lemlist_unsubscribes_write`, action `add`
DELETE`/unsubscribes/{email}` Delete Unsubscribe Email	`connection_lemlist_delete_unsubscribe`grouped: `connection_lemlist_unsubscribes_delete`, action `remove`
GET`/v2/unsubscribes/variables` List Unsubscribed Variables	`connection_lemlist_list_unsubscribed_variables`grouped: `connection_lemlist_unsubscribes_read`, action `values`
GET`/v2/unsubscribes/contacts/{contactId}` Get Contact Subscription Status	`connection_lemlist_get_contact_unsubscribe_status`grouped: `connection_lemlist_unsubscribes_read`, action `contact_status`
POST`/v2/unsubscribes/contacts/{contactId}` Unsubscribe Contact	`connection_lemlist_unsubscribe_contact`grouped: `connection_lemlist_unsubscribes_write`, action `contact`
GET`/v2/tasks` Search Tasks	`connection_lemlist_search_tasks`grouped: `connection_lemlist_tasks_read`, action `search`
POST`/tasks` Create Task	`connection_lemlist_create_task`grouped: `connection_lemlist_tasks_write`, action `create`
PATCH`/tasks` Update Task	`connection_lemlist_update_task`grouped: `connection_lemlist_tasks_write`, action `update`
GET`/hooks` Get Many Webhooks	`connection_lemlist_list_webhooks`grouped: `connection_lemlist_webhooks_read`, action `list`
POST`/hooks` Add Webhook	`connection_lemlist_create_webhook`grouped: `connection_lemlist_webhooks_write`, action `create`
DELETE`/hooks/{hookId}` Delete Webhook	`connection_lemlist_delete_webhook`grouped: `connection_lemlist_webhooks_delete`, action `delete`