Stripe

Your Stripe account, in two nodes on one connected credential. The action runs 44 operations — customers, payments and refunds, subscriptions and invoices, products and prices, Payment Links and Checkout — and can also be an AI toolkit. The trigger fires a flow when a payment succeeds or fails, a refund or a dispute happens, a subscription or an invoice changes, or a Checkout completes.

Setup

Connect Stripe under Settings → Credentials, or straight from the node: name the credential, pick Test mode or Live mode, and install the HostWebhook app on your Stripe account. Nothing is picked for you — live and test are separate credentials, and each one only sees its own mode's data. Build and test with a test-mode credential; nothing it does moves real money.

The app asks Stripe for exactly what the nodes use: read and write on customers, payments, charges and refunds, subscriptions, invoices, products and prices, Payment Links and Checkout Sessions; read on disputes, payment methods and the balance; and events, for the trigger. Uninstalling the app in Stripe stops both nodes; reconnecting the credential reinstalls it.

Operations

IDs go as Stripe writes them (cus_…, pi_…, in_…) or from the payload ({{payload.object.customer}}). Price is picked from the account's active prices, with a price ID or a template as the alternative. The output keeps Stripe's own field names, so its API reference applies as it is; lists come back as { customers: [...], count, hasMore } and the next node runs once per item.

Changing a subscription's price

Update subscription with a new price or quantity changes the subscription's own line, so the customer keeps paying for one thing. It only works on single-item subscriptions; with more than one line the node stops and says so instead of adding another.

AI toolkit mode

Once the credential is picked, the node asks for a Mode. AI toolkit turns it into 44 tools that an AI Node — or an MCP client, through one of your MCP servers — calls by name: a billing assistant that looks up a customer's payments and invoices, sends a Payment Link or opens a Checkout.

What you control

• Blocked tools. The eleven that move money or can't be undone start blocked. Unblock only what the agent really needs, under Block these tool calls.
• Characters per call sent to the model. 20,000 by default, anything from 1,000 to 200,000.

What goes back to the model

The same response as the operation. Lists return 20 unless the model asks for more, up to 100 — the model decides; a limit set in Single operation doesn't count in toolkit mode. Items that don't fit the characters limit are left out whole, with a notes field saying how many. Arguments are used as written: a {{payload.x}} the model writes is not resolved against the flow.

Testing a tool

{ "operation": "list_stripe_customers", "email": "sam.rivera@example.com" }

The trigger

Pick Stripe as the service on a Trigger node and a Stripe credential. Installing the HostWebhook app already sends the account's events to HostWebhook, so activating changes nothing in Stripe and never expires: the trigger simply starts picking the events you chose, for that account and that mode. To listen to live and test, add one trigger per credential.

What fires it

Event Trigger takes one or more; pick at least one. Changing them while the trigger is active counts from the next event, with nothing to apply.

What the trigger sends downstream

The Stripe event, one level flatter, with the object exactly as Stripe sends it — same field names, amounts in the smallest unit. On *.updated events, previousAttributes holds what changed:

{
  "id": "evt_1QZ…",
  "type": "invoice.paid",
  "label": "Invoice paid",
  "createdAt": "2026-10-08T17:02:11.000Z",
  "livemode": false,
  "accountId": "acct_1Q…",
  "objectType": "invoice",
  "objectId": "in_1QZ…",
  "object": {
    "id": "in_1QZ…",
    "object": "invoice",
    "number": "ZZ-0001",
    "customer": "cus_Q…",
    "customer_email": "sam.rivera@example.com",
    "status": "paid",
    "amount_paid": 1500,
    "currency": "usd",
    "hosted_invoice_url": "https://invoice.stripe.com/i/…",
    "…": "…"
  },
  "apiVersion": "2024-06-20"
}

Trying it out

The trigger's Test push shows what each event you picked will look like — examples with the exact shape this trigger dispatches, so you can write {{payload.object.amount}} in the nodes below it from the start. To see a real one with a test-mode credential, make a test payment in Stripe (card 4242 4242 4242 4242) or run stripe trigger payment_intent.succeeded with the Stripe CLI on that account.

Gotchas

• Live and test don't mix. A test-mode credential can't see live customers or prices, and the other way round — IDs from one mode don't exist in the other.
• Confirming a payment needs a saved payment method. With Confirm now, the node charges pm_… right away, without the customer present; without it, the payment waits for your checkout to confirm it.
• A 429 is retried once, after the wait Stripe asks for (up to 10 s), with the same idempotency key.
• Declined cards come back as the node's error with Stripe's reason, like (insufficient_funds), so the flow can branch on failure.
• Uninstalling the app stops the trigger. It turns off and says why; reconnect the credential and activate it again.