Resources · n8n integration

Stripe n8n integrationAutomate Stripe with n8n.

Want to plug Stripe into n8n without writing a line of code? The Stripe node exposes 20 operations (customers, charges, coupons, cards, sources) and the Stripe Trigger reacts to 151 events: payment succeeded, invoice unpaid, subscription cancelled, dispute opened.

Try the STRIPE Integration on n8n See the 20 operations

Verified Trustpilot reviews · AI, automation & growth agency

Why automate

Why automate Stripe with n8n?

Whether you need to react instantly to new charges, sync customer data across your tech stack, or automate coupon creation, this integration covers the full spectrum of Stripe operations. From webhook event monitoring to customer management, charge handling, and balance retrieval—everything you need to streamline your payment workflows is available natively in n8n.

In this guide, you'll discover exactly how to connect Stripe to n8n, explore every available trigger and action in detail, and learn practical ways to leverage this integration for your business.

The Stripe n8n integration gives you access to 5 powerful triggers and 20 comprehensive actions that cover virtually every aspect of payment automation. You can monitor any Stripe event in real-time—from successful charges to subscription updates, customer creation to payout completions—and immediately trigger downstream workflows.

Significant time savings: No more manually checking your Stripe dashboard for new transactions or customer updates. Set up smart rules that automatically process payments, update your CRM, send notifications, or generate invoices the moment something happens in Stripe. What used to require constant monitoring now runs 24/7 on autopilot.

Improved responsiveness: React to payment events in milliseconds. When a charge succeeds, instantly send a confirmation email. When a subscription is canceled, immediately trigger a win-back campaign. When a dispute is opened, alert your support team before the customer even reaches out.

Seamless integration: Connect Stripe to over 400+ applications available in n8n. Sync customer data with HubSpot, log transactions in Google Sheets, send Slack notifications for high-value purchases, create Notion entries for new subscriptions, or update Airtable records with payment status.

Concrete workflow examples:

Automatically create CRM contacts when new Stripe customers are added
Sync successful charges to your accounting software in real-time
Send personalized thank-you emails based on purchase amount
Alert sales teams when enterprise-level subscriptions are created
Generate weekly revenue reports from charge data

Credentials

How to connect Stripe to n8n?

01
Get a Stripe secret key
In the Stripe dashboard (Developers, then API keys), create a secret key (sk_ prefix) and name it "n8n". Start in test mode: the sk_test_ key is revealed on the same screen. Publishable keys (pk_) will not work.
02
Create the credential in n8n
In n8n, open Credentials, pick "Stripe API" and paste the key into Secret Key. One credential per mode (test, live) keeps your trials away from real customers.
03
Add the node and activate the workflow
Search "Stripe" in the nodes panel. The Stripe node calls the API, the Stripe Trigger listens to webhooks. When you publish the workflow, n8n creates the webhook endpoint on your Stripe account itself. Then grab its signing secret (whsec_, under Workbench then Webhooks) and paste it into Signature Secret: without it, anyone who knows the URL can send you forged events.

Triggers

Stripe triggers available in n8n

Stripe Trigger is the node that starts a workflow when something happens in Stripe. It listens to 151 events, listed below by family. Pick one or several, activate the workflow: n8n registers the webhook on your Stripe account.

What you see in n8n

Every event, by family

FamilyEvents

customer.*17

customer.created
customer.deleted
customer.updated
customer.discount.created
customer.discount.deleted
customer.discount.updated
customer.source.created
customer.source.deleted
customer.source.expiring
customer.source.updated
customer.subscription.created
customer.subscription.deleted
customer.subscription.trial_will_end
customer.subscription.updated
customer.tax_id.created
customer.tax_id.deleted
customer.tax_id.updated

charge.*13

charge.captured
charge.expired
charge.failed
charge.pending
charge.refunded
charge.succeeded
charge.updated
charge.dispute.closed
charge.dispute.created
charge.dispute.funds_reinstated
charge.dispute.funds_withdrawn
charge.dispute.updated
charge.refund.updated

invoice.*12

invoice.created
invoice.deleted
invoice.finalized
invoice.marked_uncollectible
invoice.paid
invoice.payment_action_required
invoice.payment_failed
invoice.payment_succeeded
invoice.sent
invoice.upcoming
invoice.updated
invoice.voided

source.*7

source.canceled
source.chargeable
source.failed
source.mandate_notification
source.refund_attributes_required
source.transaction.created
source.transaction.updated

subscription_schedule.*7

subscription_schedule.aborted
subscription_schedule.canceled
subscription_schedule.completed
subscription_schedule.created
subscription_schedule.expiring
subscription_schedule.released
subscription_schedule.updated

account.*6

account.updated
account.application.authorized
account.application.deauthorized
account.external_account.created
account.external_account.deleted
account.external_account.updated

payment_intent.*6

payment_intent.amount_capturable_updated
payment_intent.canceled
payment_intent.created
payment_intent.payment_failed
payment_intent.succeeded
payment_intent.requires_action

payout.*5

payout.canceled
payout.created
payout.failed
payout.paid
payout.updated

topup.*5

topup.canceled
topup.created
topup.failed
topup.reversed
topup.succeeded

transfer.*5

transfer.created
transfer.failed
transfer.paid
transfer.reversed
transfer.updated

order.*4

order.created
order.payment_failed
order.payment_succeeded
order.updated

payment_method.*4

payment_method.attached
payment_method.card_automatically_updated
payment_method.detached
payment_method.updated

setup_intent.*4

setup_intent.canceled
setup_intent.created
setup_intent.setup_failed
setup_intent.succeeded

application_fee.*3

application_fee.created
application_fee.refunded
application_fee.refund.updated

coupon.*3

coupon.created
coupon.deleted
coupon.updated

credit_note.*3

credit_note.created
credit_note.updated
credit_note.voided

invoiceitem.*3

invoiceitem.created
invoiceitem.deleted
invoiceitem.updated

issuing_authorization.*3

issuing_authorization.created
issuing_authorization.request
issuing_authorization.updated

person.*3

person.created
person.deleted
person.updated

plan.*3

plan.created
plan.deleted
plan.updated

product.*3

product.created
product.deleted
product.updated

recipient.*3

recipient.created
recipient.deleted
recipient.updated

reporting.*3

reporting.report_run.failed
reporting.report_run.succeeded
reporting.report_type.updated

sku.*3

sku.created
sku.deleted
sku.updated

issuing_card.*2

issuing_card.created
issuing_card.updated

issuing_cardholder.*2

issuing_cardholder.created
issuing_cardholder.updated

issuing_dispute.*2

issuing_dispute.created
issuing_dispute.updated

issuing_settlement.*2

issuing_settlement.created
issuing_settlement.updated

issuing_transaction.*2

issuing_transaction.created
issuing_transaction.updated

radar.*2

radar.early_fraud_warning.created
radar.early_fraud_warning.updated

review.*2

review.closed
review.opened

tax_rate.*2

tax_rate.created
tax_rate.updated

balance.*1

balance.available

capability.*1

capability.updated

checkout.*1

checkout.session.completed

file.*1

file.created

invoice_payment.*1

invoice_payment.paid

order_return.*1

order_return.created

sigma.*1

sigma.scheduled_query_run.created

The trigger also accepts * (any event). Handy for logging, dangerous in production.

Configuration notes

Stripe Webhook Trigger

The Stripe Webhook Trigger is the foundation of real-time payment automation in n8n. This trigger automatically monitors your Stripe account and fires your workflow the instant any selected event occurs—whether it's a successful charge, a new customer signup, or a subscription change.

What makes this trigger exceptionally powerful is its comprehensive event coverage. You can listen to virtually any Stripe activity: customer lifecycle events (created, updated, deleted), payment events (charges succeeded, failed, refunded), subscription changes, invoice activities, dispute notifications, and much more.

Configuration parameters:

Events: This is a required multi-select field where you choose which Stripe events will trigger your workflow. You can select from hundreds of predefined webhook events including customer events (Customer Created, Customer Updated, Customer Source.expiring), charge events (Charge Succeeded, Charge Failed, Charge Refunded), coupon operations, credit note actions, checkout completions, and dispute notifications. Each selected event appears as a tag that can be individually removed.

Typical use cases:

Trigger a welcome email sequence when a new customer is created in Stripe
Update your CRM record immediately when a charge succeeds
Alert your finance team via Slack when a dispute is opened
Sync coupon usage to your analytics platform when discounts are applied
Archive customer data when accounts are deleted

When to use it: Use this trigger whenever you need to react to events happening in your Stripe account in real-time. It's perfect for building responsive payment workflows that keep your entire tech stack in sync.

Stripe Trigger: Listen for Events

This trigger provides a streamlined interface for monitoring specific Stripe events and initiating automated workflows. It's designed to listen continuously for activities within your Stripe account and kick off your n8n workflow the moment a matching event is detected.

The trigger excels at monitoring complex event patterns across multiple Stripe objects simultaneously. Whether you're tracking issuing card updates, invoice lifecycle changes, or customer subscription modifications, you can configure all your monitoring needs in a single node.

Configuration parameters:

Events: A required multi-select parameter that lets you specify exactly which Stripe events should activate your workflow. Select from a comprehensive list including Issuing Card events (created, updated), Issuing Authorization events (created, updated, request), Invoice events (created, updated, voided, sent, payment_succeeded, payment_failed, finalized), and Customer Subscription events (created, updated, deleted, trial_will_end). Each event type appears as a distinct tag with the ability to deselect individually.

Typical use cases:

Monitor subscription trials ending soon and trigger retention campaigns
Track invoice payment failures and initiate dunning workflows
Sync issuing card updates to your internal card management system
Alert operations when authorization requests need review
Update customer profiles when subscription plans change

When to use it: This trigger is ideal when you need granular control over invoice, subscription, and issuing-related events. It's particularly valuable for SaaS businesses managing recurring billing or companies using Stripe Issuing for corporate cards.

Stripe Trigger (Webhook)

This comprehensive webhook trigger captures the broadest range of Stripe events, making it the go-to choice for organizations that need to monitor account-level activities, payouts, payment methods, payment intents, orders, and issuing transactions all in one place.

The trigger is particularly powerful for businesses using Stripe's advanced features like Connect (for marketplaces), Issuing (for corporate cards), or complex order management workflows. It covers event categories that other configurations might miss.

Configuration parameters:

Events: A required multi-select dropdown where you define every event type that should trigger your workflow. Available events span across Person management (Created, Updated, Deleted), Payout lifecycle (Created, Paid, Failed, Canceled), Payment Method changes (attached, detached, updated, card_automatically_updated), Payment Intent progress (created, succeeded, failed, canceled, requires_action, amount_capturable_updated), Order processing (Created, Updated, payment_succeeded, payment_failed, Return.created), and Issuing operations (Transaction, Settlement, Dispute, and Cardholder events).

Typical use cases:

Track payout statuses and update your cash flow forecasting tools
Monitor payment intent failures and trigger alternative payment collection
Sync order completions to your fulfillment or inventory system
Alert compliance teams when cardholder information is updated
Log all payment method changes for audit purposes

When to use it: Choose this trigger when your automation needs extend beyond basic customer and charge events. It's essential for marketplaces using Stripe Connect, companies managing corporate card programs, or businesses with sophisticated order management requirements.

Stripe Trigger

The Stripe Trigger provides extensive coverage of subscription schedules, source transactions, product catalog changes, and reporting events. It's designed for businesses that need to automate workflows around their product offerings, scheduled subscription changes, and internal reporting processes.

This trigger is particularly valuable for e-commerce businesses managing product catalogs, subscription boxes with scheduled delivery changes, or finance teams that rely on Stripe's Sigma reporting capabilities.

Configuration parameters:

Events: A required multi-select input field for specifying which Stripe events activate your workflow. Notable event categories include Subscription Schedule lifecycle (created, updated, completed, canceled, expiring, released), Source Transaction events (created, updated), Source status changes (failed, mandate_notification), SKU and Product management (Created, Updated, Deleted), Sigma reporting (scheduled_query_run.created), Setup Intent completion (succeeded, failed), Review actions (opened, closed), Recipient changes, Radar fraud warnings, and Plan management (Created, Updated).

Typical use cases:

Sync product catalog changes to your e-commerce platform or POS system
Trigger fulfillment workflows when subscription schedules complete
Alert merchandising teams when SKU inventory changes are detected
Automate report distribution when Sigma queries complete
Monitor setup intents for onboarding completion tracking

When to use it: This trigger is perfect for product-focused automation. Use it when you need to keep your catalog synchronized across platforms, manage scheduled subscription changes, or automate workflows based on Stripe's reporting features.

Webhook URLs

This trigger configuration provides a complete view of webhook management, combining Stripe account credential selection with comprehensive event monitoring. It's particularly useful when setting up new integrations or managing multiple Stripe accounts within your n8n workflows.

The interface clearly displays the webhook connection status and allows you to configure events across account-level activities, application fees, balance changes, transfers, top-ups, tax rates, and subscription schedules.

Configuration parameters:

Credential to connect with: A required dropdown field to select your Stripe account connection. This credential enables n8n to authenticate and interact with your specific Stripe account. You can manage multiple Stripe accounts and select the appropriate one for each workflow.

Events: A required multi-select input for defining triggering events. Available categories include Account events (Updated, Application authorized/deauthorized, External_account changes), Application Fee tracking (created, refunded, refund.updated), Balance availability notifications, Transfer lifecycle (Created, Updated, Paid, Reversed, Failed), Top-up status changes (Succeeded, Reversed, Failed, Created, Canceled), Tax Rate modifications, and Subscription Schedule events (created, updated, released, expiring).

Typical use cases:

Monitor account-level changes for compliance and security alerts
Track application fees and refunds for marketplace revenue reconciliation
Receive instant notifications when your Stripe balance becomes available
Automate transfer tracking and reconciliation with your banking systems
Sync tax rate updates to your invoicing and accounting software

When to use it: Use this trigger when you need visibility into your Stripe account's infrastructure events—balance changes, transfers, tax configurations, and connected account activities. It's essential for businesses operating marketplaces or managing multiple connected accounts.

Actions

Stripe actions available in n8n

The Stripe node exposes 20 operations across 8 resources. For each one: the node as you configure it in n8n, the required fields, and our field notes.

Resources × operations matrix
Resource	Create	Get	Get Many	Update	Delete	Add	Remove
Balance		✓
Charge	✓	✓	✓	✓
Coupon	✓		✓
Customer	✓	✓	✓	✓	✓
Customer Card		✓				✓	✓
Meter Event	✓
Source	✓	✓			✓
Token	✓

Balance

1 operation

Get a balance

balance.get

What you see in n8n

Notes & use cases

Retrieve your Stripe account's current balance, including available and pending funds across all currencies.

Key parameters:

Resource: Set to "Balance"
Operation: Set to "Get"

Key parameters:

Charge ID: A required text field for the charge to update
Update Fields: A dynamic section for specifying fields to modify

Use cases: Add order IDs to charges, update descriptions for reporting, or add fraud indicators after review.

Coupon

2 operations

Create a coupon

coupon.create

What you see in n8n

Notes & use cases

Generate new discount coupons in Stripe with flexible configuration for percentage or fixed-amount discounts, redemption limits, and duration.

Key parameters:

Apply: A required dropdown defining redemption frequency (Once, Forever, Repeating)
Discount Type: A required dropdown (Percent or Amount)
Percent Off: A required text field when using percentage discount

Use cases: Create promotional campaigns, generate referral discounts, set up loyalty rewards, or configure partner discount codes.

Get many coupons

coupon.getAll

What you see in n8n

Notes & use cases

Retrieve multiple coupon records from your Stripe account for reporting, synchronization, or validation purposes.

Key parameters:

Return All: A toggle to fetch every coupon
Limit: A number field for maximum results (default: 50)

Key parameters:

Customer ID: A required text field identifying the customer to update
Update Fields: A dynamic section where you add specific fields to modify (name, email, address, metadata, etc.)

Key parameters:

Customer ID: A required text field for the customer's unique identifier
Card ID: A required text field for the specific card to remove

Use cases: Allow customers to manage their saved cards, remove expired payment methods, or clean up duplicate card entries.

Meter Event

1 operation

Create a meter event

meterEvent.create

What you see in n8n

Notes & use cases

Record usage events for metered billing products, enabling consumption-based pricing models. This action is essential for SaaS businesses, API providers, or any service that charges based on usage.

Key parameters:

Event Name: A required text field defining the meter event type
Customer ID: A required text field identifying the customer whose usage is being recorded
Value: A required numeric field representing the usage quantity (defaults to 1)
Additional Fields: Optional key-value pairs for extended metadata

Key parameters:

Resource: Set to "Source" to interact with payment sources
Operation: Set to "Get" to retrieve source information
Source ID: A required text field where you enter the unique source identifier (starts with src_)

Use cases: Verify source status before charging, display saved payment method details to customers, or audit payment sources associated with your accounts.

Token

1 operation

Create a token

token.create

What you see in n8n

Notes & use cases

This action generates a secure card token from raw card details, which can then be used to create charges or save payment methods to customers. It's the standard approach for handling card data securely while minimizing PCI compliance scope.

Key parameters:

Type: A required dropdown to specify the token type—select "Card Token" for credit/debit card tokenization
Card Number: A required text field for the full card number (e.g., 4242424242424242 for testing)
CVC: A required text field for the card's security code
Expiration Month: A required text field (e.g., "10" for October)
Expiration Year: A required text field (e.g., "2025")

Use cases: Generate tokens for one-time charges, create saved payment methods for customers, or migrate card data from legacy systems to Stripe.

Need help

Need help automating Stripe with n8n?

Our team will get back to you in minutes.

Reply within 1 business hour

FAQ

Frequently asked questions

01Is the Stripe n8n integration free?

Yes, the Stripe integration is included natively in n8n at no additional cost—both in the self-hosted open-source version and n8n Cloud plans. You only pay for your Stripe transaction fees as usual. However, keep in mind that n8n Cloud has execution limits based on your subscription tier, so very high-volume Stripe webhook processing may require a higher plan. For self-hosted n8n, there are no execution limits, making it ideal for businesses processing thousands of Stripe events daily.

02What's the best way to test Stripe workflows in n8n before going live?

The safest approach is to use Stripe's test mode API keys during development. All Stripe accounts come with a parallel test environment where you can simulate transactions, create test customers, and trigger events without processing real payments. In n8n, create a separate credential using your test API key (starts with sk_test_), build and test your workflows thoroughly, then switch to your live credentials when ready for production. You can also use Stripe's webhook testing tools to manually trigger specific events. For more guidance, check the Stripe testing documentation.

03How do I handle high-volume Stripe webhooks without missing events?

n8n automatically manages webhook registration with Stripe, but for high-volume scenarios, consider these best practices: First, only subscribe to the specific events you need rather than selecting all events—this reduces unnecessary processing. Second, ensure your n8n instance has adequate resources (CPU/RAM) if self-hosted, or upgrade your n8n Cloud plan for higher concurrent executions. Third, design your workflows to process quickly and offload heavy operations (like database writes or API calls) to separate workflow branches using n8n's "Execute Workflow" node for better throughput. If you encounter issues, our n8n troubleshooting guide can help you debug common problems.

Hack'celeration Lab

Get our weekly integration tips.

No spam. Unsubscribe anytime.

Get a Stripe secret key

Create the credential in n8n

Add the node and activate the workflow

Every event, by family

Configuration notes

Stripe Webhook Trigger

Stripe Trigger: Listen for Events

Stripe Trigger (Webhook)

Stripe Trigger

Webhook URLs

Need help automating Stripe with n8n?

Get our weekly integration tips.