email-webhook

What This Skill Does

The email-webhook skill acts as a secure, real-time bridge between external email services and your OpenClaw agent. By providing a dedicated HTTP endpoint, it transforms asynchronous email messages into actionable system events. When an email hits the configured endpoint, the skill triggers an 'openclaw system event', forcing the agent to wake up immediately. This bypasses typical heartbeat wait times, allowing the agent to parse, filter, and notify you about important communications in real-time. It stores raw email data into a local .jsonl file, ensuring you have a durable log for processing.

Installation

To integrate this skill into your environment, first ensure you have the necessary dependencies by running 'npm install [email protected]'. Once installed, you must configure your environment variables; specifically, 'WEBHOOK_SECRET' is mandatory for security. Start the server using your secret token and ensure your 'OPENCLAW_AGENT_ID' is set so that emails are routed to the correct agent instance. Finally, append the processing logic to your 'HEARTBEAT.md' file to handle the polling and user notification lifecycle.

Use Cases

This skill is perfect for users who rely on email for high-priority notifications but want the intelligent processing power of an AI agent. Common use cases include: filtering junk from important business inquiries, summarizing long email threads into concise bullet points, responding to urgent client emails via your preferred messaging platform like Discord or WhatsApp, and integrating email-based ticket systems directly into your personal AI workflow.

Example Prompts

1. "Check for new emails and summarize any from my manager in the last hour."
2. "If I have any unread emails from the bank, alert me on Discord immediately."
3. "Show me the last three emails I received and draft a professional reply to the most recent one."

Tips & Limitations

Security is paramount: always use a complex string for your 'WEBHOOK_SECRET' to prevent unauthorized triggers. Be mindful of disk usage; since the skill logs every incoming email to an 'inbox.jsonl' file, you should implement a routine task to archive or purge this file periodically. Because this skill relies on the file system, it works best in environments where the agent has persistent local storage. Finally, remember that your agent's 'HEARTBEAT.md' logic determines how the notification is handled—ensure your notification logic is robust enough to handle empty payloads or edge-case email formatting.