Automations | Revibu - Turn app reviews into your product roadmap

Revibu automations let you turn every new review into a fully automated workflow: triage, tickets, alerts, and replies - without manual work.

An automation is a rule that runs whenever a new review arrives (or during a backfill), and follows this logic:

Triggers decide when the rule fires
Filters decide which reviews qualify
Alerts decide who is notified
Actions decide what Revibu does
Scope defines which reviews are eligible to be processed

How Revibu automations are structured

In the app, each automation is built from the same blocks:

1) Triggers (optional)

Triggers are conditions that activate the automation.

Revibu supports two trigger types:

Score trigger (rating-based)
AI trigger (review classification)

You can enable one, both, or none.
If you enable none, the automation listens to all new reviews.

Triggers section

Score trigger (rating)

Use when you want to target reviews by star rating.

You choose:

an operator (e.g. less than or equal to)
a rating value from 1 to 5

Supported operators:

Operator	Meaning	Example
`is`	rating equals value	`is 5`
`is_not`	rating is not value	`is_not 1`
`lt`	rating < value	`lt 3`
`lte`	rating ≤ value	`lte 2`
`gt`	rating > value	`gt 3`
`gte`	rating ≥ value	`gte 4`

Example
Trigger on all negative reviews:

score.enabled = true
operator = lte
value = 2

AI trigger (classification)

Use when you want to target reviews by Revibu's AI triage.

AI types:

BUG
FEATURE
IMPROVEMENT
CHORE

You pick one or more types.
The automation triggers when a review matches any selected type.

Example
Send feature requests to your backlog:

enable AI trigger
select FEATURE

AI triggers rely on Revibu's real-time classification.
If AI confidence is low, the review won't match unless you broaden filters.

2) Filters (optional)

Filters refine the triggers.
A review must pass all filters to qualify (AND logic).

Revibu currently supports three filter types:

Keyword filter
Language filter
Minimum word count filter

Filters section

Keyword filter

Use when you want to include/exclude reviews containing certain words.

You choose:

operator: contains or not_contains
one or more keywords

Example
Only keep reviews mentioning crashes:

operator = contains
keywords = ["crash", "freeze", "bug"]

Keyword filter

Language filter

Use when you want automations per locale.

You choose:

operator: is or is_not
language code (2 letters): en, fr, es, …

Example Target only French reviews:

operator = is
language = fr

Language filter

Minimum word count filter

Use when you want to ignore super-short reviews.

You choose:

minWordCount (integer)

Example Ignore “Nice app” type noise:

minWordCount = 4

Min word count filter

3) Alerts (optional)

Alerts notify your team when a review qualifies.

Supported providers:

Slack
Microsoft Teams
Discord

For each alert you can set:

Webhook URL (required)
optional channel / mentions
custom message template

Default template:

New review from {{authorName}} ({{rating}}★): {{reviewText}}

Alerts section

Slack alert

You need a Slack Incoming Webhook.

Create a webhook in Slack
https://api.slack.com/messaging/webhooks
Copy the webhook URL
Paste into Revibu

Optional:

override channel
custom message

Slack alert config

Teams alert

You need a Microsoft Teams Incoming Webhook.

Create a webhook in Teams
https://learn.microsoft.com/.../add-incoming-webhook
Copy the webhook URL
Paste into Revibu

Optional:

mention everyone
custom message

Teams alert config

Discord alert

You need a Discord channel webhook.

Create a webhook
https://support.discord.com/.../Intro-to-Webhooks
Copy the webhook URL
Paste into Revibu

Optional:

mention everyone
mention specific user IDs
custom message

Discord alert config

4) Actions (required)

Actions are what Revibu does when a review matches triggers + filters.

You must add at least one action.

Two action types:

Reply
Create issue

Actions section

Reply action

Use when you want Revibu to prepare or publish replies.

You choose:

mode: manual or ai
optional delay
optional safety guardrails

Manual mode

Revibu uses a template
You can review before publishing (depending on settings)

AI mode

Revibu generates a reply using:
- instruction (what to say)
- tone (how it sounds)
It follows your brand voice settings

Other options:

delayMinutes: wait before replying (0 → 1440)
forbiddenKeywords: block unsafe topics
template required if manual mode

Reply action

Example Auto-reply to 5★ reviews in your tone:

mode: ai
tone: “friendly, grateful, short”
delay: 0

Issue action (tickets)

Use when you want to push reviews into your product tool.

You can enable one or more:

Jira
Notion
Linear

Options include:

priority: LOW / MEDIUM / HIGH / CRITICAL
labels
optional note

Issue action

Example Create a Jira bug ticket from negative crash reviews:

addToJira: true
priority: HIGH
labels: ["android", "crash"]

Make sure Issue Sync is connected first (Settings → Issue Sync).

5) Scope

Scope defines which reviews are eligible to be processed.

Revibu uses:

sinceDate: only reviews created after this date
onlyUnreplied: only reviews that don't already have a reply

Defaults:

last 7 days
unreplied only

Scope section

Why it matters Scope prevents automations from:

replying twice,
reprocessing old history unintentionally.

Building your first automation (recommended path)

Step 1 - Create automation

Go to Automations → New automation.

Give it:

a name
(optional) description
toggle Active on/off

Create automation

Step 2 - Choose a trigger

Start simple:

for negative reviews: Score ≤ 2
for praise: Score ≥ 4
for bugs/features: AI trigger

Step 3 - Add filters if needed

Filters should be used to avoid false positives.

Example filters:

require keywords like “crash”
only English reviews
minimum 4 words

Step 4 - Add an alert (optional)

Alert the right team channel.

Example:

dev channel for bugs
product channel for features
support channel for angry reviews

Step 5 - Add actions

Pick at least one:

Reply (manual or AI)
Create ticket (Jira/Notion/Linear)

Step 6 - Set scope

Default scope is good for most cases.

If you want to process more history, move sinceDate back.

Step 7 - Save and test

Before going live:

Save
Preview matched reviews (if preview mode is available)
Activate

Real examples you can copy

1) Critical bug triage

Goal: catch 1-2★ crash reviews, alert devs, create a bug ticket.

Trigger: score ≤ 2
Filter: keywords contains ["crash", "freeze", "bug"]
Alert: Slack dev channel
Action: create Jira ticket (priority HIGH)
Optional action: AI reply with apology

2) Feature requests → backlog

Goal: every FEATURE review becomes a ticket + product alert.

Trigger: AI types [FEATURE]
Filter: score ≥ 3 (optional)
Alert: Teams product channel
Action: create Linear issue (labels ["feature-request"])

3) Auto-reply to positive reviews

Goal: reply fast to 4-5★ with your brand voice.

Trigger: score ≥ 4
Filters: onlyUnreplied (scope default)
Action: AI reply, tone “short + grateful”

Best practices

Start with one automation per use-case
Keep triggers broad, filters precise
Use AI triggers for product triage
Use a delay for replies if you want a human review window
Re-check templates every few weeks

Next steps

Connect Issue Sync (Jira / Linear / Notion)
Connect Alerts (Slack / Teams / Discord)
Explore Automation Templates