Skip to main content

Documentation Index

Fetch the complete documentation index at: https://learn.actionist.ai/llms.txt

Use this file to discover all available pages before exploring further.

Stripe is your money plumbing. Use Actionist to query payments, draft invoices, follow up on failed charges, and route finance alerts to the right humans.

​
What you can do

  • Read customers, invoices, charges, subscriptions, refunds.
  • Create customers, invoices, charges, subscriptions, refunds.
  • Subscribe to webhooks for invoice.paid, invoice.payment_failed, customer.subscription.deleted, and dozens more.
  • Issue refunds — gated behind explicit approval, always.

​
Setup

1

Install the Stripe MCP server

Integrations → Discover → Stripe → Install. Authenticate with a restricted key (recommended) or a regular secret key.
2

Use restricted keys for write ops

Stripe lets you scope keys per object type. The Actionist agent doing reads should use a read-only key. A second key with write scopes is bound to the agent that creates invoices — separation of duties.
3

Set up webhook signing

For webhook-triggered workflows, paste Stripe’s signing secret into the Credentials Vault. Actionist verifies every payload before running.

​
Common workflows

  • Failed payment recovery — when invoice.payment_failed fires, an agent looks up the customer’s history, drafts a personalized recovery email, and posts a thread in #finance asking the team to approve.
  • Daily MRR digest — every morning, calculate yesterday’s MRR delta and post it to #metrics.
  • Refund approver — when a support ticket asks for a refund, an agent verifies the original charge, drafts the refund, but waits for an explicit human “approve” reply before issuing.
  • Subscription churn watcher — when a subscription cancels, append a row to a Notion “Churn” database with the customer, plan, MRR impact, and last-touch CRM activity.

​
Limits & gotchas

  • Test vs live mode. Always check the key prefix (sk_test_ vs sk_live_). Don’t mix.
  • Idempotency. All write calls support an Idempotency-Key — Actionist passes one per workflow run to prevent dupes on retry.
  • Refunds and subscription cancellations are non-reversible. Always gate behind approvals.
  • Rate limits are 100 reads/s, 100 writes/s. Generous, but bulk operations should still batch.