Marketing
Lemlist
Multichannel sales outreach automation platform for email, LinkedIn, and call sequences.
Connect stays on CybrLink. Signed-out visitors go to sign-in. Signed-in visitors open the connect host at connect.cybrlink.dev.
Basic authScoped proxy
Connect with basic credentials
The client enters the required username, token, or secret pair in the hosted connect flow. CybrLink keeps credentials out of the agent and enforces provider scope before proxy execution.
Where to get your Lemlist API keyStep 1
Open the portal connect flow
Step 2
Enter provider credentials
Step 3
Limit write scope before launch
Sample request
// 1. Mint a session token for the end user
const session = await link.connect.session({
integrationKey: "lemlist",
userId: "u_42",
});
// 2. After the user enters their provider credentials, proxy a request
const res = await link.proxy("lemlist", "u_42", {
method: "GET",
endpoint: "/api/v1/me",
});More in this category
Typed agent tools
Typed MCP tool schemas are not published for Lemlist yet. Connecting still lets an agent call this integration through CybrLink's scoped proxy. This page does not list a tool count until those schemas exist.
Lemlist + SI (super intelligence) agents: common questions
- How do I connect Lemlist to an SI agent?
- Create a free CybrLink account, open the dashboard, and click Connect on Lemlist. You authorize once with basic credentials; CybrLink stores the credential in its token vault and your agent reaches Lemlist through the CybrLink MCP server or the agent proxy API. The credential itself is never placed in the model's context.
- Does Lemlist work with Claude, GPT, and other MCP clients?
- Yes. CybrLink exposes a remote MCP (Model Context Protocol) server, so any MCP-capable client or agent framework — including Claude, OpenAI-based agents, and custom agents — can call Lemlist once you've connected it. Non-MCP agents can use the authenticated HTTP proxy instead.
- Is it safe to give an SI agent access to Lemlist?
- CybrLink scopes every connection to the permissions you grant, keeps tokens out of the model, logs each call to an activity audit trail, and lets you revoke the Lemlist connection at any time from the dashboard.