---
title: "Build a Monday Marketing Brief That Runs Itself With groas"
description: "Schedule an agent to pull groas data, flag CPA changes and deliver a one-page Monday brief. Choose an assistant or script, with changes held for approval."
url: "https://groas.com/post/a-scheduled-ai-agent-for-the-monday-marketing-brief-build-it"
image: "https://pub-87da24ecbbfc4c3bad6875f3aa013712.r2.dev/generated-images/b000bbdb-dc6e-45e1-8a6f-3bb329bd9069.png"
published: "2026-11-20T16:35:15.238Z"
modified: "2026-11-20T16:35:15.323Z"
---

November 20, 2026 · 10 min read

# Build a Monday Marketing Brief That Runs Itself With groas

[](https://groas.com/author/alexander-perelman)

[Alexander Perelman](https://groas.com/author/alexander-perelman)Personally Tested

Head Of Product @ groas

[LinkedIn](https://www.linkedin.com/in/alexander-433793253/)

![A tiny model crew delivers a one-page brief across a desk at dawn, then queues behind a velvet rope with proposals, waiting for a giant human stamp.](https://pub-87da24ecbbfc4c3bad6875f3aa013712.r2.dev/generated-images/b000bbdb-dc6e-45e1-8a6f-3bb329bd9069.png)

In this article

1. [1. Choose the route that can actually call groas](#1-choose-the-route-that-can-actually-call-groas)
2. [2A. Connect groas and test the scheduled assistant](#2a-connect-groas-and-test-the-scheduled-assistant)
3. [2B. Schedule an authorized agent script](#2b-schedule-an-authorized-agent-script)
4. [3. Paste a prompt that produces decisions, not commentary](#3-paste-a-prompt-that-produces-decisions-not-commentary)
5. [4. Add explicit anomaly rules](#4-add-explicit-anomaly-rules)
6. [5. Make approval a real boundary](#5-make-approval-a-real-boundary)
7. [6. Deliver to one place and keep the decision there](#6-deliver-to-one-place-and-keep-the-decision-there)
8. [7. Verify the run, then add competitor context](#7-verify-the-run-then-add-competitor-context)

The best Monday marketing brief is one nobody has to remember to run. Schedule the reporting chore, not the decision: let an agent pull the numbers, explain what moved and leave proposed changes waiting for approval.

By the end of this tutorial, you will have a weekly workflow that calls groas, compares two complete weeks and produces a one-page brief. It reports spend, conversions, CPA and ROAS, flags exceptions and proposes changes. **It does not change your ad accounts.**

Before starting, have these ready:

- A groas account with your ad accounts and website connected.
- An assistant with scheduling **and authenticated groas tool access during scheduled runs**, or an authorized agent script with a groas API key.
- One delivery destination and one named approver.
- Your account scope, reporting timezone and performance targets.

The distinction between scheduling and tool access matters. An assistant that can remind you to run a report has not necessarily learned to run it.

## 1. Choose the route that can actually call groas

Pick one path before configuring the brief:

| Route                           | Use it when                                                           | Prove this before proceeding                                                                |
| ------------------------------- | --------------------------------------------------------------------- | ------------------------------------------------------------------------------------------- |
| **A: Scheduled assistant task** | You want a no-code workflow inside your assistant.                    | The scheduled task can call authenticated groas tools, not just generate text.              |
| **B: Scheduled agent script**   | You need a file, logs or a workflow covering several client accounts. | The runner can authenticate, call groas and save its output without an interactive session. |

ChatGPT’s [scheduled tasks](https://help.openai.com/en/articles/10291617-scheduled-tasks-in-chatgpt) provide a scheduling option, but a recurring task alone does not prove that your connected tools will be available when it runs. Check that separately.

**Action:** Choose `Path A` or `Path B`. Set the intended cadence to `Monday, 06:00` in your reporting timezone, where your scheduler supports that exact time.

**Expected result:** One route owns the weekly run. There is no second task producing a competing version of the same brief.

**Common mistake:** Picking the assistant you already use without testing its scheduled tool access. I would rather discover that limitation during setup than receive a beautifully written report with no fresh numbers.

## 2A. Connect groas and test the scheduled assistant

Skip this section if you chose Path B.

### Connect before scheduling

**Action:** Follow the [groas MCP setup](https://groas.com/mcp) for your assistant. Use the groas connection endpoint when the setup asks for it:

```text
https://mcp.groas.ai/mcp
```

Complete authorization, then ask the assistant to retrieve reporting data for the accounts you intend to include. Start with read-only access wherever the connection permits it.

**Expected result:** The assistant returns account data through groas rather than asking you to paste a spreadsheet.

**Common mistake:** Treating a visible connection as proof of a working connection. **A successful data pull is the test.**

### Create the recurring task

**Action:** Create a weekly task using your assistant’s scheduling controls. Set the day to `Monday`, the time to `06:00` where supported, and confirm the timezone. Paste the prompt in section 3 into the task instructions.

Put the account scope, targets and reporting rules directly in those instructions. Do not assume the task can read files or context from another chat.

**Expected result:** The task shows the intended recurring schedule and retains the full reporting instructions.

**Common mistake:** Scheduling “send my usual report” and expecting the assistant to reconstruct what _usual_ means every week. Give the task its own complete brief.

### Test the scheduled execution context

**Action:** Run a test through the scheduling workflow and check whether it can call groas with authorization. Confirm that its output contains fresh reporting data and the correct date ranges.

**Expected result:** The task retrieves data without a new sign-in or a manual prompt supplying the numbers.

**Common mistake:** Testing only in an ordinary chat. A [scheduled message does not establish authenticated tool access](https://sourcetomcp.com/articles/weekly-marketing-report-with-claude). If the scheduled run cannot use groas, use Path B rather than trusting the clock to fix it.

## 2B. Schedule an authorized agent script

Skip this section if Path A passes its scheduled-access test.

This route needs a working agent runner, not just an API key and optimism. Use the [weekly API-driven script and report](https://groas.com/post/build-your-own-ai-brand-monitor-in-an-af) as the starting pattern, then configure it for the prompt below.

### Store the key outside the prompt

**Action:** Create a groas API key using the [groas setup instructions](https://groas.com/mcp). Store it in the runner’s environment as `GROAS_API_KEY`, not in the report prompt or a committed script.

**Expected result:** The runner authenticates without exposing the raw key in the brief or its instructions.

**Common mistake:** Pasting the key into a chat so the agent can “remember” it. **Credentials belong in the execution environment, not the weekly brief.**

### Configure the weekly job

**Action:** Configure your scheduler to invoke the working, authorized runner at `06:00` every Monday. The cron schedule expression is:

```text
0 6 * * 1
```

That is the schedule field, not a complete executable job. Point it at your actual runner. Configure that runner to use the prompt below, write the report to `monday-brief.md` and retain a run log such as `brief.log`.

Confirm the scheduler’s timezone and make sure `GROAS_API_KEY` is available in its execution environment. Choose where errors go before enabling the recurring run.

**Expected result:** A test run creates a dated brief and a log showing whether data retrieval and report generation succeeded.

**Common mistake:** Scheduling a command that works in your terminal but cannot authenticate when it runs unattended. Test the scheduled job, not merely the script.

### Keep execution read-only

**Action:** Restrict the runner’s access to reporting wherever possible. Keep the instruction `Draft proposals. Do not execute.` at the top of the prompt.

**Expected result:** The runner retrieves data and writes its report without changing ads, bids, budgets, keywords or creative.

**Common mistake:** Treating a prompt as a permission boundary. Use restricted access as well as instructions; do not give the reporting job write access just because the first run succeeds.

![Clay figure waiting beside an empty Monday report inbox](https://pub-87da24ecbbfc4c3bad6875f3aa013712.r2.dev/generated-images/f34f4e19-064c-42f8-9ce9-de9378a9120a.png)

## 3. Paste a prompt that produces decisions, not commentary

Use [two complete weeks for comparison](https://sourcetomcp.com/articles/weekly-marketing-report-with-claude). At 06:00 Monday, “last seven days” must not quietly include six hours of the new week.

Keep Google Ads primary conversions separate from GA4 key events. Otherwise, the review becomes an argument about definitions instead of a decision about spend.

**Action:** Replace the bracketed fields below, then paste the complete prompt into your task or runner configuration.

```text
Draft proposals. Do not execute.

MONDAY MARKETING BRIEF

Accounts: [account names or IDs]
Reporting timezone: [timezone]
Targets by account/channel: [CPA, ROAS and other agreed goals]
Approver: [name]

Window: the last 7 complete days, ending Sunday, compared with
 the preceding 7 complete days. State both date ranges.

1. Retrieve reporting data from groas for the accounts above.
Include spend, conversions, CPA and ROAS for Google, Meta and
Microsoft/Bing where connected and available.
Keep Google Ads primary conversions separate from GA4 key events.
Do not combine incompatible conversion definitions into one total.

2. Write one page using these five blocks:
- TL;DR: outcomes versus the stated goals.
- Performance: current week versus prior week and goals.
- What changed: documented account changes and observed movements.
- What happens next: proposed actions, not executed changes.
- What the approver needs to decide or clarify.

3. Use only returned numbers and supplied targets.
State what is missing. Do not invent a source, target or explanation.
Separate observed changes from possible explanations.

4. For each proposal, show the account/campaign, what was detected,
the exact proposed change, why it is proposed and expected impact.
Do not invent a numerical impact forecast.
Wait for approval. Do not change ad accounts.

5. Return the brief to the configured workflow.
Do not independently publish, post or send it elsewhere.
```

**Expected result:** A repeatable, [five-block brief](https://www.adside.ai/tools/client-report-writer) that leads with outcomes and ends with decisions.

**Common mistake:** Asking “what changed and why” without separating evidence from inference. **A plausible explanation is not a documented cause.** Missing data belongs in the brief, not underneath confident prose.

## 4. Add explicit anomaly rules

A prompt that says “flag anything unusual” hands the definition of _unusual_ to the agent. I prefer to make that decision before Monday.

**Action:** Add the following rules to the instructions. Treat these as starting thresholds, not a claim that every account needs the same alerts.

```text
Flag these conditions:
- CPA is up 30% versus the prior complete week.
- CPA exceeds 2x the supplied target over the reporting week.
- CPA is 40% above the 14-day rolling average.
- Spend is zero on an active campaign.
- Conversions are zero on an active campaign.

Retrieve the comparison data needed for each rule.
If data or a target is unavailable, mark that rule as not evaluated.
Do not invent the missing input.
Do not report a numerical CPA when zero conversions prevents it.
Group overlapping flags for the same campaign.
```

These follow the shape of common [CPA and zero-spend alert rules](https://knowledgebase.adzooma.com/knowledge/automated-alerts-guide). Review the values against your accounts before saving them.

**Expected result:** Each flag names the campaign, the breached rule and the numbers behind it. Several rules firing on one campaign do not become several paragraphs saying the same thing.

**Common mistake:** Filling the brief with CTR and impression movements while the CPA problem gets one line. Check spend and conversion volume before writing the explanation. **Prioritize flags that could change a decision.**

## 5. Make approval a real boundary

The report should arrive automatically. Account changes should not.

**Action:** Keep `Draft proposals. Do not execute.` as the first instruction. Name one approver and require every proposed change to include:

- The account and campaign affected.
- The condition that triggered the proposal.
- The exact change being proposed.
- The reason and expected impact, with uncertainty stated plainly.
- The approver’s decision before any separate execution step.

Use the [human-in-the-loop workflow](https://www.planconversion.com/blog/human-in-the-loop-ai-agents-marketing-approval-workflow) as the operating pattern: draft, check, queue, approve, execute with limited permissions, log. This tutorial stops at the approval queue; it does not configure automatic execution after a reply.

**Expected result:** A proposal contains enough detail to approve, edit or reject without another round of “what exactly do you mean?”

**Common mistake:** Quietly turning approval into a notification. “I changed the budget; let me know if that is wrong” is not approval. **Keep groas autopilot off for this reporting workflow.**

![Approval queue with a proposed budget change awaiting human sign-off](https://pub-87da24ecbbfc4c3bad6875f3aa013712.r2.dev/generated-images/1f5c7c7e-7778-47a1-a2b7-2acb9734e962.png)

## 6. Deliver to one place and keep the decision there

**Action:** Choose one primary review destination supported by your workflow: the task’s chat, email or a shared Slack channel. Configure delivery there rather than asking the agent to improvise a destination.

For Path B, also retain `monday-brief.md` and the run log. The file is the record; the delivery destination is where someone reads it.

Keep the prompt’s restriction on independent sending. The configured workflow delivers the report; the agent does not gain permission to publish or message elsewhere.

**Expected result:** The approver sees the same five blocks in the same place every Monday. Delivery does not wait for approval; proposed account changes do.

**Common mistake:** Routing the brief everywhere and assuming that increases accountability. Nobody owns a decision that appears to belong to three different channels.

**Action:** Review in ten minutes: read the TL;DR, inspect the flags, then approve, edit or reject each proposal. Keep the decisions with the report so the record shows the run date, decision and decision-maker.

**Expected result:** One readable trail from evidence to proposal to decision.

**Common mistake:** Reviewing the charts and leaving the proposal list untouched. **The useful output is the decision, not proof that the report ran.**

## 7. Verify the run, then add competitor context

Do not call the setup finished because a task says it is active. Verify the output and the absence of writes.

1. **Check the run at `06:15` Monday.** Inspect the task history or scheduler log. Confirm completion and fresh groas retrieval, not merely a generated message. If it failed, inspect authorization, connection status and the schedule before rerunning. The mistake is treating a quiet inbox as a quiet account.
2. **Match three figures to groas.** Check spend, conversions and CPA for the same account or channel, dates, currency and conversion definition. Confirm the brief names two complete weeks and excludes Monday’s partial day. The mistake is comparing totals built from different scopes and blaming the arithmetic.
3. **Confirm zero account writes.** Inspect change history in the connected ad accounts. There should be no changes from the reporting agent. Confirm the output contains proposals, not claims of completed changes. The mistake is accepting “draft only” in the prompt without checking what happened.
4. **Check delivery and ownership.** Confirm the brief reached the chosen destination and the named approver can respond there. The mistake is proving generation while leaving review unowned.

**A successful run has fresh data, matching figures, visible proposals and zero account changes.** Keep the workflow unchanged until it produces two clean Mondays in a row.

Then change one thing first: add rival context. Ask the agent to retrieve the top three competitor ads groas saw that week and add three short lines beneath the flags: who appeared, what angle they used and whether that merits attention. Keep observations separate from guesses about a rival’s budget or results.

That is a better next step than adding another page of charts. **The brief earns its keep when Monday starts with a decision, not a download.**

## Frequently Asked Questions

### Should I use a scheduled assistant task or an agent script for my groas Monday brief?

Use a scheduled assistant task (Path A) for a no-code workflow inside your assistant, or a scheduled agent script (Path B) when you need a file, logs, or a workflow covering several client accounts. Whichever you choose must be able to call authenticated groas tools during scheduled runs, not just generate text. One route should own the weekly run.

### Why can't my assistant run my scheduled report even though it's connected to groas?

Scheduling and tool access are separate capabilities: a recurring task can exist without authenticated groas tools being available when it runs. Run a test through the scheduling workflow and check whether the output contains fresh reporting data with the correct date ranges, without a new sign-in. If the scheduled run cannot use groas, switch to the agent script route.

### What date range should a weekly marketing report compare?

Compare the last 7 complete days ending Sunday with the preceding 7 complete days, and state both date ranges explicitly. A rolling 'last seven days' window running Monday at 06:00 would quietly include six hours of the new week. Also confirm the brief excludes Monday's partial day.

### What thresholds should I set for CPA alerts in my weekly brief?

Flag CPA up 30% versus the prior complete week, CPA exceeding 2x the supplied target over the reporting week, CPA 40% above the 14-day rolling average, zero spend on an active campaign, and zero conversions on an active campaign. Treat these as starting thresholds to review against your accounts. If data or a target is unavailable, the rule should be marked as not evaluated rather than estimated.

### Will the scheduled reporting agent change my ad campaigns automatically?

No. Keep the instruction 'Draft proposals. Do not execute.' at the top of the prompt, restrict the runner's access to reporting, and require a named approver to sign off before any separate execution step. Approval means a human decision on each proposal, not a notification after a change was already made.

### How do I verify my automated Monday brief is actually working?

Check the task history or scheduler log at 06:15 Monday, match spend, conversions and CPA against groas for the same dates and definitions, inspect the ad accounts' change history for zero writes from the reporting agent, and confirm the brief reached the named approver. A successful run has fresh data, matching figures, visible proposals and zero account changes. Keep the workflow unchanged until it produces two clean Mondays in a row.

### What should I add to my marketing brief after the basic workflow works?

Add rival context: ask the agent to retrieve the top three competitor ads groas saw that week and add three short lines beneath the flags covering who appeared, what angle they used and whether that merits attention. Keep observations separate from guesses about a rival's budget or results.

## Run Your Marketing On groas

Plug ChatGPT, Claude or any AI agent into groas and let it do the work of a whole marketing team: $19 a month flat with every feature included, and autopilot whenever you’re ready.

[Start For $19](https://groas.com/pricing)

[Or have groas run it for you](https://groas.com/done-for-you)

## Structured data

```json
{"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://graph.groas.com/entity/groas","name":"groas","url":"https://groas.com/","description":"groas is the marketing infrastructure for your own AI: it connects your AI to all your marketing and gives it proprietary marketing data collected 24/7. Plug Claude, ChatGPT or any AI agent into groas and run all your marketing from it, for a tiny fraction of the usual cost, with the groas app there whenever you want to see more. It is the layer ChatGPT, Claude and any AI assistant run a business’s online marketing on. Through groas an assistant can do anything you could do natively in Google Ads, Bing Ads, Meta Ads and ChatGPT ads, on your website and in AI search, and, where the owner switches it on, can run connected campaigns by itself, so AI agents do the work a whole marketing team used to. groas also gives those agents large-scale proprietary marketing data it collects around the clock, on any schedule the owner chooses: every ad competitors run on Google and Meta, their landing pages and full funnels with the offers and prices in them, Reddit customer research, AI search answers from ChatGPT, Google AI Overviews, Gemini, Claude and Perplexity, and SEO data from Semrush and Ahrefs, backlinks included ($19 a month, flat, with everything included, for unlimited teammates on one shared workspace and unlimited ad accounts and websites, delivered as an MCP server). Separately, its done-for-you service has senior people and proprietary quantitative systems run paid ads, SEO and AI search for businesses, and white label for agencies, from $5,000 a month.","logo":{"@type":"ImageObject","url":"https://groas.com/icon-512.png","width":512,"height":512},"sameAs":["https://www.linkedin.com/company/groas/"]},{"@type":"WebSite","@id":"https://groas.com/#website","name":"groas","url":"https://groas.com/","inLanguage":"en-US","publisher":{"@id":"https://graph.groas.com/entity/groas"}},{"@type":"WebPage","@id":"https://groas.com/post/a-scheduled-ai-agent-for-the-monday-marketing-brief-build-it#webpage","url":"https://groas.com/post/a-scheduled-ai-agent-for-the-monday-marketing-brief-build-it","name":"Build a Monday Marketing Brief That Runs Itself With groas","description":"Schedule an agent to pull groas data, flag CPA changes and deliver a one-page Monday brief. Choose an assistant or script, with changes held for approval.","inLanguage":"en-US","isPartOf":{"@id":"https://groas.com/#website"},"about":{"@id":"https://graph.groas.com/entity/groas"},"primaryImageOfPage":{"@type":"ImageObject","url":"https://pub-87da24ecbbfc4c3bad6875f3aa013712.r2.dev/generated-images/b000bbdb-dc6e-45e1-8a6f-3bb329bd9069.png"},"breadcrumb":{"@id":"https://groas.com/post/a-scheduled-ai-agent-for-the-monday-marketing-brief-build-it#breadcrumb"},"dateModified":"2026-11-20T16:35:15.323Z","mainEntity":{"@id":"https://groas.com/post/a-scheduled-ai-agent-for-the-monday-marketing-brief-build-it#article"}},{"@type":"BreadcrumbList","@id":"https://groas.com/post/a-scheduled-ai-agent-for-the-monday-marketing-brief-build-it#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://groas.com/"},{"@type":"ListItem","position":2,"name":"Blog","item":"https://groas.com/blog"},{"@type":"ListItem","position":3,"name":"Build a Monday Marketing Brief That Runs Itself With groas","item":"https://groas.com/post/a-scheduled-ai-agent-for-the-monday-marketing-brief-build-it"}]},{"@type":"BlogPosting","@id":"https://groas.com/post/a-scheduled-ai-agent-for-the-monday-marketing-brief-build-it#article","url":"https://groas.com/post/a-scheduled-ai-agent-for-the-monday-marketing-brief-build-it","mainEntityOfPage":{"@id":"https://groas.com/post/a-scheduled-ai-agent-for-the-monday-marketing-brief-build-it#webpage"},"isPartOf":{"@id":"https://groas.com/blog#blog"},"headline":"Build a Monday Marketing Brief That Runs Itself With groas","description":"Schedule an agent to pull groas data, flag CPA changes and deliver a one-page Monday brief. Choose an assistant or script, with changes held for approval.","datePublished":"2026-11-20T16:35:15.238Z","dateModified":"2026-11-20T16:35:15.323Z","image":{"@type":"ImageObject","url":"https://pub-87da24ecbbfc4c3bad6875f3aa013712.r2.dev/generated-images/b000bbdb-dc6e-45e1-8a6f-3bb329bd9069.png"},"author":{"@id":"https://groas.com/author/alexander-perelman#person"},"publisher":{"@id":"https://graph.groas.com/entity/groas"},"keywords":"groas, brief, monday, data, expected result, common mistake, assistant, reporting","wordCount":2190,"inLanguage":"en-US"},{"@type":"Person","@id":"https://groas.com/author/alexander-perelman#person","name":"Alexander Perelman","jobTitle":"Head Of Product @ groas","description":"My background includes Goldman Sachs and Stanford Computer Science.","image":"https://groas.com/media/blog/4f17cac3a81acc224cc1b2cfab8f94bbc295a3089d13e8421125771ef8d4064f.jpg","worksFor":{"@id":"https://graph.groas.com/entity/groas"},"sameAs":["https://www.linkedin.com/in/alexander-433793253/"]},{"@type":"FAQPage","@id":"https://groas.com/post/a-scheduled-ai-agent-for-the-monday-marketing-brief-build-it#faq","mainEntity":[{"@type":"Question","name":"Should I use a scheduled assistant task or an agent script for my groas Monday brief?","acceptedAnswer":{"@type":"Answer","text":"Use a scheduled assistant task (Path A) for a no-code workflow inside your assistant, or a scheduled agent script (Path B) when you need a file, logs, or a workflow covering several client accounts. Whichever you choose must be able to call authenticated groas tools during scheduled runs, not just generate text. One route should own the weekly run."}},{"@type":"Question","name":"Why can't my assistant run my scheduled report even though it's connected to groas?","acceptedAnswer":{"@type":"Answer","text":"Scheduling and tool access are separate capabilities: a recurring task can exist without authenticated groas tools being available when it runs. Run a test through the scheduling workflow and check whether the output contains fresh reporting data with the correct date ranges, without a new sign-in. If the scheduled run cannot use groas, switch to the agent script route."}},{"@type":"Question","name":"What date range should a weekly marketing report compare?","acceptedAnswer":{"@type":"Answer","text":"Compare the last 7 complete days ending Sunday with the preceding 7 complete days, and state both date ranges explicitly. A rolling 'last seven days' window running Monday at 06:00 would quietly include six hours of the new week. Also confirm the brief excludes Monday's partial day."}},{"@type":"Question","name":"What thresholds should I set for CPA alerts in my weekly brief?","acceptedAnswer":{"@type":"Answer","text":"Flag CPA up 30% versus the prior complete week, CPA exceeding 2x the supplied target over the reporting week, CPA 40% above the 14-day rolling average, zero spend on an active campaign, and zero conversions on an active campaign. Treat these as starting thresholds to review against your accounts. If data or a target is unavailable, the rule should be marked as not evaluated rather than estimated."}},{"@type":"Question","name":"Will the scheduled reporting agent change my ad campaigns automatically?","acceptedAnswer":{"@type":"Answer","text":"No. Keep the instruction 'Draft proposals. Do not execute.' at the top of the prompt, restrict the runner's access to reporting, and require a named approver to sign off before any separate execution step. Approval means a human decision on each proposal, not a notification after a change was already made."}},{"@type":"Question","name":"How do I verify my automated Monday brief is actually working?","acceptedAnswer":{"@type":"Answer","text":"Check the task history or scheduler log at 06:15 Monday, match spend, conversions and CPA against groas for the same dates and definitions, inspect the ad accounts' change history for zero writes from the reporting agent, and confirm the brief reached the named approver. A successful run has fresh data, matching figures, visible proposals and zero account changes. Keep the workflow unchanged until it produces two clean Mondays in a row."}},{"@type":"Question","name":"What should I add to my marketing brief after the basic workflow works?","acceptedAnswer":{"@type":"Answer","text":"Add rival context: ask the agent to retrieve the top three competitor ads groas saw that week and add three short lines beneath the flags covering who appeared, what angle they used and whether that merits attention. Keep observations separate from guesses about a rival's budget or results."}}]}]}
```
