Connect lemlist to Crush
Give Crush governed access to lemlist’s 35 tools through Runlayer, with identity, policy, scanning, and audit on every call.
Set up
Add lemlist to Crush in four steps
Admins approve the server once. Everyone in Crush then gets it through the same governed connection.
- 1
Approve lemlist in Runlayer
Add lemlist from the catalog and choose who can use it and which of its tools are allowed.
- 2
Connect Crush to Runlayer
Users add the Runlayer Plugin to Crush by following Runlayer’s setup guide. Crush reaches lemlist’s 35 tools through the Runlayer Plugin’s search and execute tools instead of listing each one.
Crush setup guide - 3
Sign in to lemlist
Each user signs in to lemlist with OAuth. Runlayer keeps the tokens out of the client’s configuration.
- 4
Use lemlist from Crush
lemlist’s approved tools appear in Crush. Every call is checked against policy and recorded.
Tools
35 lemlist tools in Crush
Runlayer policy decides which of these Crush users can call.
Ask question
Ask user questions with multiple-choice options.
Get team info
Get basic team info (ID, name, plan, credits remaining).
Get team members
Get all team members with ID, email, name, and role.
Get team overview
Get a quick summary of your account: total campaigns count and breakdown by status (draft, running, paused, ended, archived, errors).
Get campaigns
List campaigns with details (id, name, status, leadsCount).
Get campaigns reports
Get lifetime stats for MULTIPLE campaigns in one call.
Get campaign details
Get configuration and settings for ONE campaign (timezone, emoji, sequences).
Get campaign sequences
Get the email sequences and their content (subject, body) for a specific campaign.
Control
What Runlayer can see and stop in Crush
Some controls apply to every client at the gateway. Others depend on what Crush exposes to Runlayer.
Gateway policy (available)
Every lemlist call from Crush passes through Runlayer, where your policies can allow, alert, mask, or block it.
Audit trail (available)
Each call is recorded with the user, Crush as the client, the tool, and the policy and scanner decisions.
Native enforcement adapter (not available)
Runlayer has no device-side adapter for Crush yet, so control happens at the gateway.
Frequently asked questions
Connect more
