betool

Documentation

Stripe

Read your Stripe revenue, MRR and subscriptions from a pipeline, and generate payment links.

The Stripe integration gives your pipelines a read of your Stripe activity — and the ability to collect payments via payment links. It's your Stripe account: betool reads your data, does not insert itself into the money flows, and takes no margin.

What you can do with it

  • Track your revenue — revenue collected over a period, MRR, active subscriptions, new subscriptions, cancellations, number of customers.
  • Feed a leadership agent — for example an agent that summarizes the week's finances (see Use cases → CFO IA).
  • Collect payments from an agent — generate a Stripe Checkout payment link and verify its status (see No-code actions).

Connection (BYO)

  1. Settings → Services → Stripe, Accounts tab, then + New account.
  2. Enter a label, the mode (test or live) and your Stripe API key. The admin recommends a read-only restricted key (rk_live_… or rk_test_…) allowed on Balance, Charges, Customers and Subscriptions; to generate payment links, the key must also be able to create Checkout sessions.
  3. The key is stored server-side and never shown again: reads from the admin API only expose a has_secret_key indicator.

Multi-account. An organization can connect several Stripe accounts (e.g. two legal entities). One account is marked as the default; the node targets a specific account via account_id, the tools via their account parameter (label or identifier).

The stripe_report node

Place a stripe_report node in a pipeline to fetch a snapshot of your activity: revenue, mrr, active_subs, new_subs, churned_subs, customers, with currency, period and since. You choose the metrics (none checked = all) and the window (24h, 7d, 30d, 90d, month to date, year to date). Amounts are returned in the currency's main unit (e.g. euros, not cents). Its output is published into the context and consumable by a downstream agent, which rephrases it.

Recommended pattern for a leadership-facing figure: let the node compute the aggregate, and have the agent only write the prose — a deterministic node cannot hallucinate an amount.

Agent tools

  • Read: stripe.report (the same metrics as the node), stripe.list_customers, stripe.get_subscription, stripe.check_payment.
  • Write: stripe.create_payment_link.

An agent can generate a Stripe Checkout payment link (stripe.create_payment_link) and then verify whether the payment has been received (stripe.check_payment). Typical use: have an appointment prepaid before confirming it. Tool details in No-code actions.

Security & costs

  • Reads are scoped to your organization; your Stripe data is never visible to another org.
  • No betool metering on these calls — you are using your own account.