Follow these steps
Complete the workflow, then verify it
- 1
Open the saved Flow
In the dashboard, open the Flow you want to verify. Confirm the source app, destination, task, and rules are the ones you intend to test.
- 2
Trigger the test alert
Use the Flow setup action to send the test alert. Wait for the destination to receive the message before changing the configuration.
- 3
Check the review context
Look for rating, title or body, app or platform context, locale or version where available, timestamp, and the original review link.
- 4
Ask the owner to acknowledge it
The person responsible for the destination should be able to identify the next action without opening several dashboards or asking who owns the message.
- 5
Only then expand the Flow
If the handoff is correct, add another app, locale, keyword, or destination. If it is not, fix the smallest part of the setup and send another test.
Quick checklist
- ✓The test reached the intended destination.
- ✓Review details are readable and complete.
- ✓The original review link works.
- ✓The destination owner knows the next action.
If something does not work
No test alert arrives+
Check the Flow status, connected account, destination permissions, and selected channel or inbox. Reconnect the destination if authorization has expired, then send the test again.
The test arrives but the link or fields are missing+
Confirm the source app and Flow are correct, then report the missing context to support with the Flow configuration—not private review content.
Frequently asked questions
Does a test alert count as a real review?+
No. It is a delivery check for the Flow and destination. It should not be treated as customer feedback or included in product trend analysis.
When should I send another test?+
Send one after changing the destination, permissions, source app, or important alert rules.