lemlist is a prospecting tool that automates multichannel outreach, enabling users to find leads with valid contact information and reach them across email, LinkedIn, or calls with personalized messages.
lemlist is a prospecting tool that automates multichannel outreach, enabling users to find leads with valid contact information and reach them across email, LinkedIn, or calls with personalized messages. On Nagent, Lemlist is exposed as a fully-configurable marketing automation integration that any agent can call — 54 actions, and API key authentication. No code is required to wire Lemlist into your workflow — connect it once via the External Integrations panel and reuse it across every agent you build.
Agent builders use Lemlist to automate the kinds of tasks marketing automation teams previously handled manually. Concrete examples — each one is a single agent step in Nagent — include:
Every action and trigger is paired with a structured input/output schema (visible in the sections below), so when you wire Lemlist into Helix — our agentic agent builder — the editor knows exactly what each step expects and produces. Configure once, deploy anywhere across your Nagent agents.
Every operation an agent can call against Lemlist, with input parameters and output schema. Drop these into any step of an agent built in Helix.
LEMLIST_CREATE_COMPANY_NOTETool to create a note attached to a specific company. Use when you need to add annotations or notes to a company record for tracking purposes.
Input parameters
The note content to be created for the company.
The unique identifier of the company to attach the note to.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
LEMLIST_DELETE_DELETE_SCHEDULETool to delete a specific schedule by scheduleId. Use when you need to remove a schedule permanently after confirming its ID.
Input parameters
The unique ID of the schedule to delete
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
LEMLIST_DELETE_DELETE_UNSUBSCRIBE_EMAILTool to delete an email from the unsubscribed list. Use when restoring a subscriber who has opted back in and you need to remove them from the suppressed contacts.
Input parameters
The email address to remove from the unsubscribed list
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
LEMLIST_DELETE_UNSUBSCRIBE_LEAD_FROM_CAMPAIGNTool to unsubscribe a lead from a campaign. Use when you need to stop further outreach by removing a lead from the specified campaign.
Input parameters
The unique ID of the lead to unsubscribe
The unique ID of the campaign from which the lead will be unsubscribed
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
LEMLIST_GET_ALL_WEBHOOKSTool to retrieve the list of all webhooks configured for the team. Use when you need to sync or audit active webhooks.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
LEMLIST_GET_CAMPAIGN_BY_IDTool to retrieve a specific campaign by campaignId. Use when you need detailed campaign information by ID.
Input parameters
Unique identifier of the campaign to retrieve.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
LEMLIST_GET_CAMPAIGN_EXPORT_STARTTool to start an asynchronous export of all campaign statistics (CSV). Use when you need to initiate a CSV export for a given campaign and track its progress.
Input parameters
Unique identifier of the campaign to export.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
LEMLIST_GET_CAMPAIGN_EXPORT_STATUSTool to check the status of an asynchronous campaign export. Use after starting an export to poll until done or error.
Input parameters
The ID of the export job returned from the start export endpoint.
The ID of the campaign whose export is being checked.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
LEMLIST_GET_CAMPAIGN_SEQUENCESTool to retrieve a list of all sequences for a campaign with steps and conditions. Use after fetching campaign to inspect its nested sequences and branching rules.
Input parameters
Unique identifier of the campaign to fetch sequences for.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
LEMLIST_GET_CAMPAIGN_STATSTool to retrieve performance statistics for a specific campaign within a date range. Use when you need campaign analytics including lead engagement, message delivery, and step-by-step performance metrics.
Input parameters
End date for the statistics period in ISO 8601 format (e.g., 2026-02-14T23:59:59.999Z).
Filter by communication channels. Valid values include 'email', 'linkedin'.
Filter statistics by specific user. Format: sendUserId\\ | sendUserEmail
Start date for the statistics period in ISO 8601 format (e.g., 2025-01-01T00:00:00.000Z).
Filter by A/B test variant. Valid values: 'A' or 'B'.
Unique identifier of the campaign to retrieve statistics for.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
LEMLIST_GET_COMPANIES_SCHEMATool to retrieve the schema definition for companies in the people database. Use when you need to understand the structure, fields, and data types available for company records.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
LEMLIST_GET_CONTACT_MESSAGESTool to retrieve all messages exchanged with a specific contact. Use when you need to fetch conversation history for a contact by their contactId.
Input parameters
Number of items to skip for pagination (default: 0)
Maximum number of messages to retrieve
Identifier of the user viewing the conversation. Required if markAsRead is provided.
The unique identifier of the contact (format: ctc_*)
When true, marks the conversation as read (default: false). Requires userId to be provided.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
LEMLIST_GET_DATABASE_FILTERSTool to retrieve available filters for searching the people and companies database. Use when you need to discover what search criteria are available before querying the database.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
LEMLIST_GET_EXPORT_CAMPAIGN_LEADSTool to export campaign leads with state filtering and choose between JSON or CSV output. Use when you need to download leads and their statuses for reporting or analysis.
Input parameters
Filter to export only the specified leads' last state. Specify one of the global states: imported, scanned, skipped, reviewed, contacted, hooked, attracted, warmed, interested, notInterested, emailsBounced, emailsUnsubscribed, meetingBooked, paused, failed; or detailed states: emailsSent, emailsOpened, emailsClicked, emailsReplied, emailsInterested, emailsNotInterested, emailsFailed, opportunitiesDone, aircallDone, aircallInterested, aircallNotInterested, apiDone, apiInterested, apiNotInterested, linkedinVisitDone, linkedinVisitFailed, linkedinInviteDone, linkedinInviteAccepted, linkedinInviteFailed, linkedinSent, linkedinOpened, linkedinReplied, linkedinInterested, linkedinNotInterested, linkedinSendFailed, manualInterested, manualNotInterested. Use 'all' to export all leads regardless of state.
Output format for the export. Choose 'json' or 'csv'.
The ID of the campaign to export leads from.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
LEMLIST_GET_EXPORT_UNSUBSCRIBESTool to download a CSV file containing all unsubscribed email addresses. Use when you need to export the full unsubscribes list for analysis or archival.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
LEMLIST_GET_GET_UNSUBSCRIBE_EMAILTool to retrieve a single unsubscribed email record. Use when you need to verify if a specific email has opted out of campaigns before re-subscribing them.
Input parameters
Email address of the unsubscribed user to retrieve
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
LEMLIST_GET_LABELTool to retrieve information about a specific label by its ID. Use when you need details about an inbox label.
Input parameters
Unique identifier of the label to retrieve.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
LEMLIST_GET_LIST_CAMPAIGNSTool to retrieve a list of campaigns for the team. Use when you need to discover campaign IDs, names, or statuses before performing operations like auditing or pausing campaigns.
Input parameters
Page number to retrieve (alternative to offset).
Maximum number of campaigns to retrieve. Default: 100, Max: 100.
Pagination offset - number of campaigns to skip.
Field to sort by. Currently only supports 'createdAt'.
Filter campaigns by status.
Sort order: ascending or descending.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
LEMLIST_GET_LIST_TASKSTool to retrieve all pending tasks assigned to team members. Use when you need to view tasks by campaign, assignee, or other filters. Completed tasks are automatically excluded from results.
Input parameters
Page number (0-indexed). Default: 0.
JSON array of filter objects as a string. Available filters: fullName, email, phone, linkedin, campaignId, campaignState, type, assignedTo, dueDate. Must be valid JSON array format (e.g., '\[\]' or '\[{"campaignId":"abc123"}\]'). Empty array returns all tasks.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
LEMLIST_GET_LIST_TEAM_SENDERSTool to retrieve all team members and their associated campaigns. Use when you need to discover which team members are managing which campaigns or to understand campaign distribution across the team.
Input parameters
Valid campaign states for filtering.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
LEMLIST_GET_LIST_WATCHLIST_SIGNALSTool to retrieve paginated watchlist signals with filtering and sorting. Use when you need to fetch signals from watchlists based on type, status, date range, or specific watchlist ID.
Input parameters
Page number to retrieve (cannot be used with offset).
Filter by signal type(s) such as 'jobChange', 'companyIsHiring', 'companyRaisedFunds', 'newHire', 'companyEmployeeVisitedMyWebsite', 'linkedinProfile', 'linkedinTopic'.
Number of signals to retrieve. Maximum value: 100.
Number of records to skip (cannot be used with page).
Fields available for sorting watchlist signals.
Filter by signal status(es) like 'new', 'old', 'handled', or 'ignored'.
Sort order direction.
Filter signals by specific watchlist ID.
Filter signals received on or before this date (ISO date-time format).
Filter signals received on or after this date (ISO date-time format).
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
LEMLIST_GET_PEOPLE_SCHEMATool to retrieve the schema definition for people in the people database. Use when you need to understand available fields and their structure before querying or importing people data.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
LEMLIST_GET_RETRIEVE_ACTIVITIESTool to fetch recent campaign activities. Use after authentication to retrieve activities filtered by campaignId, type, or limit.
Input parameters
Filter activities by type, e.g., 'paused', 'linkedinInviteAccepted', 'emailSent'.
Maximum number of activities to retrieve. Default: 100, Max: 100.
Filter activities by lead ID.
Number of records to skip for pagination.
Filter for first activity only.
Filter activities by contact ID.
Filter activities by specific campaign ID.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
LEMLIST_GET_RETRIEVE_LEAD_BY_EMAILTool to retrieve a lead by their email address. Use when you have a lead's email to fetch complete lead details.
Input parameters
Email address of the lead to retrieve.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
LEMLIST_GET_RETRIEVE_UNSUBSCRIBESTool to retrieve the list of all people who are unsubscribed. Use when you need to sync or audit unsubscribed contacts across your campaigns.
Input parameters
Maximum number of unsubscribes to retrieve per request. Default: 100, Max: 100.
Number of records to skip for pagination.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
LEMLIST_GET_TEAM_CREDITSTool to retrieve credits left in the team. Use after authenticating your session.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
LEMLIST_GET_TEAM_INFOTool to retrieve information about your team. Use after authentication to inspect current team settings, members, webhooks, and enabled features. Verify the returned teamId matches the intended workspace before passing it to campaign-creation or other write operations to avoid creating resources in the wrong account context.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
LEMLIST_GET_USERTool to retrieve all information for a specific user by their ID. Use when you have a user ID to fetch complete user details including LinkedIn settings and connected mailboxes.
Input parameters
Unique identifier of the user to retrieve.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
LEMLIST_GET_USER_INFOTool to retrieve all information of the authenticated user. Use after confirming a valid access token.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
LEMLIST_LIST_COMPANIESTool to retrieve a paginated list of all companies in your CRM. Use when you need to discover companies, search by name, or fetch company details for further operations.
Input parameters
Page number to retrieve.
Quantity of companies to retrieve per page. Default: 100, Max: 100.
Specify returned fields as comma-separated list. Omit to get all fields.
Search by company name (case insensitive).
Field to sort by. Currently only supports 'createdAt'.
Sort direction: 'desc' for descending, other values for ascending.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
LEMLIST_LIST_COMPANY_NOTESTool to retrieve all notes associated with a specific company. Use when you need to view annotations, comments, or activities logged against a company record.
Input parameters
Page number for pagination.
Number of notes to retrieve; default 100, max 100.
Sort field; currently supports 'createdAt'.
Unique identifier of the company to retrieve notes for.
Sort direction ('asc' or 'desc'); defaults to ascending.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
LEMLIST_LIST_LABELSTool to list all labels available to your team. Use when you need to retrieve the full list of labels for inbox organization or filtering.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
LEMLIST_PATCH_MARK_LEAD_AS_NOT_INTERESTED_IN_CAMPAIGNTool to mark a lead as not interested in a specific campaign. Use after confirming campaign and lead IDs to set status to not_interested.
Input parameters
The unique identifier of the campaign.
The unique identifier of the lead or the lead's email address.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
LEMLIST_PATCH_UPDATE_CAMPAIGNTool to update settings of a campaign. Use after fetching or creating a campaign to adjust name, stop-on behaviors, and other campaign flags.
Input parameters
New name for the campaign.
Identifier of the campaign to update.
Enable or disable sharing of the sequence.
Automatically determine lead interest.
Disable email open tracking.
Disable email click tracking.
Disable reply tracking.
Whether the campaign should stop on any link click.
Mark opportunity when clicked.
Mark opportunity when replied.
Whether the campaign should stop when an email is replied to.
Whether the campaign should stop when a meeting is booked.
Pause leads when they show interest.
URL filter for stopping on link click; set to null to unset.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
LEMLIST_PATCH_UPDATE_SCHEDULETool to update an existing schedule with new parameters. Use after retrieving schedule details to adjust days, time window, and limits.
Input parameters
List of weekdays when sends are allowed. e.g., \['monday','tuesday','wednesday'\].
New name for the schedule.
Whether the schedule is active (true) or paused (false).
Daily send window end time in HH:mm format. e.g., '17:30'.
IANA timezone for the schedule. e.g., 'Europe/Paris'.
Maximum number of sends allowed per day.
Daily send window start time in HH:mm format. e.g., '09:00'.
Identifier of the schedule to update.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
LEMLIST_PATCH_UPDATE_SEQUENCE_STEPTool to update an existing step in a sequence (edit subject/message/delay/etc.) by sequenceId and stepId. Use after retrieving sequences to modify step content or timing.
Input parameters
Valid HTTP/HTTPS URL for API call. Only applicable for 'api' type steps.
Type of the step (required but cannot be changed; must match existing step type). Valid types: 'email', 'linkedinInvite', 'linkedinView', 'linkedinSend', 'manual', 'phone', 'whatsappMessage', 'api', 'conditional', 'sendToAnotherCampaign'.
Delay in hours before step execution. Not applicable for 'sendToAnotherCampaign' type.
Manual task label. Only applicable for 'manual' type steps.
HTTP verb for API call. Only applicable for 'api' type steps.
Unique identifier of the step to update.
Message content. Applicable for 'email', 'manual', 'phone', LinkedIn types, and 'whatsappMessage' steps.
Email subject line. Only applicable for 'email' type steps.
Timing logic for conditional steps. Only applicable for 'conditional' type steps.
Fallback message. Only applicable for 'linkedinSend' type steps.
Destination campaign ID. Only applicable for 'sendToAnotherCampaign' type steps.
Unique identifier of the sequence containing the step.
Behavior trigger identifier. Only applicable for 'conditional' type steps.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
LEMLIST_POST_ADD_STEP_TO_SEQUENCETool to add a new step (email, LinkedIn, conditional, etc.) to an existing sequence. Use when building or editing campaign sequences to add outreach steps.
Input parameters
URL of the API endpoint to call. Required for api steps. Must start with http:// or https://
The type of step to create. Must be one of: email, manual, phone, api, linkedinVisit, linkedinInvite, linkedinSend, sendToAnotherCampaign, conditional, whatsappMessage
Delay in seconds before the step executes. Defaults to 0 for the first step, 1 for subsequent steps. For conditional steps with delayType other than 'within', delay is not required
Position in the sequence (must be >= -1). If omitted or exceeds the step count, the step is appended to the end
Title or label for manual steps. Required for manual steps
HTTP method for API steps. Required for api steps
Content for email, LinkedIn, manual, phone, or WhatsApp steps. Required for steps that send messages
Email subject line. Required for email steps
Delay type for conditional steps. Must be 'within' or 'waitUntil'. For conditional steps with delayType other than 'within', the delay field is not required
Alternate message for linkedinSend steps
Target campaign ID for sendToAnotherCampaign steps. Required for sendToAnotherCampaign steps
The unique identifier of the sequence to add the step to
Condition type for conditional steps. Must be one of: emailsOpened, emailsClicked, emailsUnsubscribed, meetingBooked, linkedinInviteAccepted, hasWhatsappAccount
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
LEMLIST_POST_ADD_UNSUBSCRIBE_EMAIL_DOMAINTool to add an email or domain to the unsubscribed list. Use when you need to globally block sending to a specific recipient or domain.
Input parameters
Email address or domain to add to the unsubscribed list. Domain entries must start with '@', e.g. '@example.com'.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
LEMLIST_POST_ADD_VARIABLES_TO_LEADTool to add one or more variables to a lead. Use when you need to enrich a lead with custom data after its creation or retrieval.
Input parameters
Unique identifier of the lead to which the variables will be added.
Namespace for these variables; must match your company name in Lemlist.
Mapping of variable names to values. Keys must be unique and not override existing variables.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
LEMLIST_POST_ASSOCIATE_SCHEDULE_WITH_CAMPAIGNTool to associate a schedule with a campaign. Use after confirming both campaignId and scheduleId to bind a schedule to its campaign.
Input parameters
ID of the campaign to which the schedule will be associated
ID of the schedule to associate with the campaign
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
LEMLIST_POST_CREATE_CAMPAIGNTool to create a new campaign. Use after confirming the team ID. Returns campaign, sequence, and schedule IDs nested under a `data` key (e.g., `result\['data'\]\['campaignId'\]`).
Input parameters
The name of the campaign to create
The ID of the team under which the campaign will be created
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
LEMLIST_POST_CREATE_LABELTool to create a new label for inbox conversations. Use when you need to organize inbox messages with custom labels.
Input parameters
Name of the label to create. Must be unique within the team.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
LEMLIST_POST_CREATE_LEAD_IN_CAMPAIGNTool to create a lead and add it to a specific campaign. Use when you need to enroll a new lead into an outreach campaign. Supports optional deduplication and enrichment features.
Input parameters
Email address of the lead (required for lead creation).
Contact phone number for the lead.
Lead's professional role or job title.
Last name of the lead.
IANA format timezone for the lead (e.g., Europe/Paris, America/New_York).
If true, attempts to find and verify the lead's email address.
If true, attempts to find the lead's phone number.
First name of the lead.
Unique identifier of the campaign to add the lead to.
Personalized message or icebreaker text for the lead.
Name of the lead's organization.
If true, checks if email exists in other campaigns and skips insertion if found (prevents duplicate leads).
URL to the lead's LinkedIn profile.
If true, validates the existing email using debounce service.
User ID or email of the contact owner responsible for this lead.
Domain of the lead's company website.
If true, executes LinkedIn enrichment to enhance lead data.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
LEMLIST_POST_CREATE_SCHEDULETool to create a new schedule for the team. Use when you need to define custom active times or delays for outreach operations. Returns a `scheduleId`; store it for association with campaigns or sequences. Avoid creating unused schedules.
Input parameters
Optional end time in HH:mm format. Defaults to '18:00'.
Optional name for the schedule. Defaults to 'Default schedule'.
Optional start time in HH:mm format. Defaults to '09:00'.
Optional timezone for the schedule (IANA timezone identifier). Defaults to 'Europe/Paris'.
Optional list of active weekdays (1=Monday .. 7=Sunday). Defaults to \[1,2,3,4,5\].
Optional delay in seconds between operations. Defaults to 1200 seconds.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
LEMLIST_POST_CREATE_TASKTool to create a manual task (opportunity) associated with a contact, company, or lead. Use when you need to track follow-ups or action items for outreach prospects.
Input parameters
Task type - must be one of: email, manual, phone, or linkedin.
Task title; defaults to empty string if not provided.
Due date timestamp in ISO 8601 format (e.g., 2026-03-15T10:00:00.000Z).
Task description/message; defaults to empty string if not provided.
Priority level - empty string, 0, 1, or 2; defaults to empty string if not provided.
The ID of the contact, company, or lead associated with the task.
The user ID of the team member assigned to the task.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
LEMLIST_POST_IGNORE_TASKSTool to mark one or more tasks as ignored in Lemlist. Use when you want to dismiss tasks without completing them.
Input parameters
Array of task IDs to ignore (e.g., opp_ouYzdLYGs4RcrHTfm)
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
LEMLIST_POST_MARK_LEAD_AS_INTERESTEDTool to mark a lead as interested in all campaigns. Use when a lead responds positively and you want to advance or personalize your outreach.
Input parameters
Email address of the lead to mark as interested.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
LEMLIST_POST_MARK_LEAD_AS_INTERESTED_IN_CAMPAIGNTool to mark a lead as interested in a specific campaign. Use after confirming the lead's positive engagement in that campaign.
Input parameters
Email address of the lead to mark as interested.
Unique identifier of the campaign.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
LEMLIST_POST_MARK_LEAD_AS_NOT_INTERESTEDTool to mark a lead as not interested in all campaigns. Use when a lead explicitly declines outreach and should be paused across campaigns.
Input parameters
Email address or lead ID ('lea_...') to mark as not interested.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
LEMLIST_POST_PAUSE_CAMPAIGNTool to pause a running campaign. Use after confirming you have the correct campaign ID and that the campaign is currently running.
Input parameters
ID of the campaign to pause
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
LEMLIST_POST_PAUSE_LEADTool to pause a lead in all campaigns or a specific campaign. Use when you want to temporarily halt outreach to a lead.
Input parameters
ID of the campaign to pause the lead in. If omitted, pauses in all campaigns.
Email address of the lead or the lead's Lemlist ID (e.g., lea_xxx)
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
LEMLIST_SEARCH_COMPANIES_DATABASETool to search the companies database using filters, keywords, and pagination. Use when you need to find companies based on criteria like industry, size, or keywords. Returns a paginated list of companies matching the specified filters.
Input parameters
Page number for pagination (1-indexed). Defaults to 1.
Number of results per page. Maximum 100. Defaults to 25.
Free-text query to search across common company fields like name, domain, and keywords.
Array of filter objects to narrow search results by criteria like keywords, industry, or company size.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
LEMLIST_SEARCH_PEOPLE_DATABASETool to search the Lemlist people database using filters, keywords, and pagination. Use when you need to find prospects based on criteria like location, job title, seniority, or company. Supports free-text search and structured filtering.
Input parameters
Page number for pagination (1-indexed). Minimum value is 1.
Number of results per page. Must be between 1 and 100.
Free-text search query across common fields (name, title, company, location). Use for keyword-based filtering.
Array of filter objects to narrow search results. Each filter must include filterId, 'in' array, and 'out' array (can be empty).
Array of field names to omit from the response. Use to reduce payload size when certain fields are not needed.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
LEMLIST_UPDATE_TASKTool to update an existing task including assignment, scheduling, and status. Use when modifying task details such as title, priority, due date, or completion status.
Input parameters
The unique identifier of the task to update.
Mark task as completed (true) or incomplete (false).
Updated task title.
Updated due date in ISO 8601 format.
Updated task message/description.
Priority levels for tasks.
The ID of the team member to assign the task to (userId).
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
No publicly available marketplace agent is found using this tool yet. There are 94 agents privately built on Nagent that already use Lemlist.
Build on Nagent
Connect Lemlist to any Nagent agent in minutes — no API key management, no boilerplate. Just configure and deploy.
The five questions agent builders ask before adopting a new integration.
Open the External Integrations panel inside Nagent (app.nagent.ai/externalIntegration), find Lemlist, and click "Connect Now." You'll authenticate with an API key — Nagent handles credential storage and refresh automatically. Once connected, Lemlist is available to any agent in your workspace.
No. Nagent provides no-code integration for every tool. Once Lemlist is connected, you configure its 54 actions directly in the agent builder UI — no API calls, no boilerplate, no schema management.
Helix — Nagent's agentic agent builder — lets you drop Lemlist steps into any workflow visually. Pick an action (e.g., one of those listed above), fill in the inputs (Helix knows the required vs. optional schema for each parameter), and connect it to upstream/downstream steps. Triggers run as the entry point of an agent, so when a Lemlist event fires, the agent kicks off automatically.
Every Lemlist action and trigger ships with a fully-typed schema — input parameters with name, type, required flag, and description, plus the output payload shape. The schemas are documented in the sections above. Helix uses these schemas to validate your configuration at build time and to type-check the data flowing between steps.
Yes. While Lemlist ships with 54 pre-built marketing automation actions, you can layer custom logic around them inside Helix — pre/post-processing steps, conditional branches, retries, or stitching Lemlist together with other connected tools. For deeper customization, talk to our team about Nagent's Agentic AI Lab — forward-deployed engineers who build Lemlist-based workflows tailored to your business.