Weekly Amazon Seller performance recap in Notion

By General Input

Every Monday at 8am, get an executive recap of last week's Amazon store performance posted to Notion, so you can read your business in two minutes.

Integrations

  • Amazon Seller Partner
  • Notion

Type

Agentic Task

Categories

  • Operations
  • Finance

Every Monday at 8am in my local time, generate a weekly Amazon Seller performance recap and publish it to Notion so I can read the past week of my store like an executive summary instead of digging through Seller Central. Use a cron trigger.

Data collection from Amazon Seller Partner:

1) Call Search Orders for my marketplace covering the last 7 full days (the most recently completed Mon to Sun window) and capture order count, unit count, and revenue. Then call Search Orders again for the prior 7 days as a baseline for week over week comparisons.

2) Call Create Report to request a sales and traffic report for the same last 7 day window so we get unit, session, page view and conversion context. Also request a returns report (or equivalent) covering the same window. Create Report is asynchronous, so for each reportId returned, poll Get Report with a short backoff loop (start at 5 seconds, double up to 60 seconds, cap total wait around 5 minutes) and keep polling until processingStatus is DONE. If a report fails or is cancelled, note it in the recap and continue instead of crashing the workflow.

3) Once a report is DONE, call Get Report Document to get the pre-signed URL (it expires after 5 minutes, so fetch the data immediately) and download the report contents for use in the analysis.

Analysis the agent should do in-memory before writing to Notion:

- Top 5 SKUs by revenue for the week, with units sold and revenue. Tie-break by units.

- Week over week change in total revenue and total units versus the prior 7 days, expressed as both absolute and percent.

- Refund and cancellation observations, including any SKUs whose refund rate looks unusually high versus the prior week.

- 2 to 3 concrete, specific recommendations grounded in the data, for example 'restock SKU X before it stocks out at current sell-through' or 'investigate the refund spike on SKU Y this week'. No vague advice.

Publishing to Notion:

4) Call Notion Create a Page as a child of my database titled 'Amazon Weekly Reports'. Use the report date (the Monday of the new week, ISO format) as the page title.

5) Call Append Block Children to fill the new page with: a one paragraph executive summary at the top (what happened this week and why it matters), a heading 'Top SKUs' followed by a numbered list or simple table of the top 5 SKUs by revenue, a heading 'Week over week' with the revenue and unit deltas, a heading 'Refunds and cancellations' with the notable observations, and a heading 'Recommendations' with the 2 to 3 action items as a bulleted list.

Tone and formatting rules:

- Executive and skimmable. Short sentences. Numbers up front.

- No em dashes anywhere in the output.

- Format currency with the marketplace's currency symbol and round to whole units.

- If a number is flat (within 2 percent) call it flat instead of inventing a trend.

Make the marketplace (default US), the Notion database name (default 'Amazon Weekly Reports'), and the run time (default Monday 8am) easy to change without rewriting the workflow.

Related prompts

Explore more prompts
Screen chartered vessels for AIS gaps and sanctions red flagsCompare candidate store locations with drive time trade areasBrowse every competitor ad and build a Notion swipe fileAudience persona studio for brand and product marketersArtwork desk for the Notion posts still missing an imageShare of voice dashboard for your brand and competitorsInfluencer campaign roster board with AI creator briefsSmart home entity health cockpit for Home AssistantOpen model approval desk for your production AI stackBid board that watches every procurement portal for you