Skip to content

Weekly marketing report digest

Reads the week's marketing reports, decks and meeting notes, and tells you what actually changed. It keeps a log so slow trends stand out.

MarketingWorks with Claude Desktop with MCP · Claude Code+1Community example

What it does

  • Reads a fixed list of report senders and meetings
  • Opens linked decks and docs, not just the summary
  • Checks last week's log and open questions
  • Writes a digest of signal, noise and questions to ask
  • Updates the log for next week

Your approval boundaries

Creates drafts

These actions always wait for your yes:

  • Sharing the digest beyond you

You decide what happens next.

More about this workflow

This setup is for marketers and solo creators who need steady output without losing their voice. It takes a repeat chore off your plate and hands back something you can check quickly.

First, it reads a fixed list of report senders and meetings. Next, it opens linked decks and docs, not just the summary. Then it checks last week's log and open questions. After that, it writes a digest of signal, noise and questions to ask. Finally, it updates the log for next week. It works with your email, calendar and docs, each on its own login with limited access.

You get the prep work done and waiting for you. The agent stops and asks for your yes before sharing the digest beyond you, and says plainly if a step cannot be undone.

“one weekly digest that reads everything, remembers what it read last time”
PaulaXimenaMejia PaulaXimenaMejia on GitHub · Sep 8, 2026
Before you startEmail · Calendar accessScoped permissionsClaude Desktop with MCP or Claude Code
Explore required tools and model recommendations

Tools and access

  • Gmail

    Handles the email part of this job. Grant read-only plus compose (drafts) scopes.

    API required: Yes. Needs a Google Cloud project with an OAuth app and the Gmail API turned on. The agent signs in through OAuth with only the scopes you pick.

  • Google Calendar

    Handles the calendar part of this job. Grant read-only calendar scope.

    API required: Yes. Needs a Google Cloud OAuth app with the Calendar API turned on.

  • Google Docs

    Handles the docs part of this job. Grant one folder, create and edit only.

    API required: Yes. Needs a Google Cloud OAuth app with the Docs API turned on.

Official links only. Not sponsored, no affiliate links.

Model recommendations

Best pick

GPT-6.1 Sol

Strong general writer at a mid price.

$2 per million input tokens, $10 per million output tokens, for prompts up to 272K tokens. Longer prompts cost $4 in and $15 out.

OpenAI docs as of October 11, 2026

Cheaper backup

GPT-6 Luna

Very low cost for first drafts and digests.

$0.10 per million input tokens, $0.50 per million output tokens, for prompts up to 272K tokens.

OpenAI docs as of October 11, 2026

Our own picks. Not sponsored, no affiliate links.

Build your prompt

Add your details, then copy the prompt into your tool.

1Your details

Fill these in and the prompt updates as you type.

senders and meeting names

e.g. Friday morning

2Your prompt

4 of 4 still empty
Fill these in before you run it: [REPORT SOURCES: senders and meeting names] [CONTINUITY LOG DOC] [METRICS YOU CARE ABOUT] [DAY TO RUN: e.g. Friday morning] You are the Weekly marketing report digest agent. Reads the week's marketing reports, decks and meeting notes, and tells you what actually changed. It keeps a log so slow trends stand out. Use only the details filled in above. If any [BRACKETED] item is still blank or unclear, stop and ask for it first. Do not guess. What you do on your own: - Reads a fixed list of report senders and meetings - Opens linked decks and docs, not just the summary - Checks last week's log and open questions - Writes a digest of signal, noise and questions to ask - Updates the log for next week What you must never do without a yes from a person: - Sharing the digest beyond you Rules: - Before any step on the list above, stop and ask. Say in plain words what you want to do, who it affects, and whether it can be undone. - If something cannot be undone, say so first, in one short line. - Write drafts, not final actions. A person sends, pays, posts, or deletes. - Keep a short log of every action you took and every source you read. - If you are unsure, ask instead of guessing.
View run instructionsPaste into: Claude Desktop with MCP, Claude Code, Zapier Agents

Your answers stay in this browser only.

Run your workflow

Connect your tools with only the access this setup needs, then follow these steps.

Steps

Do these in order. Test on old data before it touches live work.

  1. 1Connect Gmail with its own login, not yours. Grant read-only plus compose (drafts) scopes.
  2. 2Connect Google Calendar with its own login, not yours. Grant read-only calendar scope.
  3. 3Connect Google Docs with its own login, not yours. Grant one folder, create and edit only.
  4. 4Paste the prompt where your harness takes instructions. See the note under the Copy button.
  5. 5Do a dry run on old or test data first. Check every draft and every stop point by hand before you let it near live work.
  6. 6Read its log after the first real run. Only widen access once a week of runs looks clean.

Safeguards and trust score

The score describes this example setup’s access, approval boundaries, ability to undo changes, and scope.

Access24 / 30

Writes drafts and notes inside your tools, nothing leaves on its own.

Human approval27 / 30

Waits for a yes on: sharing the digest beyond you.

Undo and logs17 / 20

Leaves drafts you can throw away, with a record of what it made.

Scope16 / 20

Runs on its own login across 3 tools. Fewer connections means a smaller blast radius.

How to raise it

  • Human approval: Add a second named stop next to "sharing the digest beyond you", so every step that leaves your hands waits for a yes, and have the confirm say plainly what cannot be undone +3
  • Scope: Cut it down from 3 connected tools to the 2 it needs most, each with its own limited login instead of your full account +2

Do all of these to reach 89, up from 84.

Want help getting there? Get an AI Trust Audit from Pixeldesigns

Reviewed by Trustcase (example setup). How scoring works

Embed badge

Show this trust score on your site or README. It links back here.

Trustcase trust score badge
Markdown
[![Trustcase trust score for Weekly marketing report digest](https://trustcase.dev/badge/weekly-marketing-report-digest.svg)](https://trustcase.dev/use-cases/weekly-marketing-report-digest)
HTML
<a href="https://trustcase.dev/use-cases/weekly-marketing-report-digest"><img src="https://trustcase.dev/badge/weekly-marketing-report-digest.svg" alt="Trustcase trust score for Weekly marketing report digest" height="20"></a>
  • New page internal link suggester

    Once a week it finds the pages you published and suggests where your older pages should link to them. You approve the links before they go live.

  • One idea to a full post package

    Turns rough notes or a draft into a folder of ready to review posts, a blog draft and images for each platform. Nothing is published for you.

  • Review request texts after a sale

    When a sale or service is marked done, it waits two days and texts the customer a link to leave a review, then one reminder. It checks opt outs first and tells the owner if a text fails.

  • Backlink prospecting with you sending

    Finds the sites AI answers actually cite in your category, prepares what each publisher needs and drafts every outreach email. You send each email and approve each placement yourself.