CONNECT APP
Build with lemlist
Marketing
- API key
MCP
Give your agent lemlist tools
Every lemlist action is exposed as an MCP tool on Pipedream's remote server. Point a client at it with your end user's ID and Connect resolves that user's lemlist account for each tool call — you store no tokens.
// accessToken: mint a short-lived token with the Connect SDK — see the MCP guide
const transport = new StreamableHTTPClientTransport(
new URL("https://remote.mcp.pipedream.net/v3"),
{
requestInit: {
headers: {
Authorization: `Bearer ${accessToken}`,
"x-pd-project-id": "{project_id}",
"x-pd-environment": "production",
"x-pd-external-user-id": "{external_user_id}", // any stable ID for this user in your system
"x-pd-app-slug": "lemlist",
},
},
},
)
const mcp = new Client({ name: "my-agent", version: "1.0.0" })
await mcp.connect(transport)
const { tools } = await mcp.listTools()
// e.g. run Add Email In Unsubscribes:
const result = await mcp.callTool({
name: "lemlist-add-email-in-unsubscribes",
arguments: {
email: "Email",
},
})# access_token: mint a short-lived token with the Connect SDK — see the MCP guide
headers = {
"Authorization": f"Bearer {access_token}",
"x-pd-project-id": "{project_id}",
"x-pd-environment": "production",
"x-pd-external-user-id": "{external_user_id}", # any stable ID for this user in your system
"x-pd-app-slug": "lemlist",
}
async with streamablehttp_client("https://remote.mcp.pipedream.net/v3", headers=headers) as (read, write, _):
async with ClientSession(read, write) as session:
await session.initialize()
tools = await session.list_tools()
# e.g. run Add Email In Unsubscribes:
result = await session.call_tool("lemlist-add-email-in-unsubscribes", {
"email": "Email",
})API PROXY
Call the lemlist API directly
For an endpoint with no pre-built tool, the Connect proxy forwards your request to the lemlist API with the connected user's credentials attached. You store no tokens and write no refresh logic.
const resp = await pd.proxy.get({
externalUserId: "{external_user_id}", // any stable ID for this user in your system
accountId: "apn_xxxxxxx",
url: "https://api.lemlist.com/api/team",
})
// Any allowed lemlist endpoint works here. Pipedream attaches the
// connected account's credentials to the outgoing request.# The path segment is the target URL, URL-safe base64 encoded:
# https://api.lemlist.com/api/team
curl "https://api.pipedream.com/v1/connect/{project_id}/proxy/aHR0cHM6Ly9hcGkubGVtbGlzdC5jb20vYXBpL3RlYW0?external_user_id={external_user_id}&account_id=apn_xxxxxxx" \
-H "Authorization: Bearer {access_token}" \
-H "x-pd-environment: production"SDK
Run lemlist actions from your backend
Connect a user's lemlist account once, then run Add Email In Unsubscribes on their behalf from your own code — TypeScript, Python, or plain HTTP.
import { PipedreamClient } from "@pipedream/sdk"
const pd = new PipedreamClient({
projectId: process.env.PIPEDREAM_PROJECT_ID!,
clientId: process.env.PIPEDREAM_CLIENT_ID!,
clientSecret: process.env.PIPEDREAM_CLIENT_SECRET!,
projectEnvironment: "production",
})
const result = await pd.actions.run({
id: "lemlist-add-email-in-unsubscribes",
externalUserId: "{external_user_id}", // any stable ID for this user in your system
configuredProps: {
lemlist: { authProvisionId: "apn_xxxxxxx" },
email: "Email",
},
})from pipedream import Pipedream
pd = Pipedream(
client_id="{oauth_client_id}",
client_secret="{oauth_client_secret}",
project_id="{project_id}",
project_environment="production",
)
result = pd.actions.run(
id="lemlist-add-email-in-unsubscribes",
external_user_id="{external_user_id}", # any stable ID for this user in your system
configured_props={
"lemlist": {"authProvisionId": "apn_xxxxxxx"},
"email": "Email",
},
)curl -X POST https://api.pipedream.com/v1/connect/{project_id}/actions/run \
-H "Content-Type: application/json" \
-H "X-PD-Environment: production" \
-H "Authorization: Bearer {access_token}" \
-d '{
"external_user_id": "{external_user_id}",
"id": "lemlist-add-email-in-unsubscribes",
"configured_props": {
"lemlist": { "authProvisionId": "apn_xxxxxxx" },
"email": "Email"
}
}'TOOLS
lemlist actions
On-demand operations your product or agent can configure and run on behalf of a connected user.
-
Add Email In Unsubscribes
actionThis action adds a lead in the unsubscribed list. See the docs hereWritev0.0.2 -
Add Lead To A Campaign
actionThis action adds a lead in a specific campaign. If the lead doesn't exist, it'll be created, then inserted to the campaign. The creator of the lead is the campaign's sender See the docs hereWritev0.0.3 -
Delete An Email From Unsubscribes
actionThis action deletes a lead in the unsubscribed list. See the docs hereWritev0.0.2 -
Delete Lead From Campaign
actionThis action deletes a lead from a specific campaign. All information, including statistics, will be deleted. See the docs hereWritev0.0.2 -
Get Lead
actionThis action retrieves all the information of a specific lead using its email. See the docs hereRead-onlyv0.0.2 -
List Campaign Id Options
actionRetrieves available options for the Campaign Id field.Read-onlyv0.0.1 -
Mark Lead From All Campaigns As Interested
actionThis action marks a specific lead as interested using its email in all campaigns. See the docs hereWritev0.0.2 -
Mark Lead From All Campaigns As Not Interested
actionThis action marks a specific lead as not interested using its email in all campaigns. See the docs hereWritev0.0.2 -
Mark Lead From One Campaigns As Interested
actionThis action marks a specific lead as interested using its email in a specific campaign. See the docs hereWritev0.0.2 -
Mark Lead From One Campaigns As Not Interested
actionThis action marks a specific lead as not interested using its email in a specific campaign. See the docs hereWritev0.0.2 -
Pause Lead From All Campaigns
actionThis action pauses a specific lead using its email in all campaigns. See the docs hereWritev0.0.2 -
Resume Lead From All Campaigns
actionThis action starts a specific lead using its email in all campaigns. See the docs hereWritev0.0.2 -
Unsubscribe Lead From Campaign
actionThis action will unsubscribe a lead from all campaigns if he belongs to the specified campaign. See the docs hereWritev0.0.2 -
Update Lead In Campaign
actionThis action updates a lead in a specific campaign. If the lead doesn't exist a 404 error will be returned. See the docs hereWritev0.0.2
EVENTS
lemlist triggers
Event sources your backend can deploy for users and receive through a webhook.
MULTI-APP
Use lemlist with other popular apps
Most products don't stop at one integration. Pair lemlist with the other apps your users rely on, and ship use cases that span both.
- App slug
- lemlist
- Authentication
- API key
- Categories
- Marketing
- Actions
- 14
- Triggers
- 2
- API proxy
- Available