
StackAdapt Brief
v0.1.0Every Monday, where last week's programmatic spend went and what it bought.
StackAdapt Brief
agents
Spend Reader
.agents/spend-reader/
Weekly StackAdapt Brief
0 9 * * 1
1
Agents
1
Jobs
1
Depts
2
Pages
Reads last week's StackAdapt spend across every campaign and writes one short brief saying where the money went and what it bought.
StackAdapt Brief
Every Monday, where last week's programmatic spend went and what it bought.
What you get
One page, waiting for you Monday morning. Every campaign that spent money last week on StackAdapt gets one line — what it cost, what it actually returned, and whether that got better or worse than the week before. Biggest spender first, so the campaign quietly eating your budget doesn't hide at the bottom.
Nothing is changed. No bid, budget, status or target is touched — it only reads.
How to look at it
Open the Weekly Brief app in this cabinet. It comes pre-filled with a made-up example so you can see the shape of it straight away — the page says clearly that those campaigns are fake. Your first real brief takes its place.
Before it can read your real StackAdapt
Connect StackAdapt in Cabinet's integrations screen. You'll need an API key from your StackAdapt account — the screen walks you through it, and Cabinet keeps the key in a locked file on your own machine. It goes nowhere else.
Set aside five minutes for it once. After that it stays connected. Until then the page keeps showing the example.
What's inside
- Spend Reader — the one agent. Reads last week's campaigns, writes the brief.
- Weekly StackAdapt Brief — the one routine. Runs at 09:00 every Monday.
- Weekly Brief — the one page. Opens on this week, with a picker for earlier ones.
$ git clone --filter=blob:none --sparse https://github.com/cabinetai/cabinets.git && cd cabinets && git sparse-checkout set stackadapt-brief