Follow these steps
Complete the workflow, then verify it
- 1
Public monitoring
Find a public App Store or Google Play listing in the Flow setup. No developer-account authorization is required for ordinary public written-review monitoring.
- 2
Destination access
Authorize Slack or Zendesk, supply Freshdesk’s subdomain/API key, or complete the selected Teams/email setup. Use only an account that can access the intended destination.
- 3
Reply access
Enable Reply-to-Review only for an eligible Slack or Zendesk Flow. Complete the separate store-account authorization and approve its per-Flow price. Public monitoring does not confer permission to publish replies.
- 4
Google Play complete ratings
Authorize the separate report-data connection if you need star-only ratings. Check source notes and freshness when interpreting the report.
- 5
Request support securely
Send the Flow name, public listing, destination type and approximate failure time. Do not send passwords, API keys, payment information or private customer records in a support message.
Quick checklist
- ✓Access matches the selected capability.
- ✓Destination belongs to the intended team.
- ✓Secrets entered only in the appropriate connection form.
If something does not work
Monitoring works but replies do not+
Check the separate reply setup, store permission and eligibility status.
An integration loses access+
Use Manage connection to reconnect the affected destination, then verify delivery.
Frequently asked questions
Can I monitor a public competitor listing?+
A selectable public listing can be monitored without owning its developer account. You cannot publish replies for an app you do not control.
Where are data-handling terms?+
Read the Privacy Policy and Terms linked in the footer; contact support for a specific access question.