Skip to main content
Verslay
All Use Cases
Finance

Stripe + Slack + Notion Revenue Pulse Channel

Revenue changes broadcast and remembered.

Keeps revenue visibility inside Slack while preserving anomalies and decisions in the team knowledge base.

Best forEcommerceProfessional ServicesSaaS
Agents7 required
Duration5-10 minutes

Combines payment data, team communication, and knowledge capture so revenue changes are broadcast and retained for review.

How it runs

Multi-agent orchestration — here's the flow, step by step.

01

Call verslay_recall to retrieve prior revenue pulse baselines, the Notion knowledge base page ID for revenue tracking, and the Slack channel ID for pulse delivery from memory. Connect to Stripe to pull the current period's MRR movements (new, expansion, contraction, churn), gross and net revenue, failed payment count, and refund rate. Produce a Stripe revenue snapshot as Phase 1 output.

payment scanner
02

Consume Phase 1 Stripe snapshot. Calculate net revenue retention, MRR growth rate, churn percentage, and 30-day revenue run-rate forecast. Identify top 3 revenue-driving customers and any customers showing sudden contraction signals. Produce a revenue analysis summary for Phase 3.

revenue analyst
02

In parallel with revenue-analyst, call verslay_news_headlines to pull sector news that may contextualize this period's revenue movements. Call verslay_news_search targeting the company's industry and 'SaaS revenue pulse benchmarks' for KPI comparison data. Call verslay_web_search for recent industry MRR growth rate reports. Produce an industry context package for Phase 3.

web researcher
03

Consume Phase 2 revenue analysis and Phase 2 industry context. Build a revenue pulse scorecard: all KPIs vs prior period vs benchmark. Call verslay_chart_create to generate an MRR waterfall chart and a revenue-trend sparkline for the trailing 12 weeks. Produce an enriched pulse package for Phase 4.

data analyst
04

Consume Phase 3 pulse package. Update the designated Notion revenue tracking page with the current period's KPIs, MRR waterfall, benchmark comparison, and top insights. Append this period's entry to the revenue history log in Notion so the knowledge base remains current. Confirm Notion update completion.

notion knowledge base operator
04

Consume Phase 3 pulse package and Phase 4 Notion page update confirmation. Post a formatted revenue pulse message to the designated Slack channel: headline KPIs (MRR, churn, NRR), week-over-week deltas with emoji indicators (↑↓), top mover highlights, link to the updated Notion page, and a 1-sentence industry context note from Phase 2. Confirm Slack delivery.

slack channel operations agent
05

Consume Phase 3 pulse package, Phase 4 Notion update confirmation, and Phase 4 Slack delivery confirmation. Write a brief pulse summary confirming all delivery channels, noting any anomalies flagged, and providing the forward revenue run-rate. Call verslay_memorize to store the current period's MRR, churn, NRR, and run-rate as the new baseline for the next pulse run. Return the pulse summary as the final agent response.

executive briefing writer

Required Agents

7
  • payment-scanner
  • revenue-analyst
  • web-researcher
  • data-analyst
  • notion-knowledge-base-operator
  • slack-channel-operations-agent
  • executive-briefing-writer

Connections

Required

stripeslacknotion

What it does

  • Revenue pulse summary
  • Exception detection
  • Slack update draft
  • Notion decision log prep
  • Finance action list

Example prompt

Create a revenue pulse from Stripe, draft a Slack update, and log anomalies or decisions for Notion.

Ready to deploy Stripe + Slack + Notion Revenue Pulse Channel?

Start free. One click, full agent orchestration.

Get Started Free →