> ## Documentation Index
> Fetch the complete documentation index at: https://docs.stefanbrain.com/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> Follow the content contract in AGENTS.md.
> Treat text as the canonical explanation; video and screenshots enhance it.
> Do not publish unverified product behavior or duplicate an existing canonical article.

# Schedule: Automatically turn data into fresh ad angles

> Run recurring requests against customer feedback and connected marketing data, then use the results to plan your next creative tests.

Use **Schedule** to turn a request you repeat into a recurring task. Give it a
source that changes—such as new survey responses—and get fresh material for
your next round of ads without rebuilding the prompt each time.

## Watch the walkthrough

<video controls playsInline preload="metadata" className="w-full h-auto rounded-xl" poster="/images/tutorials/qa/schedule-poster.jpg" alt="Schedule: Automatically turn data into fresh ad angles" aria-label="Schedule: Automatically turn data into fresh ad angles">
  <source src="https://stefanbrain.com/api/video/adaptive/tutorials/schedule-fresh-ad-angles/full-frame-2026-10-09.mp4" type="video/mp4" />

  <a href="https://stefanbrain.com/api/video/adaptive/tutorials/schedule-fresh-ad-angles/full-frame-2026-10-09.mp4">Watch the walkthrough</a>
</video>

[Watch on Loom](https://www.loom.com/share/77c57ef9671643cc98e8fcfbfdbbc245).
Jump to **0:24** for connected-data examples, **1:08** for survey-based angles,
or **2:22** for testing and refining a task.

## Practical use cases

<CardGroup cols={2}>
  <Card title="Turn survey responses into your next creative brief" icon="message-square">
    Use new post-purchase responses in Google Sheets to generate angles based
    on customer language, then shortlist directions for your next ad batch.
  </Card>

  <Card title="Bring fresh objections into your ads" icon="messages-square">
    Review recent Meta ad comments for recurring questions so you can choose
    which objections your next hooks or landing-page updates should answer.
  </Card>

  <Card title="Start your media review with priorities" icon="chart-no-axes-combined">
    Request a recurring Meta performance briefing that highlights changes
    worth investigating before you decide what to test next.
  </Card>
</CardGroup>

## Before you start

Connect the account containing your data and confirm that StefanBrain can
read the specific sheet or ad account you want to use. See
[connector workflows](/knowledge-base/connectors-automations/connector-use-cases)
for choosing a source and checking the returned evidence.

A recurring prompt needs fresh input to produce useful new work. Repeating
the same request against an unchanged file may give you similar ideas each time.

## Create and test your schedule

<Steps>
  <Step title="Open Schedule">
    From the StefanBrain sidebar, open **Schedule**, then select **New Schedule**.
  </Step>

  <Step title="Describe the task and its source">
    Name the data to read, the time period, and the output you will use.
    Include the sheet link or account name when needed to identify the source.
  </Step>

  <Step title="Choose when and where it runs">
    Set the recurrence and check the time zone. Choose the relevant Project
    or Chat, and add any files or context the request needs.
  </Step>

  <Step title="Save and check its status">
    Save the schedule. If it is paused, select **Resume** to activate recurring
    runs. Check the displayed timing before leaving the page.
  </Step>

  <Step title="Run it now and inspect the result">
    Use **Run now** to test the request. Open the result and check its source,
    dates, and usefulness. Edit the task if it pulls the wrong data or gives
    you repetitive angles.
  </Step>
</Steps>

## A prompt you can reuse

Use this to turn recent customer language into a shortlist your creative team
can develop. Replace the sheet reference with your own source.

```text theme={"system"}
Read the new post-purchase survey responses from the past seven days in
[Google Sheet URL]. Use the connected Google account and the selected Product.

Generate 20 distinct cold-traffic ad angles based on the customers' own
language. Group similar ideas, include the response that inspired each angle,
and shortlist five directions for our next creative brief. Explain what
customer desire or objection each direction addresses.

If there are no new responses, tell me instead of repeating the previous batch.
Read the sheet only; do not edit it.
```

Choose a cadence that matches the source. A weekly survey review is more
useful than hourly runs when responses arrive slowly.

## More recurring workflows to try

Choose a source your connected account can read. If the data lives elsewhere,
keep an updated sheet or document in an accessible source and point the task
there. Test the request with **Run now** before making it recurring.

### Turn support questions into objection-handling hooks

Use a weekly support-summary sheet to find purchase questions your ads could
answer earlier. Leave out customer contact details when preparing the source.

```text theme={"system"}
Read this week's new rows in [support-summary sheet URL]. Group recurring
questions about the selected Product by what might stop someone buying.
Give me 10 distinct hooks that address those concerns, using only product
facts already in our context. For each hook, identify the question it answers.
Shortlist three to develop into ads. Read only.
```

### Turn customer praise into testimonial-led concepts

Review new feedback weekly to find benefits customers describe in their own
words, then choose which ones deserve a creative test.

```text theme={"system"}
Read the past seven days of feedback in [customer-review sheet URL]. Find
repeated benefits and unexpected use cases for the selected Product.
Create 20 distinct testimonial-led ad concepts. Include the source quote
behind each concept and keep quotes separate from proposed ad copy.
Group similar concepts and shortlist five for our next creative brief.
Read only; do not change the source.
```

### Prepare a client-ready weekly action brief

Run this before your client meeting so the team can discuss decisions rather
than spend the call assembling the report.

```text theme={"system"}
Use the connected Meta account for [client]. Compare the last complete week
with the previous week. Show spend, purchases, CPA, and ROAS, then identify
the campaigns behind the biggest changes. Separate observations from possible
explanations. End with the questions we should resolve and the next creative
tests worth considering. Read only; do not change campaigns or budgets.
```

Keep each client's source, account, and Project explicit. Reuse the structure,
not another client's data or conclusions.

## Make each run useful

* Check that the result used the intended account and date range.
* Combine overlapping ideas before choosing your next tests.
* Keep a record of the angles you selected so you can ask for different directions next time.
* Pause a schedule when you no longer need its output.

If a run cannot read its source, check the connector and file access before
changing the prompt. Follow
[reconnection guidance](/knowledge-base/connectors-automations/reconnect-a-service)
when a connection needs attention. For account-access issues, contact
[support@stefanbrain.com](mailto:support@stefanbrain.com).

## Next steps

* [Turn connected data into useful work](/knowledge-base/connectors-automations/connector-use-cases)
* [Develop original hooks and ad copy](/knowledge-base/chat/develop-original-hooks-and-ad-copy)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.