Stripe
The Stripe integration gives your pipelines a read-only view 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 — amount collected over a period, MRR, new subscriptions, cancellations, active customers.
- Feed a leadership agent — a CFO IA 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)
- Administration → Integrations → Stripe → Add an account.
- Enter your Stripe secret key (
sk_live_…orsk_test_…). - The key is encrypted at rest and is never re-exposed — the admin panel only shows key configured: yes.
Multi-account. An organization can connect several Stripe accounts (e.g. two legal entities). One account is marked as the default; nodes and tools can target a specific account via an account parameter.
The stripe_report node
Place a stripe_report node in a pipeline to fetch a snapshot of your activity (volume, MRR, new / canceled / active subscriptions). Its output is published into the context and consumable by a downstream agent, which rephrases it in plain language.
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.
Payment links
An agent can generate a Stripe Checkout payment link and then verify whether the payment has been received. 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 reading your own account.
- Stripe objects are handled robustly regardless of the SDK version.