MCP Media Inbox Triage
Use this skill when a marketing, PR, community, or partnerships team needs a lightweight triage layer for a shared Gmail inbox.
What This Skill Does
- Searches a configured Gmail inbox or label in a bounded window.
- Reads only the message context needed for classification.
- Classifies each message as media request, partnership inquiry, customer/community lead, urgent executive risk, vendor pitch, spam/no action, or unclear.
- Scores urgency and recommends the right owner.
- Routes relevant requests to Slack, Google Sheets, or a triage doc.
- Drafts suggested replies only for human review.
When You Need This Pattern
- A shared inbox mixes press requests, creator pitches, partnership notes, customer signals, newsletters, and vendor spam.
- One person spends time each week skimming every email just to find the real asks.
- The team needs human review before any reply is sent.
- The team already works in Gmail, Slack, and Google Sheets.
- You want a practical Zapier MCP workflow that saves attention, not just time.
Architecture
Shared Gmail inbox
-> Zapier MCP Gmail search and read
-> AI classification
-> Slack summary, Google Sheets triage log, or Gmail draft
Required Connections Through Zapier MCP
- Gmail: search and read messages from the shared inbox.
- Slack: post triage summaries or urgent alerts.
- Google Sheets: append a persistent triage log.
- LLM: classify and summarize.
Optional:
- Google Docs: create a weekly media-request digest.
- Google Calendar: check deadline windows or schedule follow-ups.
- CRM or advocacy database: match senders to known customers, partners, or advocates.
Core Workflow
1. Define The Inbox Window
Start with a bounded search:
to:{SHARED_INBOX} newer_than:7d -label:triaged
Adjust the inbox address, label, and time window for your team.
2. Pull Minimal Email Context
For each candidate message, read only:
| Field |
Why |
| Sender name and email |
Identify source and possible owner |
| Subject |
Fast classification signal |
| Date received |
Urgency and SLA |
| Plain-text body |
Extract the ask |
| Thread count |
Spot follow-ups and repeated requests |
| Gmail thread link |
Source of truth |
Do not dump full email bodies into Slack.
3. Classify The Request
| Category |
Signal |
Default action |
| Media request |
Journalist, publication, interview, quote, deadline |
Route to PR or comms |
| Partnership inquiry |
Co-marketing, integration, affiliate, event, sponsorship |
Route to partnerships or marketing |
| Customer/community lead |
Customer story, testimonial, community invite, user feedback |
Route to advocacy or community |
| Urgent executive risk |
Legal threat, brand risk, sensitive complaint, public escalation |
Alert owner immediately |
| Vendor pitch |
Agency, list purchase, ad buy, unrelated service offer |
Log or ignore |
| Spam/no action |
Generic blast, irrelevant outreach, phishing indicators |
Archive or leave unassigned |
| Unclear |
Not enough context to decide |
Send to human review |
4. Score Urgency
| Urgency |
Signals |
Response target |
| High |
Deadline within 48 hours, named journalist, public brand risk, customer escalation |
Same day |
| Medium |
Specific ask, relevant sender, no immediate deadline |
Two business days |
| Low |
Useful but exploratory, vague timing, non-critical |
Weekly batch |
| Ignore |
Spam, irrelevant vendor pitch, duplicate |
No response |
5. Output The Summary
Media inbox triage: 14 messages scanned, 4 need action
High urgency
- Jane Lee, TechWeekly: asks for comment on AI workflow story by Friday.
Owner: PR
Suggested action: reply with availability and approved spokesperson.
Source: Gmail thread link
Ignored
- 8 vendor pitches
- 2 unrelated newsletters
Google Sheets Log
| Column |
Purpose |
| received_at |
Message timestamp |
| sender_name |
Human-readable sender |
| sender_email_domain |
Domain only if privacy matters |
| subject |
Email subject |
| category |
Classification |
| urgency |
High / Medium / Low / Ignore |
| summary |
One-sentence ask |
| suggested_owner |
Team or person |
| suggested_next_action |
Concrete next step |
| gmail_thread_link |
Source link |
| status |
New / Routed / Done / Ignored |
Classification Prompt
You are triaging a shared media inbox.
Classify this email for a human team. Do not draft a reply unless the email needs action.
Return JSON:
{
"category": "media_request|partnership_inquiry|customer_community_lead|urgent_executive_risk|vendor_pitch|spam_no_action|unclear",
"urgency": "high|medium|low|ignore",
"sender_name": "string or unknown",
"sender_org": "string or unknown",
"deadline": "string or null",
"summary": "One sentence describing the actual ask",
"why_it_matters": "One sentence explaining relevance",
"suggested_owner": "PR|Community|Marketing|Partnerships|Support|Leadership|Human review|Ignore",
"suggested_next_action": "Concrete next action",
"draft_reply_needed": true,
"confidence": "high|medium|low"
}
Rules:
- Do not expose private email content in team channels.
- If the message is vague, classify as unclear.
- If the message is a generic vendor pitch, classify as vendor_pitch or spam_no_action.
- If the message mentions legal risk, public complaint, a journalist deadline, or a customer escalation, mark high urgency.
Zapier MCP And SDK Role
- Use Zapier MCP to search Gmail, read message context, post Slack summaries, append Google Sheets rows, and create Gmail drafts when approved.
- Use Zapier SDK for recurring runs, owner routing, retry handling, status logging, follow-up reminders, and weekly reporting when the workflow becomes productionized.
Guardrails
- Never auto-send replies.
- Do not expose full private email threads in Slack.
- Keep Gmail thread links as the source of truth.
- Route uncertain messages to a human.
- Treat generic vendor pitches as vendor_pitch or spam_no_action unless there is a specific relevant ask.
- Keep ignored messages auditable during tuning.
Inspired By
Generalized from Matt Canning and NoPlex. The reference workflow uses Zapier MCP and Gmail to reduce media inbox review from about 4 hours per week to about 15 minutes.
1---2name: mcp-media-inbox-triage3description: Find media, partnership, and high-intent requests buried in a shared Gmail inbox, summarize the useful ones, and route them to the right owner through Zapier MCP.4---56# MCP Media Inbox Triage78Use this skill when a marketing, PR, community, or partnerships team needs a lightweight triage layer for a shared Gmail inbox.910## What This Skill Does11121. Searches a configured Gmail inbox or label in a bounded window.132. Reads only the message context needed for classification.143. Classifies each message as media request, partnership inquiry, customer/community lead, urgent executive risk, vendor pitch, spam/no action, or unclear.154. Scores urgency and recommends the right owner.165. Routes relevant requests to Slack, Google Sheets, or a triage doc.176. Drafts suggested replies only for human review.1819## When You Need This Pattern2021- A shared inbox mixes press requests, creator pitches, partnership notes, customer signals, newsletters, and vendor spam.22- One person spends time each week skimming every email just to find the real asks.23- The team needs human review before any reply is sent.24- The team already works in Gmail, Slack, and Google Sheets.25- You want a practical Zapier MCP workflow that saves attention, not just time.2627## Architecture2829```text30Shared Gmail inbox31 -> Zapier MCP Gmail search and read32 -> AI classification33 -> Slack summary, Google Sheets triage log, or Gmail draft34```3536## Required Connections Through Zapier MCP3738- Gmail: search and read messages from the shared inbox.39- Slack: post triage summaries or urgent alerts.40- Google Sheets: append a persistent triage log.41- LLM: classify and summarize.4243Optional:4445- Google Docs: create a weekly media-request digest.46- Google Calendar: check deadline windows or schedule follow-ups.47- CRM or advocacy database: match senders to known customers, partners, or advocates.4849## Core Workflow5051### 1. Define The Inbox Window5253Start with a bounded search:5455```text56to:{SHARED_INBOX} newer_than:7d -label:triaged57```5859Adjust the inbox address, label, and time window for your team.6061### 2. Pull Minimal Email Context6263For each candidate message, read only:6465| Field | Why |66| --- | --- |67| Sender name and email | Identify source and possible owner |68| Subject | Fast classification signal |69| Date received | Urgency and SLA |70| Plain-text body | Extract the ask |71| Thread count | Spot follow-ups and repeated requests |72| Gmail thread link | Source of truth |7374Do not dump full email bodies into Slack.7576### 3. Classify The Request7778| Category | Signal | Default action |79| --- | --- | --- |80| Media request | Journalist, publication, interview, quote, deadline | Route to PR or comms |81| Partnership inquiry | Co-marketing, integration, affiliate, event, sponsorship | Route to partnerships or marketing |82| Customer/community lead | Customer story, testimonial, community invite, user feedback | Route to advocacy or community |83| Urgent executive risk | Legal threat, brand risk, sensitive complaint, public escalation | Alert owner immediately |84| Vendor pitch | Agency, list purchase, ad buy, unrelated service offer | Log or ignore |85| Spam/no action | Generic blast, irrelevant outreach, phishing indicators | Archive or leave unassigned |86| Unclear | Not enough context to decide | Send to human review |8788### 4. Score Urgency8990| Urgency | Signals | Response target |91| --- | --- | --- |92| High | Deadline within 48 hours, named journalist, public brand risk, customer escalation | Same day |93| Medium | Specific ask, relevant sender, no immediate deadline | Two business days |94| Low | Useful but exploratory, vague timing, non-critical | Weekly batch |95| Ignore | Spam, irrelevant vendor pitch, duplicate | No response |9697### 5. Output The Summary9899```text100Media inbox triage: 14 messages scanned, 4 need action101102High urgency103- Jane Lee, TechWeekly: asks for comment on AI workflow story by Friday.104 Owner: PR105 Suggested action: reply with availability and approved spokesperson.106 Source: Gmail thread link107108Ignored109- 8 vendor pitches110- 2 unrelated newsletters111```112113## Google Sheets Log114115| Column | Purpose |116| --- | --- |117| received_at | Message timestamp |118| sender_name | Human-readable sender |119| sender_email_domain | Domain only if privacy matters |120| subject | Email subject |121| category | Classification |122| urgency | High / Medium / Low / Ignore |123| summary | One-sentence ask |124| suggested_owner | Team or person |125| suggested_next_action | Concrete next step |126| gmail_thread_link | Source link |127| status | New / Routed / Done / Ignored |128129## Classification Prompt130131```text132You are triaging a shared media inbox.133134Classify this email for a human team. Do not draft a reply unless the email needs action.135136Return JSON:137{138 "category": "media_request|partnership_inquiry|customer_community_lead|urgent_executive_risk|vendor_pitch|spam_no_action|unclear",139 "urgency": "high|medium|low|ignore",140 "sender_name": "string or unknown",141 "sender_org": "string or unknown",142 "deadline": "string or null",143 "summary": "One sentence describing the actual ask",144 "why_it_matters": "One sentence explaining relevance",145 "suggested_owner": "PR|Community|Marketing|Partnerships|Support|Leadership|Human review|Ignore",146 "suggested_next_action": "Concrete next action",147 "draft_reply_needed": true,148 "confidence": "high|medium|low"149}150151Rules:152- Do not expose private email content in team channels.153- If the message is vague, classify as unclear.154- If the message is a generic vendor pitch, classify as vendor_pitch or spam_no_action.155- If the message mentions legal risk, public complaint, a journalist deadline, or a customer escalation, mark high urgency.156```157158## Zapier MCP And SDK Role159160- Use Zapier MCP to search Gmail, read message context, post Slack summaries, append Google Sheets rows, and create Gmail drafts when approved.161- Use Zapier SDK for recurring runs, owner routing, retry handling, status logging, follow-up reminders, and weekly reporting when the workflow becomes productionized.162163## Guardrails164165- Never auto-send replies.166- Do not expose full private email threads in Slack.167- Keep Gmail thread links as the source of truth.168- Route uncertain messages to a human.169- Treat generic vendor pitches as vendor_pitch or spam_no_action unless there is a specific relevant ask.170- Keep ignored messages auditable during tuning.171172## Inspired By173174Generalized from Matt Canning and NoPlex. The reference workflow uses Zapier MCP and Gmail to reduce media inbox review from about 4 hours per week to about 15 minutes.