email-channel

Monitor an IMAP inbox and send SMTP replies with attachments.

3|1|Updated Feb 5, 2026
One-click install
npx skills add https://github.com/timothy-node/openclaw-email-channel --skill email-channel
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: email-channel
Source: https://github.com/timothy-node/openclaw-email-channel/tree/main
Command: npx skills add https://github.com/timothy-node/openclaw-email-channel --skill email-channel

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the problem of manually sending replies and monitoring inboxes by enabling automated two-way email conversations through IMAP/SMTP.

Core Features & Use Cases

  • Instant inbound support: Regularly polls an IMAP inbox and turns allowed incoming emails into user messages for OpenClaw.
  • Thread-aware replies: Maintains conversational context using message/thread identifiers so responses stay coherent across email chains.
  • Attachment handling (inbound + outbound): Saves incoming attachments to a configured directory and can attach files to outgoing replies.

Quick Start

Use the email-channel skill to reply to an incoming email by calling the message tool with channel=email, including the recipient target, replyTo message ID, and your message text.

Frequently Asked Questions about email-channel

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate email replies using IMAP and SMTP?

Automated email replies are enabled by polling an IMAP inbox for allowed incoming messages and sending responses via SMTP. This Skill handles two-way email communication by converting inbound emails into messages and replying through SMTP with optional attachments.

Can I keep email threading context when sending automated replies?

Email threading context is maintained using Message-ID and References headers. This ensures automated replies stay coherent within existing email chains, preserving conversational context across back-and-forth messages.

How do I restrict automated email replies to specific senders only?

Sender allowlisting restricts automated replies to approved email addresses. The Skill enforces this allowlist during IMAP inbox polling, ensuring only messages from permitted senders trigger automated SMTP responses.

Does this Skill support handling email attachments in automated workflows?

Email attachment handling works in both directions: incoming attachments are saved to a configured directory, and outgoing SMTP replies can include attached files. This enables attachment-based notifications and automated reply workflows.

What's the best way to configure IMAP polling for automated email responses?

IMAP polling configuration is defined through YAML-based skill metadata. The runtime channel behavior manages polling intervals, allowlist enforcement, and SMTP delivery settings to process inbound emails and generate automated replies.