Integrations
Everything Reply Argus connects to.
The ways you bring your world into Reply Argus: your review sources, the channels your team already works in, and where your roadmap lives. Connect any of them in Settings in a couple of clicks. To drive it all from an AI agent, see Agentic Tools.
Review sources
Where your reviews come from. Connect these first. Nothing works without a source.
Apple App Store
Pulls your App Store reviews into the unified inbox and posts your replies back.
For Every iOS app owner.
Google Play
Pulls Google Play reviews into the inbox and posts replies (within Play's ~7-day reply window).
For Every Android app owner.
Alerts
Where Reply Argus pings you. Pick the channels your team already lives in.
Slack
Posts a message when a review lands, a draft is ready, or a reply publishes.
For Teams that run support in Slack.
Telegram
DMs you review activity in real time.
For Solo founders who live on their phone.
Discord
Posts review activity to a Discord channel.
For Communities and indie teams on Discord.
Webhook
POSTs a JSON payload to your endpoint on each event. Build whatever you want on top, including email via Zapier / Make / n8n.
For Developers wiring Reply Argus into their own systems, or anyone who wants email.
Signal export destinations
Where your ranked feature requests land. Signal ranks recurring requests into an evidence-backed feed, reviews ranked by what to fix first. Push each entry, one-way, into the tool your team already plans in. Signal is on Indie and up; file downloads are always free.
Jira
Pushes a roadmap card into a Jira project as an issue: title, the evidence summary, and links back to the source reviews. One-way export, not a two-way sync.
For Product and engineering teams who plan in Jira.
Notion
Adds a roadmap card as a page in a Notion database, carrying the evidence summary and links to the reviews behind it. One-way push.
For Teams whose roadmap lives in a Notion database.
Google Sheets
Appends a roadmap card as a row (title, count, status, and the evidence) to a Google Sheet. One-way export.
For Anyone who'd rather triage in a spreadsheet.
DevRev
Creates a DevRev work item from a roadmap card, with its evidence summary and review links. One-way push, authenticated by a token.
For Teams running product + support on DevRev.
File download
Downloads a card (or the whole board) as CSV, Markdown or JSON, no connection needed. The one export that's ungated.
For Everyone, including the Free plan.
From the blog
Wiring it up
Integrations FAQ
Connections, answered.
What you can plug in, where alerts land, and how to pull your data out.
Start connecting freeWhich review sources can I connect?
The Apple App Store and Google Play. You connect each with your own developer credentials, and reviews from both stores flow into one inbox. Connecting a store is the only required step to start; everything else is optional.
Can I get review alerts in Slack?
Yes. Argus can alert you in Slack, Telegram, Discord, email, or your own webhook the moment a new review lands, a draft is ready, or a reply publishes. Rating-crash and review-spike anomaly alerts (which watch each app's last 24 hours against a 28-day baseline) are included on Indie and up. Alert channels are set up per app in Settings.
Is there an API?
Yes, a read-only REST API on Pro and up. You mint a workspace-scoped API key and pull your apps, your reviews (each with its reply), and your Signal feature-request items over simple endpoints. Reads are paginated and rate-limited per key, and keys are managed in Settings under Developers.
Where can I export the feature requests Signal finds?
Push them one-way to Notion or Google Sheets with a Connect click (available on Indie and up), or download any board as CSV, Markdown, or JSON for free on every plan. Jira and DevRev are coming soon. Exports are a clean handoff into your workflow, not a two-way sync to babysit.
Do you support webhooks?
Yes. Add a webhook as an alert channel and Argus sends events as JSON POSTs: review.created, draft.created, reply.published, digest.weekly, anomaly.detected, plus a test ping you can fire yourself. Every webhook POST is HMAC-signed so you can verify it came from Reply Argus and was not tampered with, and the signing secret is revealable to admins in the connect flow.
Can I run all of this from an AI assistant?
Yes. Reply Argus is a remote MCP server, so you can add it by URL in Claude, Cursor, Codex, or any MCP client and drive triage, drafting, analytics, and approved publishing in plain language. See the Agentic Tools page for the full toolkit and one-click install steps.
Built to be trusted with your data
The protections behind every review we read and every reply we draft.
Encrypted, and yours alone
Your store credentials are encrypted at rest and in transit. We never see your raw keys.
Isolated per workspace
Reviews, replies, and knowledge are isolated at the database layer. One workspace can never read another's.
We never store card data
Payments run through a merchant of record. Card details never touch our servers.
Scoped, revocable access
Role-based permissions, OAuth for integrations, and hashed API keys you can revoke anytime.
Nothing ships without your say-so
Drafts never publish on their own. Auto-publish is an explicit opt-in, off by default.
Hardened by default
Strict security headers, a content security policy, enforced HTTPS, and signed, verified webhooks.
Connect once. Watch everywhere.
Bring your stores in, wire your alerts, then let an AI agent run it, set up in minutes.
Store credentials are encrypted at rest. Revoke any connection anytime.