Skip to content
Agentmart
Submit a tool

mcp-media-inbox-triage

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…

Skill by zapierOfficial

IndexedMIT★ 351
Write a review

Chalk Labs

Need help deploying mcp-media-inbox-triage?

Chalk Labs sets up agents like this inside real teams: connected to your tools, tested on your data, with a human in the loop where it matters.

Book a call

Install

Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.

npx agentmarket install skill/zapier-mcp-media-inbox-triage

Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.

Get the weekly diff

The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.

We use your email only for this newsletter. Privacy

About

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.

Use cases: marketing, agent-building

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this skill can do and what it asks for, from its SKILL.md. Checked Oct 25, 2026.

Tools
No tools found
Secrets
None asked for
Install scripts
None found

Network hosts it talks to 1

  • codeload.github.com · found in install command

Files it touches

  • ~/.claude/skills/mcp-media-inbox-triage

What's inside

Skill name
mcp-media-inbox-triage
Description
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.
License
MIT
Instructions
171 lines in SKILL.md · view on GitHub

Files (6)

  • ONBOARDING-PROMPT.md
  • README.md
  • SCHEMA-MAP.md
  • SETUP.md
  • SKILL.md
  • metadata.yaml

SKILL.md (first lines)

# 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

1. Searches a configured Gmail inbox or label in a bounded window.
2. Reads only the message context needed for classification.
3. Classifies each message as media request, partnership inquiry, customer/community lead, urgent executive risk, vendor pitch, spam/no action, or unclear.
4. Scores urgency and recommends the right owner.
5. Routes relevant requests to Slack, Google Sheets, or a triage doc.
6. 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

```text
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:

```text
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

```text
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 |

From zapier/gtm-cheat-codes, MIT.

Signals

Stars
351
Forks
21
Open issues
0
Last commit (this folder)
Jun 1, 2026 (5 months ago)

From GitHub (fetched Oct 24, 2026).

Details

License
MIT
First seen
Oct 24, 2026
Last checked
Oct 24, 2026

Done for you

Rather not set it up yourself?

Chalk Labs scopes, builds and runs agents for your team: the task audit, the eval harness, the integrations and the weekly ops report. Fixed scope, priced before we start.

See how we build AI agents →Read the case studies

Chalk Labs is a two-founder AI and growth studio. We build AI agents, CRMs and MVPs for Web3 and AI companies, and have shipped 50+ product and token launches.

launches shipped
50+
launches shipped
media placements
500+
media placements
founders on every account
2
founders on every account

Press we've placed: Forbes · CoinDesk · Decrypt · Cointelegraph · The Block

Rahil Jain, Co-founder, Chalk Labs. Ex-Goldman Sachs engineer. You talk to the person who builds it.

Get mcp-media-inbox-triage running in your business

Tell us what you want to automate. A founder replies within one working day with a plan, not a pitch deck.

Goes to the Chalk Labs founders, not the newsletter. Privacy

Need help deploying mcp-media-inbox-triage?

CallGet help
Cite this page

mcp-media-inbox-triage skill. Agent Mart. https://agentmart.dev/skills/zapier-mcp-media-inbox-triage (last updated 2026-10-24)