Pilot Email Bridge for Openclaw

A bridge that connects Pilot Protocol messaging with standard email services to enable agent-based email communication.

teoslayer
v1.0.0
Apr 9, 2026
0
653
0

Install & Download

1. ClawHub CLI

The fastest way to install a skill directly from the registry.

npx clawhub@latest install pilot-email-bridge

2. Manual Installation

Copy the skill folder to one of these locations

Global
~/.openclaw/skills/
Workspace
<project>/skills/

Priority: Workspace > Local > Bundled

3. Prompt Installation

Copy this prompt to OpenClaw to install it automatically.

Help me install pilot-email-bridge using Clawhub. If Clawhub is not installed, install it first (npm i -g clawhub).

Prefer to download?

Get the raw skill files in a ZIP archive.

What is Pilot Email Bridge?

The pilot-email-bridge is a robust integration layer designed to facilitate two-way communication between the Pilot Protocol and traditional email infrastructures. By utilizing this component within the Openclaw Skills library, developers can empower their AI agents to interact with the world via SMTP and IMAP. This skill effectively wraps email functionality into the native Pilot messaging lifecycle, allowing for automated notifications and event-driven responses based on incoming mail.

Built for high-performance agentic workflows, this skill handles the translation of JSON-based Pilot messages into standard email formats and vice versa. It is an essential utility for anyone looking to extend their agent's reach beyond internal protocols and into the ubiquitous world of email communication, ensuring that Openclaw Skills remain highly interoperable with existing business systems.

Pilot Email Bridge Use Cases

  • Sending automated system alerts or notifications from Pilot agents to human supervisors.
  • Ingesting incoming customer emails as Pilot events for automated agent processing.
  • Integrating autonomous agent workflows with legacy email-based ticketing systems.
  • Facilitating file transfers via email attachments using the Pilot command-line interface.

How Pilot Email Bridge Works

  1. The Pilot daemon is initialized on a specific hostname to serve as the relay point.
  2. A webhook is configured to route outbound messages to an SMTP relay service.
  3. The bridge subscribes to the email-outbound topic to listen for outgoing message requests.
  4. When a message is published to the topic, the bridge triggers the webhook to send the physical email.
  5. For inbound communication, the daemon polls or receives updates from an IMAP source, populating the local Pilot inbox.

Pilot Email Bridge Setup

To utilize this feature in your Openclaw Skills environment, ensure you have the pilot-protocol skill installed and the pilotctl binary available on your path.

# Start the Pilot daemon
pilotctl --json daemon start --hostname email-relay

# Configure the outbound email webhook
pilotctl --json set-webhook https://your-smtp-gateway.com/send

# Subscribe to the outbound channel
pilotctl --json subscribe localhost email-outbound

Pilot Email Bridge Data Schema & Taxonomy

The pilot-email-bridge uses a structured JSON format for message exchange. This schema ensures compatibility across various Openclaw Skills and email providers.

Attribute Description Required
to The recipient's email address Yes
subject The subject line of the email Yes
body The plaintext or HTML content of the message Yes
attachments Path to files for the send-file command No

Pilot Email Bridge Advanced Features

  • Support for multi-file attachments via the send-file command-line utility.
  • Granular inbox management with the ability to clear or selectively receive messages by count.
  • Asynchronous webhook integration for high-throughput email relaying.
  • Seamless compatibility with headless environments using the pilotctl daemon mode.

SKILL.md


Loading

Related Openclaw Skills

METADATA

Github Stars: 0
forks: 0

Featured*