Summarize Stripe revenue changes for campaign reports | Copy-Paste AI Recipe

Name: Summarize Stripe revenue changes for campaign reports
Prep time: 7 min
Ingredients: Notion AI system; Slack AI system; Brave Search AI system

NextFlows Contributors

doi:nextflows.ai/recipes/summarize-stripe-revenue-changes-for-campaign-reports-marketing-27

⚡ TL;DR

✓ Spot campaign risks earlier with concise summaries of feedback, performance signals, and next best actions
✓ 7 minutes to first success
✓ Read-only
✓ Uses Notion MCP, Slack MCP, Brave Search MCP

Before you start

0/5

Claude Desktop installedNotion MCP access configuredSlack MCP access configuredBrave Search MCP access configuredPermission for Notion read access, Slack read access, Brave Search read access

Setup (7 min)

0/5

1Connect Notion MCP in your MCP client and confirm the server shows as available.

2Connect Slack MCP and Brave Search MCP so the assistant can combine context.

3Grant the minimum read scopes needed for this content workflow.

4Open the workspace, channel, repository, database, or account you want the assistant to use.

5Paste the prompt from this recipe into your AI client.

The prompt

You are helping a Marketing teammate with this workflow: Summarize Stripe revenue changes for campaign reports.
Use the connected Notion MCP, Slack MCP, Brave Search MCP tools to gather only the information needed for content.
Create a concise result with: summary, important details, recommended next actions, owners, and links to sources.
Flag anything uncertain, stale, sensitive, or missing instead of guessing.
Do not make changes without asking me to confirm the final draft.

Paste into Claude Desktop. It will use your connected AI servers: Notion MCP, Slack MCP, Brave Search MCP.

Expected outcome

Spot campaign risks earlier with concise summaries of feedback, performance signals, and next best actions

Success checklist

0/4

The output explains the content context in plain English.Every recommendation includes a source, owner, or next action.Sensitive data is summarized only at the level needed for the task.Marketing teammates can use the result without asking for extra background.

Troubleshooting

MCP server is not available in the client

Cause

The server config was not saved, the client was not restarted, or Node.js cannot run npx.

Solution

Run Notion MCP manually with its install command, then restart your MCP client.

The assistant cannot find the expected records

Cause

The connected account lacks access to the workspace, channel, repo, database, or page.

Solution

Grant the missing read scope and test with one known record before running the full recipe.

The result is too broad or includes stale context

Cause

The prompt did not limit the date range, source, account, or project clearly enough.

Solution

Add the relevant team, date range, channel, repo, account, or page name to the prompt.