lemlist + Grok Bot
Connect lemlist to Grok Bot
Prepare a grounded outreach campaign briefing
Read campaigns with Grok Bot and Agent200. Prepare a outreach campaign briefing using the connected user’s own lemlist account.
On this page
Overview
Identify the selected campaign and ask Grok Bot to use the Agent200 connection. Inspect tool activity so browser context or another app does not replace the requested read.
Start with one identified campaign. Preserve returned campaign, lead and activity fields; report missing data and keep the workflow read-only.
Provider reference: lemlist API.
- Connector
- lemlist
- Works with
- Grok Bot · Agent app, through MCP
- Authentication
- Managed OAuth, per end user
- You need
- An Agent200 API key
- Tools
- 5 tools
- MCP server
https://api.agent200.com/mcp/
Before you start
- An Agent200 API key. Create one on the API keys page of the dashboard.
- lemlist enabled for your project. In the dashboard's Connectors settings, with the endpoints and scopes your agent needs.
- An end user with a lemlist account. They approve access once, on lemlist's own page.
- Grok Bot, with custom MCP servers allowed. Grok Bot comes with SuperGrok, Grok Business seats and paid Cursor plans. On a team, the admin's connector policy must allow the Agent200 server.
Connect lemlist to Grok Bot
-
1
Step 1: Create your Agent200 API key
Open the API keys page in the Agent200 dashboard and choose Create an API key. You add it to Grok Bot in the next step, as "Authorization: Bearer <your key>". One key covers lemlist and every other connector enabled for your project. Keep it out of chats and source control.
-
2
Step 2: Open the custom connector form
In Grok Bot, open Connect apps from the sidebar and choose Add a custom connector at the bottom.
-
3
Step 3: Fill in the server and your key
Enter the name Agent200, pick Type Remote HTTPS, enter the server URL and add one HTTP header:
Authorizationwith the valueBearerfollowed by your key. Leave Client ID empty, then choose Add plugin.Add a custom connectorMCP: Grok Bot custom connector form Name: Agent200 Type: Remote HTTPS Server URL: https://api.agent200.com/mcp/ HTTP headers: Authorization: Bearer YOUR_AGENT200_API_KEY -
4
Step 4: Attach Agent200 in a chat
In a Bot chat, type
@and attach Agent200 to the task. Custom servers are account-wide, so every Bot on the account can use it. -
5
Step 5: Connect your lemlist account
The first time you ask Grok Bot for something in lemlist, Agent200 returns an authorization link. Open it and approve access on lemlist's own page. Agent200 stores the connection and keeps it working; your password never reaches Grok Bot or Agent200.
Test your connection
Run one request to check everything is wired up.
Ask
Read the lemlist campaign I identify and prepare a outreach campaign briefing. Name the source and use only campaign, lead and activity fields. State access gaps; do not change records.
What should come back
- The selected campaign is identified.
- Only the returned campaign, lead and activity fields are reported.
- Access gaps and missing context are explicit; no source data is changed.
Check the selected campaign ID, account scope, read permission and pagination. Campaign and team scope matter. Do not interpret a paged activity list as every send, open or reply.
Get your API key
Create a key in the Agent200 dashboard. It reaches lemlist and every other connector enabled for your project.
Instructions for AI agents
Using a coding agent? Paste this brief into it, or give it the address of this page. It lists what to do, in order, to connect lemlist to Grok Bot.
Goal: connect lemlist to Grok Bot with Agent200, through its MCP server. Guide: https://www.agent200.com/connectors/lemlist/framework/grok-bot/ 1. The user needs an Agent200 API key. If they have none, send them to https://agent200.com/platform/apikeys/ to choose "Create an API key". They paste it into Grok Bot's settings themselves: never ask for it in chat and never write it into files you share. 2. Make sure lemlist is enabled for their project in the Agent200 dashboard (Connectors), with the tools the task needs. 3. Add Agent200's MCP server to Grok Bot: URL https://api.agent200.com/mcp/, transport streamable HTTP, header "Authorization: Bearer <the user's Agent200 API key>". Follow the setup steps on the guide page for Grok Bot's exact menus or commands. 4. The first lemlist request returns an authorization link if the user has not connected lemlist yet: show it to them and continue once they have approved access on lemlist's own page. 5. Check it works with this request: "Read the lemlist campaign I identify and prepare a outreach campaign briefing. Name the source and use only campaign, lead and activity fields. State access gaps; do not change records." What should come back: - The selected campaign is identified. - Only the returned campaign, lead and activity fields are reported. - Access gaps and missing context are explicit; no source data is changed. 6. If a tool is missing or a call is refused, check the project's Connectors settings in the dashboard and the access the user granted in lemlist, then retry.
The whole guide is also available as Markdown, for agents and LLMs: /connectors/lemlist/framework/grok-bot.md
lemlist tools Grok Bot can call
-
List campaigns
Readlemlist_list_campaignsFind campaigns available to the connected team.
-
Read a campaign
Readlemlist_get_campaignRetrieve one identified campaign.
-
List campaign leads
Readlemlist_list_campaign_leadsFind leads in the selected campaign.
-
Read a lead
Readlemlist_get_leadRetrieve one identified campaign lead.
-
List activities
Readlemlist_list_activitiesReview recorded outreach activity in scope.
No tool matches that search.
How it works
-
01
You ask Grok Bot
In your own words, for something in lemlist.
-
02
Grok Bot picks a tool
It sees the lemlist tools on the Agent200 MCP server and calls the one the request needs.
-
03
Agent200 runs the call
With your own lemlist connection, within the tools and scopes your project allows.
-
04
Grok Bot answers
It gets the result back from the MCP server and uses it in its reply or its next step.
Each user's own connection. Connections belong to individual end users. A request for one user never reaches another user's lemlist account.
Permissions at every level. Your project settings decide what the agent may request, the end user decides what they authorize, and lemlist enforces what its API grants.
Troubleshooting
The source cannot be read
Check the selected campaign ID, account scope, read permission and pagination. Campaign and team scope matter. Do not interpret a paged activity list as every send, open or reply.
FAQ
How do I verify this result?
Compare the named campaign and returned campaign, lead and activity fields with the source. Treat missing information as missing, not as a fact.
