Skip to main content
Book a demo

Connect lemlist to Gumloop

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

Book a demo Gumloop setup guide

Set up

Add lemlist to Gumloop in four steps

Admins approve the server once. Everyone in Gumloop 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 Gumloop to Runlayer

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

    Gumloop 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 Gumloop

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

Tools

35 lemlist tools in Gumloop

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

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

  • Gateway policy (available)

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

  • Audit trail (available)

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

  • Native enforcement adapter (not available)

    Runlayer has no device-side adapter for Gumloop yet, so control happens at the gateway.

Frequently asked questions

Connect more

Find another combination