STRIPE n8n INTEGRATION: AUTOMATE STRIPE WITH N8N
Looking to automate Stripe with n8n? You're in the right place. The Stripe n8n integration gives you access to 5 triggers and 20 actions to build powerful payment automation workflows without writing a single line of code.
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.
Need help automating Stripe with n8n?
Our team will get back to you in minutes.
Why automate Stripe with n8n?
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
How to connect Stripe to n8n?
! 1 stepHow to connect Stripe to n8n?
- 01
Add the node
The Stripe n8n integration uses API Key authentication, which provides secure and straightforward access to your Stripe account. Here's how to set it up:Basic configuration:Access your Stripe Dashboard: Log into your Stripe account and navigate to Developers → API Keys in the left sidebar.Copy your API Key: For most automation use cases, you'll want to use your Secret Key (starts with sk_live_ for production or sk_test_ for testing). Copy this key securely.Create credentials in n8n: In your n8n workflow, add a Stripe node, click on "Credential to connect with", then select "Create New". Paste your Stripe API key in the designated field.Test the connection: Save your credentials and run a simple test action (like "Get Balance") to confirm everything is working correctly.Configure webhooks (for triggers): When using Stripe triggers, n8n will automatically register the necessary webhooks with your Stripe account—no manual configuration required.
TIP💡 TIP: Always start with your Stripe test mode API keys during development. This lets you simulate transactions without affecting real payments. Once your workflows are tested and validated, switch to production keys. Also, consider creating a dedicated restricted API key with only the permissions your automation needs for enhanced security.- 01
Need help automating Stripe with n8n?
Our team will get back to you in minutes.
Stripe triggers available in n8n
01 Trigger 01Stripe 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.
02 Trigger 02Stripe 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.
03 Trigger 03Stripe 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.
04 Trigger 04Stripe 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.
05 Trigger 05Webhook 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.
Stripe actions available in n8n
01 Action 01Create Token
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.
02 Action 02Get Source
Retrieve detailed information about a specific Stripe source, including its status, type, and associated customer. This action is essential for verifying payment source validity before processing transactions.
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.
03 Action 03Stripe: Source
Manage Stripe sources with full CRUD capabilities, including the ability to delete sources from customer accounts. This action is crucial for maintaining clean payment records and handling customer requests to remove saved payment methods.
Key parameters:
- Operation: Select "Delete" to remove a source
- Customer ID: A required text field for the customer's unique identifier
- Source ID: A required text field for the source to be deleted
Use cases: Remove expired payment methods, handle customer deletion requests (GDPR compliance), or clean up test sources from development environments.
04 Action 04Create Source
Create new payment sources in Stripe, supporting various payment method types including WeChat Pay, Alipay, and other regional payment methods. This action expands your payment acceptance capabilities beyond traditional cards.
Key parameters:
- Type: A required dropdown to select the source type (WeChat, Alipay, etc.)
- Amount: A required number field for the payment amount
- Currency Name or ID: A required field for the three-letter currency code
- Customer ID: An optional field to associate the source with an existing customer
- Additional Fields: Optional parameters for custom metadata or configuration
Use cases: Accept regional payment methods for international customers, create reusable payment sources, or integrate alternative payment options into your checkout flow.
05 Action 05Create Meter Event
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
Use cases: Track API calls for usage-based billing, record storage consumption, log compute hours, or monitor any metered resource for accurate billing.
06 Action 06Remove Customer Card
Delete a specific card from a customer's account. This action handles card removal cleanly, ensuring the customer's saved payment methods stay up to date.
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.
07 Action 07Get Customer Card
Retrieve detailed information about a specific card saved to a customer's account, including card brand, last four digits, expiration date, and billing address.
Key parameters:
- Customer ID: A required text field for the customer's identifier
- Source ID: A required text field for the specific card/source ID
Use cases: Display card details in customer portals, verify card expiration before renewal charges, or audit saved payment methods.
08 Action 08Stripe: Add Customer Card
Add a new card to an existing customer's account using a secure token. This action enables customers to save multiple payment methods for future transactions.
Key parameters:
- Customer ID: A required text field where you specify the customer
- Card Token: A required text field containing the tokenized card data (e.g.,
tok_1IMfKdJhRTnqsS5TKQVG1LI9o)
Use cases: Save cards during checkout for faster future purchases, add backup payment methods, or migrate payment data from other platforms.
09 Action 09Update Customer
Modify existing customer records in Stripe, updating details like email, name, address, metadata, or default payment source.
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.)
Use cases: Sync customer profile changes from your CRM, update billing addresses, change default payment methods, or add custom metadata for segmentation.
10 Action 10Stripe: Get Many Customers
Retrieve multiple customer records from Stripe with filtering and pagination options. Perfect for bulk operations, reporting, or syncing customer data across systems.
Key parameters:
- Return All: A toggle to fetch all matching records (overrides limit)
- Limit: A number field specifying maximum results (default: 50)
- Filters: Optional criteria to narrow results
Use cases: Export customer lists for analysis, sync all customers to your CRM, generate customer segments based on Stripe data, or audit your customer database.
11 Action 11Stripe: Customer - Get
Retrieve complete details for a single customer, including their email, name, saved payment methods, subscriptions, and metadata.
Key parameters:
- Customer ID: A required text field for the customer's unique identifier
Use cases: Fetch customer details for order confirmation emails, verify customer existence before processing actions, or retrieve metadata for personalization.
12 Action 12Delete Customer
Permanently remove a customer and their associated data from Stripe. This action is essential for GDPR compliance and data cleanup.
Key parameters:
- Customer ID: A required text field for the customer to delete
Use cases: Handle account deletion requests, clean up test data, or remove inactive customers according to your data retention policies.
13 Action 13Create Customer
Create new customer records in Stripe with optional details like name, email, and metadata. This action is typically the first step in any subscription or payment workflow.
Key parameters:
- Name: An optional text field for the customer's name
- Additional Fields: Optional parameters including email, description, phone, address, metadata, and more
Use cases: Create customers during signup, sync new CRM contacts to Stripe, or set up customer records before subscription creation.
14 Action 14Stripe: Get Many Coupons
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)
Use cases: Audit active promotions, sync coupon data to your marketing platform, or generate reports on discount usage.
15 Action 15Create Coupon
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.
16 Action 16Update Charge
Modify existing charge records to update metadata, descriptions, or fraud reporting details. Useful for adding context to transactions post-purchase.
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.
17 Action 17Get Many Charges
Retrieve multiple charge records with filtering options for comprehensive transaction analysis and reporting.
Key parameters:
- Return All: A toggle to fetch all charges
- Limit: A number field for maximum results (default: 50)
Use cases: Generate transaction reports, reconcile charges with orders, analyze payment patterns, or export data for accounting with tools like QuickBooks or Xero.
18 Action 18Stripe: Get a Charge
Retrieve complete details for a single charge, including amount, status, customer, payment method, and metadata.
Key parameters:
- Charge ID: A required text field for the charge's unique identifier
Use cases: Display transaction details to customers, verify charge status for order fulfillment, or retrieve charge data for refund processing.
19 Action 19Create Charge
Process a new payment by creating a charge against a customer's payment method or source. This is the core action for collecting payments through Stripe.
Key parameters:
- Customer ID: An optional text field for the customer (required if using saved payment method)
- Amount: A required number field for the charge amount (in smallest currency unit)
- Currency Name or ID: A required field for the currency code
- Source ID: An optional text field for the payment source
- Additional Fields: Optional parameters for description, metadata, shipping, etc.
Use cases: Charge saved cards for recurring purchases, process one-time payments, or create charges for manual orders.
20 Action 20Get Balance
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"
Use cases: Monitor cash flow, display balance in dashboards, trigger alerts for low balances, or integrate balance data into financial reports.
Build your first workflow with our team
Drop your email and we'll send you the catalog of automations you can ship today.
- Free n8n & Make scenarios to import
- Step-by-step setup docs
- Live cohort + community support
Frequently asked questions
Is 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.What'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.How 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.
