Stripe

Payments Secret key Windmill docs

Manage payments, subscriptions, invoices and customers from any Windmill script, flow or app.

Set up in 3 steps

1

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_.

2

Add the resource in Windmill

Open Resources, add a resource of type stripe, and paste the key.

3

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.

Submit a script →

Trigger flows from Stripe

Stripe is not only a destination. These inbound paths are supported today.

New customers (scheduled poll)

The Get recently added customers trigger script polls Stripe and returns the customers created since its last run. To run it, open a flow, add a trigger and choose Scheduled Poll, then pick the trigger script and an interval. Windmill puts the script first in the flow with a loop after it, so the steps you add run once per new item. The cursor is saved per flow: two flows polling the same source each get every item, and test runs keep a cursor of their own.

Resource type

The shape of the credential every script on this page expects.

FieldTypeRequiredWhat it is
tokenstringNo

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.