Skip to main content
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

Watch on Loom. 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

Turn survey responses into your next creative brief

Use new post-purchase responses in Google Sheets to generate angles based on customer language, then shortlist directions for your next ad batch.

Bring fresh objections into your ads

Review recent Meta ad comments for recurring questions so you can choose which objections your next hooks or landing-page updates should answer.

Start your media review with priorities

Request a recurring Meta performance briefing that highlights changes worth investigating before you decide what to test next.

​
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 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

1

Open Schedule

From the StefanBrain sidebar, open Schedule, then select New Schedule.
2

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.
3

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.
4

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.
5

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.

​
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.
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.

​
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.

​
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.
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 when a connection needs attention. For account-access issues, contact support@stefanbrain.com.

​
Next steps