How to Automate Stripe and Supabase Reporting in Slack

Stop switching between dashboards. Get your revenue, user, and ops data delivered to Slack — on a schedule or on demand.

TL;DR

• Connect Stripe and Supabase to Slack through alicehasnoidea
• Get scheduled reports (daily MRR, weekly churn, signups) in any channel
• Run slash commands like /alice mrr or /alice users --plan=pro for instant data
• Combine sources: Stripe revenue + Supabase user data in one query
• One-click actions: tag customers, send DMs, fire webhooks — without leaving Slack
• Free tier available, setup takes under 5 minutes

The problem

It's Monday morning. Your ops lead opens Stripe, exports last month's MRR into a CSV, pastes it into a spreadsheet, takes a screenshot, and drops it in the #ops Slack channel. Then they open Supabase, run a query for new signups, format the results, and post those in a thread. By the time they're done, it's been 45 minutes — and someone still asks "what's the churn rate?"

This happens at every Series A startup with a small ops team. The data lives in two places, and pulling it together is a manual process:

• Revenue numbers — log into Stripe, export CSV, paste into Slack. Every time someone asks.
• User metrics — query Supabase, format results, share in a thread. Repeat for each question.
• Churn signals — cross-reference payment failures with login activity across two dashboards. No one does this regularly because it takes too long.
• Ad-hoc requests — "Can someone pull the MRR?" messages in Slack that interrupt deep work. The person who knows how to pull the numbers becomes a bottleneck.

Most teams end up with a patchwork of Zapier automations, cron scripts, or one person who "knows how to pull the numbers." When that person goes on vacation, the numbers stop. When the Zapier zap breaks, nobody notices for a week.

What alicehasnoidea does

alicehasnoidea connects your Stripe and Supabase accounts to Slack. It gives your team three things: scheduled reports that post automatically, slash commands for on-demand data, and combined queries that join data across both sources.

Scheduled reports

Automated messages delivered to a Slack channel on a schedule you set. You pick the metric, the frequency, the time, and the channel. The report runs automatically and posts formatted results — no manual work, no forgotten updates.

Examples:

• Daily MRR summary — from Stripe, every weekday at 9am. Shows current MRR, change from yesterday, and trend direction.
• Weekly new signups — from Supabase, Monday at 8am. Lists new users with signup date, plan, and source.
• Failed payments this week — from Stripe, daily at 10am. Shows which customers have failing payments and how many retry attempts have been made.
• Trial users not logged in 7+ days — from Stripe + Supabase, daily. Combines trial subscription status with last login timestamp to identify at-risk trials before they expire.

Each report runs the query automatically and posts formatted results to the channel you choose. Your team sees the numbers without anyone having to pull them.

Slash commands

On-demand queries from any Slack channel. Type the command, get the answer in seconds. No need to open another tab, log into a dashboard, or ask someone else to look it up.

• /alice mrr — current monthly recurring revenue from Stripe
• /alice churn-risk — customers with failed payments and no recent logins
• /alice users --plan=pro — list of users on the Pro plan from Supabase
• /alice revenue --period=this-month — revenue breakdown for the current month
• /alice signups --days=7 — new signups from the last 7 days
• /alice customers --status=past_due — customers with past-due invoices

Results come back formatted as summaries with key numbers highlighted. For list results, you get sortable rows with the most important fields. Anyone on the Slack workspace can run these — no special permissions needed.

Combined queries

This is where alicehasnoidea differs from simple Stripe-to-Slack integrations. You can join data across Stripe and Supabase in a single command, creating insights that neither source can provide alone:

• churn-risk — payment failed in Stripe + no login in 14 days in Supabase. Neither source tells you this alone. Together, you see exactly which customers are about to leave.
• vip-users — revenue > $500/mo in Stripe + user profile details from Supabase. See your highest-value customers with their usage patterns.
• expansion-ready — on starter plan in Stripe + hitting usage limits in Supabase. These are your best upsell candidates.
• trial-health — trial users from Stripe + feature adoption metrics from Supabase. Know which trials are likely to convert before they expire.

These are called skills. Each skill is a saved query with a name, one or more data sources, optional parameters, an optional schedule, and optional action buttons. You build them once and your whole team can use them.

Data sources

Stripe

Connect your Stripe account with a read-only restricted API key. alicehasnoidea can query:

• Monthly and annual recurring revenue (MRR, ARR)
• Active subscriptions by plan
• Churn rate and churned customers
• Failed payments and dunning status
• Customer lifetime value
• Revenue by period (day, week, month)
• Upcoming renewals
• Refunds and disputes

Supabase

Connect your Supabase project with a read-only database connection string. alicehasnoidea runs queries directly against your Postgres database, so you can pull:

• Any table in your Postgres database
• User signups, activity, last login
• Feature usage and adoption
• Custom application metrics
• Anything you can write a SQL query for

The Supabase connection is especially powerful because your application data is unique to your business. Stripe metrics are standardized — every SaaS tracks MRR. But your Supabase data (feature usage, user behavior, custom events) is what makes combined queries valuable.

Coming soon

• Posthog (product analytics)
• Crisp and Intercom (support tickets)
• Linear (engineering tickets)
• HubSpot (CRM, deals)

How setup works

Step 1 — Install in Slack

Add alicehasnoidea to your Slack workspace. The install uses standard Slack OAuth — you'll see exactly which permissions are requested before confirming. Everyone on the workspace gets access automatically. No invite codes, no per-user setup. If you're in the Slack workspace, you can use alicehasnoidea.

Step 2 — Connect Stripe

Go to Sources, then Add source, then Stripe. Paste your Stripe restricted API key. alicehasnoidea never gets write access to your Stripe account — the key should be read-only.

What to grant: Read access to Customers, Charges, Subscriptions, Invoices, and Balance. That's it. No write permissions, no access to payment methods or sensitive card data. You can create a restricted key in your Stripe dashboard under Developers > API keys > Create restricted key.

Step 3 — Connect Supabase

Go to Sources, then Add source, then Supabase. Enter your Supabase project URL and a read-only database connection string.

Important: Create a dedicated read-only Postgres role for alicehasnoidea. It should only have SELECT permissions on the tables you want to query. alicehasnoidea runs user-defined queries against your database, so a read-only role prevents any accidental writes. Your Supabase dashboard has connection strings under Settings > Database.

Step 4 — Create your first skill

A skill is a saved query that your team can run from Slack. You have three ways to create one:

• Pick a template — 22 pre-built Stripe skills (MRR, churn, failed payments, etc.) ready to use in one click. These cover the most common metrics.
• Write your own — custom SQL for Supabase queries, or configure Stripe metric parameters. Full control over what data you pull and how it's formatted.
• Use AI assist — describe what you want in plain English ("show me users who signed up this week but haven't logged in"), and alicehasnoidea generates the query for you.

Each skill has a name (what you type after /alice), one or more sources (Stripe, Supabase, or both), a query, optional parameters (like --plan=pro or --days=30), an optional schedule, a channel for posting results, and optional action buttons.

Step 5 — Test and activate

Run the skill once with /alice your-skill-name to verify the output. Check that the data looks right and the formatting is clear. If everything checks out, set a schedule (daily at 9am, weekly on Mondays, etc.) and pick the Slack channel where reports should post.

Pre-built skill templates

22 templates for common Stripe queries, ready to install in one click. Each template comes pre-configured with the right Stripe API parameters, sensible defaults, and formatted output. Install one, test it, customize it if needed.

Revenue

• MRR and ARR summary
• Revenue by plan
• Revenue trend (30, 60, 90 days)
• Net revenue (new + expansion - churn - contraction)

Customers

• Active subscribers by plan
• New customers this period
• Customer lifetime value distribution
• Customers by country or region

Churn and retention

• Churn rate (monthly)
• Churned customers list
• At-risk accounts (payment failed)
• Upcoming renewals

Payments

• Failed payments
• Refunds and disputes
• Outstanding invoices
• Payment method distribution

Each template can be customized after install — change parameters, add a schedule, or modify the query. Templates are a starting point, not a constraint.

Actions

Query results can include action buttons. When you see a list of at-risk customers or failed payments, you can act on them directly from Slack — one click, no context switching.

• Tag in Stripe — add a tag or note to a customer's metadata. Useful for marking accounts as "contacted" or "at risk" so your team can track follow-ups.
• Send Slack DM — message a teammate about a specific result. Click the button, pick the person, and the DM includes the relevant data from the query result.
• Fire webhook — POST to a URL you configure. Use this to trigger automations in other tools — create a Notion task, log to a spreadsheet, or kick off a custom workflow.

alicehasnoidea only supports safe, non-destructive actions. No cancellations, no deletions, no refunds. Actions are about tagging, notifying, and routing — never about changing billing state.

How it compares

alicehasnoidea vs. Zapier

Zapier can send Stripe notifications to Slack, but each trigger is a separate zap with its own cost. There's no way to combine data across sources in a single zap. No slash commands for on-demand queries. No action buttons on results. A typical setup with 5-10 Stripe-to-Slack zaps costs $100+/mo on Zapier's Team plan, and you still can't run ad-hoc queries or join Stripe data with your database.

alicehasnoidea vs. a custom Slack bot

You can absolutely build this yourself. Connect to the Stripe API, write SQL queries, format results for Slack Block Kit, handle slash command routing, build a scheduler, manage credentials securely, handle rate limits. Most teams that go this route spend 2-4 weeks of engineering time on the initial build, then ongoing maintenance as APIs change and edge cases appear. alicehasnoidea gives you the same result with pre-built templates and a visual skill editor.

alicehasnoidea vs. Datadog / Grafana

Datadog and Grafana are infrastructure monitoring tools. They're excellent at tracking server health, latency, and error rates, but they don't integrate with Stripe or Supabase out of the box. No subscription metrics, no customer-level queries, no Slack slash commands. They solve a different problem — infrastructure observability, not business ops.

What makes alicehasnoidea different: combined queries across Stripe + Supabase, slash commands for on-demand data, 22 pre-built templates, scheduled reports, and one-click actions — all in Slack. It's purpose-built for ops teams at startups, not a general-purpose monitoring tool.

Pricing

Free — $0/mo. 1 data source, 50 queries/month, 10 skills, 1 weekly scheduled report, 3 monitors, no actions, 7-day history. Good for trying it out with Stripe or Supabase (not both).

Pro — $39/mo ($32.50/mo annual). 3 data sources, 2,000 queries/month, 50 skills, unlimited scheduled reports, 25 monitors, actions enabled, 30-day history. This is where combined queries unlock — connect both Stripe and Supabase.

Business — $99/mo ($82.50/mo annual). Unlimited data sources, 10,000 queries/month, unlimited skills, unlimited scheduled reports, unlimited monitors, actions enabled, 90-day history. For teams that run everything through Slack.

Practical tips

Start with one scheduled report. Pick the metric your team asks about most — usually MRR or new signups. Set it to post daily in your #ops or #revenue channel. Once people see consistent, automated numbers every morning, they'll ask for more. This is the fastest way to demonstrate value.

Use read-only credentials. Both Stripe and Supabase connections should be read-only. For Stripe, create a restricted key with only read permissions. For Supabase, create a dedicated Postgres role with SELECT-only access. alicehasnoidea enforces read-only on its end, but defense in depth means restricting at the source too.

Combined queries are the unlock. A Stripe-only MRR report is useful but not unique — you can get that from Stripe's dashboard. A report that shows MRR + which users haven't logged in this week + which payments failed — that's the insight that actually changes behavior. Start with a simple combined query like churn-risk and build from there.

Name skills clearly. Your whole team will use these as slash commands, so names matter. /alice mrr is better than /alice stripe-monthly-recurring-revenue-summary-v2. Keep names short, lowercase, and descriptive. Use hyphens for multi-word names: /alice churn-risk, /alice trial-health.

Set timezone correctly. Scheduled reports use the timezone you configure in your organization settings. A "daily 9am" report set to UTC when your team is in EST means messages at 4am. Check your timezone setting before wondering why reports arrive at odd hours.

Security

• Credentials are encrypted at rest using AES-256
• Supabase queries run as read-only — alicehasnoidea cannot write to your database
• Stripe API keys should be restricted to read-only with specific resource access
• No raw data is stored beyond query results (retained per plan: 7, 30, or 90 days)
• Slack workspace = organization boundary — full multi-tenant isolation between workspaces
• All connections use TLS/HTTPS — no plaintext credentials in transit

Get started

1. Go to alicehasnoidea.com

2. Click Start free — connects via your Slack workspace

3. Add your first source (Stripe or Supabase)

4. Pick a template or create a custom skill

5. Run it with /alice your-skill

Free plan includes 1 source, 50 queries/month, and 10 skills. No credit card required.