Use cases
Use cases: database events your team can act on
Ready-to-copy Rowfire triggers: the SQL, the rule and the destination for alerts, tickets and campaigns from PostgreSQL, MySQL and MariaDB.
Alert sales when an account nears its seat limit
Post to Slack when a PostgreSQL account uses 80% of the seats it pays for, once a month per account, so account managers can start an upgrade conversation.
Celebrate trials that convert to paid
Post to #wins in Slack and update the customer's plan attribute in Braze when a PostgreSQL trial converts to a paid plan. Two actions, one trigger.
Escalate the third declined charge in a month
Alert the account owner's team when an account's card fails for the third time in a calendar month in PostgreSQL. A window function makes the count.
Flag large refunds to finance in Slack
Post refunds over a threshold from your MySQL orders database to a finance channel in Slack, once per refund, with the order and the reason.
Follow up on low satisfaction ratings
Open a Zendesk follow-up when a customer rates a support conversation badly in your MySQL help desk, once per ticket, before they churn quietly.
Follow up with every NPS detractor
Open one Zendesk ticket per unhappy account a month and share detractor comments in Slack, from NPS responses in PostgreSQL. SQL and cadences included.
Post new Enterprise sign-ups to Slack
Tell #sales the moment an Enterprise account signs up in PostgreSQL, once per account, with internal QA tenants filtered out. Trigger SQL and backtest included.
Notify customers at 90% of their quota
Send a Braze event when a customer's usage in PostgreSQL passes 90% of their plan quota, at most once a month, so a push or email campaign can warn them.
Recover abandoned carts from MariaDB
Start a Braze cart-recovery campaign four hours after a cart in MariaDB stops changing without a checkout. One event per cart, no tracking code.
Revoke access when a subscription lapses
Call your own API to revoke access when a subscription ends in PostgreSQL, once per subscription. Watch the requests in shadow mode before it goes live.
Send flagged orders to a fraud service
Post high-risk orders from MySQL to your fraud-review service's API, once per order, without changing checkout code. Trigger SQL and request shape included.
Share cancellation reasons with the team
Post every cancellation and its stated reason to Slack, and open a Zendesk ticket for paying accounts, from subscriptions in PostgreSQL.
Thank customers on every fifth order
Send a Braze event on a customer's first order and every fifth one after it, from PostgreSQL, with an every-nth cadence instead of counting code.
Ticket orders paid but not shipped in 24 hours
Open a Zendesk ticket when an order in MySQL was paid 24 hours ago and still isn't fulfilled. The clock is computed in the query, so the absence fires.
Welcome users the first time they activate
Send a Braze event the first time a user activates in PostgreSQL, exactly once per user, so the onboarding campaign starts on what they actually did.
Win back users after 14 days without a login
Start a Braze win-back campaign when a user hasn't logged in for 14 days. A PostgreSQL trigger with a computed clock fires on the absence itself.
Escalate urgent tickets nobody has answered
Post to #support in Slack when an urgent ticket in your MySQL support desk has no first response. Spam excluded, one alert per ticket. SQL included.
Rescue trials that never activated
Open a Zendesk ticket for customer success three days before a trial ends, if the account never activated. A PostgreSQL trigger with a computed clock.
Slack and Zendesk alerts when a card is declined
Tell #billing and open one Zendesk ticket per account when a charge fails in PostgreSQL, without a ticket for every retry. Trigger SQL and rules included.