Skip to main content
Book a demo

Connect lemlist to Hermes

Give Hermes governed access to lemlist’s 35 tools through Runlayer, with identity, policy, scanning, and audit on every call.

Book a demo Hermes setup guide

Set up

Add lemlist to Hermes in four steps

Admins approve the server once. Everyone in Hermes then gets it through the same governed connection.

  1. 1

    Approve lemlist in Runlayer

    Add lemlist from the catalog and choose who can use it and which of its tools are allowed.

  2. 2

    Connect Hermes to Runlayer

    Users add the Runlayer Plugin to Hermes by following Runlayer’s setup guide. Hermes reaches lemlist’s 35 tools through the Runlayer Plugin’s search and execute tools instead of listing each one.

    Hermes setup guide
  3. 3

    Sign in to lemlist

    Each user signs in to lemlist with OAuth. Runlayer keeps the tokens out of the client’s configuration.

  4. 4

    Use lemlist from Hermes

    lemlist’s approved tools appear in Hermes. Every call is checked against policy and recorded.

Tools

35 lemlist tools in Hermes

Runlayer policy decides which of these Hermes 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.

See all 35 lemlist tools

Control

What Runlayer can see and stop in Hermes

Some controls apply to every client at the gateway. Others depend on what Hermes exposes to Runlayer.

  • Gateway policy (available)

    Every lemlist call from Hermes passes through Runlayer, where your policies can allow, alert, mask, or block it.

  • Audit trail (available)

    Each call is recorded with the user, Hermes as the client, the tool, and the policy and scanner decisions.

  • Client hooks (available)

    Capture supported prompts, reasoning, local and MCP tool calls, responses, and scanner decisions in real time.

  • Stop a call before it runs (available)

    Runlayer can deny a tool call before Hermes runs it.

  • Block output after it runs (available)

    Runlayer can block a tool’s output in Hermes and show a message in its place.

  • Redact output in place (not available)

    Hermes cannot take masked output, so Runlayer can block a tool’s output but not mask it. The gateway still applies policy to the call.

In Hermes

  • Hermes can replace blocked tool output with a message, but its after-call event is for monitoring only.

Frequently asked questions

Connect more

Find another combination