Follow these steps
Complete the workflow, then verify it
- 1
Create a Status Report Flow
Open Create Flow and choose the Status Report task. Select the app review source and destination that the report owner already uses.
- 2
Choose the schedule
Use weekly reports for release and support cadence. Use monthly reports for leadership trends, portfolio review, and longer-term rating movement.
- 3
Set the scope
Choose the apps, platforms, locales, or filters that answer the report owner’s question. Keep the report focused enough to read in one meeting.
- 4
Define the meeting outcome
Decide what the report should make possible: assign a recurring issue, compare a release, review a support gap, or spot rating movement.
- 5
Send a test and schedule
Verify the first report destination before enabling the schedule. Add owners and a follow-up date to the meeting or workflow where the report is reviewed.
Quick checklist
- ✓The report has one decision-making audience.
- ✓The schedule matches the team’s review cadence.
- ✓The scope is narrower than the full raw stream.
- ✓A destination owner knows when to expect it.
If something does not work
The report is too long to use+
Reduce the number of sources or filters and move urgent reviews to a notification Flow. A report should explain movement and exceptions, not repeat every event.
The report arrives but no action follows+
Add an owner and a recurring meeting prompt. Use the report to answer what changed, what needs attention, and what to check next—not only to display a rating.
Frequently asked questions
Should I use alerts or reports?+
Use alerts for individual reviews that need timely ownership. Use reports for trends, recurring themes, and decisions that can wait for a weekly or monthly cadence.
Can a report go to Slack or email?+
Choose the destination supported by the Flow setup and the audience that will act on the summary.