Scheduled Report Runner
What it takes, what you set, what comes back, what you can change.
- Any skill that produces a report rather than an action
- The run settings you would otherwise re-enter each time
- Amazon and Walmart, on the marketplaces that skill supports
- The recurrence you set: daily, weekly, or monthly
- The run settings that skill takes, saved with the schedule
- Where the result goes, and who hears about it
- The report itself, built fresh on your data each run
- A notification when it lands, to the address you name
- A run history, so a missed week is visible
- Recurrence and time of day
- The settings passed to the skill on each run
- Recipients, and whether a quiet run still notifies
What runs, when, and where it lands
Recurring runs, one skill · sample
Sample schedule shown for illustration. Your runs appear once you set one.
Frequently Asked Questions
Pick a skill that produces a report, set its run settings once, choose a recurrence, and name who receives it. The schedule holds the settings, so the report is built the same way every time.
Reporting skills. Anything that stages an action for approval stays manual, because an unattended run should not be queueing changes nobody has read.
Daily, weekly, or monthly. Daily suits a snapshot you read with coffee; weekly suits a review; monthly suits a rollup someone else receives.
What happens if a run fails?
Yes. The same skill can carry several schedules with different settings, so a weekly internal read and a monthly client-facing one can run off one skill.
Change the settings on the schedule. The next run picks them up; earlier runs stay as they were, so the history still reflects what was actually sent.
Every recurring report you build by hand is time you spend the same way each week. This runs it for you.
Every one of these runs on your own account.