In n8n, add a Stripe node (or a Stripe Trigger) and create new Stripe credentials. You’ll authenticate with your Stripe account and allow n8n to access the data it needs. Then choose what event you want, like “payment succeeded” or “invoice paid.” Test with Stripe test mode first, honestly—it makes debugging painless. Once the workflow runs correctly, switch to live mode and turn the workflow on.

A lot. You can route new payments to Slack, write charges to Google Sheets, email receipts via Gmail, create or update HubSpot contacts, and open a Notion task for fulfillment. You can also react to failures: notify support, tag a customer, or start a dunning sequence. For subscriptions, trigger onboarding when a trial converts, pause access when a subscription is canceled, and keep your reporting tables consistent.

Yes. You’ll connect n8n to your Stripe workspace to read events and perform actions.

The biggest gotcha is mixing test and live data. Make sure your workflow, keys, and webhooks all match the same mode, or you’ll think “nothing is firing.” Also, Stripe events can arrive more than once, so build in idempotency (for example, store the event ID and skip duplicates). Some actions require the right API permissions, and certain fields depend on how you’ve configured Stripe Checkout, invoices, or subscriptions. When in doubt, start from a template and tweak one step at a time.