email-listener

Converts labeled Gmail threads into Pi-CEO sessions via webhook and Pub/Sub.

Updated Aug 23, 2026

Search Tags:#automation #gmail #webhook #email triage #pii redaction #agent sessions #intent parsing

Ready to run

npx skills add https://github.com/CleanExpo/Pi-Dev-Ops --skill email-listener

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: email-listener
Source: https://github.com/CleanExpo/Pi-Dev-Ops/tree/main/skills/email-listener
Command: npx skills add https://github.com/CleanExpo/Pi-Dev-Ops --skill email-listener

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill removes the need to manually forward or paste emails by turning inbound Gmail messages into Pi-CEO execution sessions automatically, based on an explicit user label.

Core Features & Use Cases

Push-triggered Gmail intake: Uses Gmail push notifications via Pub/Sub so threads become first-class triggers within seconds, without polling.
Intent synthesis from email threads: Fetches thread details, summarizes the latest message body, and converts the email into a structured payload for downstream intent parsing.
Safety and privacy guardrails: Applies PII redaction before intent parsing, enforces allowlist-based sender restrictions, and prevents reply-all recipient leakage.
Use Case: Label a support or request email with pi-ceo/inbox and have Pi-CEO draft a reply, dispatch research, or route ticket-creation intent for review and execution.

Quick Start

Label a Gmail thread with pi-ceo/inbox and expect Pi-CEO to create a new session with triggered_by=email and a parsed intent routed for review.

Frequently Asked Questions about email-listener

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

FAQPage Schema

How do I automate Gmail thread processing without manual polling?▼

Automate Gmail thread processing using Pub/Sub push notifications routed to a webhook, which fetches labeled threads and synthesizes intent payloads instantly without polling.

How does email triage handle PII redaction before intent parsing?▼

Email triage handles PII redaction by scrubbing inbound message data before synthesizing the structured intent payload, ensuring sensitive information is removed prior to downstream parsing.

Can I trigger agent sessions directly from labeled inbound emails?▼

Trigger agent sessions directly by applying a specific inbox label to Gmail threads, which initiates a session that parses the email intent for review or execution.

How to enforce sender allowlists and prevent reply-all leakage during email automation?▼

Enforce sender allowlists by restricting inbound processing to authorized contacts and applying recipient leakage prevention guardrails before generating the structured intent payload.

What is the best way to convert Gmail messages into structured intent payloads?▼

Convert Gmail messages into structured intent payloads by fetching thread details, summarizing the latest message body, and formatting the data for downstream intent parsing.

Does Gmail push notification intake require a processed-label update after completion?▼

Gmail push notification intake requires a processed-label update applied to the thread only after the session and intent parsing complete successfully.