Esta página todavía está en inglés. La traducción al español está en progreso.
Stripe Integration
Stripe integration provides financial metrics to the @flux agent: MRR tracking, charge monitoring, churn detection, and subscription analytics.Setup
1. Get Your API Key
- Go to dashboard.stripe.com
- Navigate to Developers > API Keys
- Copy your Secret key (starts with
sk_live_orsk_test_)
sk_test_) during setup to verify the integration without affecting live data.
2. Configure .env
nano .env) or the dashboard .env editor.
3. Test the Connection
What It Tracks
The Stripe integration provides data for these metrics:Skills That Use Stripe
Automated Routines
Stripe + Omie
For a complete financial picture, EvoNexus combines Stripe data (revenue, subscriptions) with Omie ERP data (expenses, invoices, accounts payable/receivable). Thefin-daily-pulse skill queries both sources.
If you only use Stripe (no Omie), the financial routines still work — they show revenue metrics and skip the expense/ERP sections.
Using the int-stripe Skill Directly
You can query Stripe interactively through Claude Code:int-stripe skill to call the Stripe API and return formatted results. Supported operations:
- List charges, customers, invoices, subscriptions
- Filter by date range, status, amount
- Create and update customers
- Process refunds
- List products and prices
Security Notes
- The secret key has full access to your Stripe account. Use a restricted key if you only need read access (Developers > API Keys > Create restricted key).
- Never commit
.envto version control. The.gitignorealready excludes it. - The dashboard masks the key in the .env editor (displayed as
*****).