Manage payments, subscriptions, invoices and customers from any Windmill script, flow or app.
Set up in 3 steps
Copy your secret key
In the Stripe dashboard, open Developers then API keys and reveal the secret key. Use the test key while you build — it starts with sk_test_.
Add the resource in Windmill
Open Resources, add a resource of type stripe, and paste the key.
Run your first script
Fork any script below and read a customer before creating anything. There are hundreds here, so search by the verb you need.
Scripts
Building blocks, if none of the projects above fit. Fork one, run it, or call it as a step inside your own flow.
Get recently added customers
Update a Customer
List Invoices
List Customers
Delete a Customer
Create Usage Record
List Balance History
Create a Refund
Create a Payout
Retrieve Invoice Line Item
Create Invoice Line Item
Create Invoice
Create a Customer
Confirm a Payment Intent
Capture a Payment Intent
Cancel a Payment Intent
Cancel Or Reverse a Payout
Get all active stripe products from your account
Post climate orders order cancel
Get financial connections transactions transaction
Post tax ids
Post financial connections accounts account unsubscribe
Get climate orders order
Post invoices invoice lines line item id
Get climate products product
Get tax registrations id
Post tax registrations id
Post financial connections accounts account subscribe
Get climate suppliers
Post tax registrations
Resource type
The shape of the credential every script on this page expects.
stripe
View raw schema →| Field | Type | Required | What it is |
|---|---|---|---|
| token | string | No |
Questions
Test mode or live mode?
The key decides. A test key only ever touches test data, so keep two resources and switch the one a flow points at.
Can I restrict what the key can do?
Yes. Stripe restricted keys grant per-resource read or write permissions, and work here in place of the secret key.
Is my key stored on the hub?
Never. It lives only in your own Windmill workspace, encrypted at rest.