Get every Stripe payment into QuickBooks without typing. When a charge succeeds, the flow finds or creates the right customer and makes a sales receipt in QuickBooks. Great for finance teams that want clean books and less manual work.

Here is how it runs end to end. A Stripe payment event starts the flow. It pulls the Stripe customer, then checks QuickBooks by email to see if that person already exists. If not, it creates the customer in QuickBooks. The data from the payment and the customer are merged. The flow then posts a sales receipt to QuickBooks using the API. Two branches handle existing and new customers so the receipt always uses the correct record. The QuickBooks endpoint shown uses the sandbox URL, which is helpful for safe testing.

To set this up, connect your Stripe account, connect your QuickBooks Online account, and map the fields you care about like description and tax code. Expect less data entry, faster close, and fewer errors from hand entry. This is useful for online stores, subscription apps, and any team that collects card payments and needs records in QuickBooks. Run first in test mode, then switch to live once you confirm the receipt appears as expected.

• Stripe event trigger listens for payment intent succeeded and starts the flow instantly
• Pulls the Stripe customer by ID from the payment to get name and email
• Searches QuickBooks Online for a matching customer by email before creating new records
• Creates a new QuickBooks customer when no match is found to avoid duplicates
• Merges payment and customer data so the sales receipt uses accurate fields
• Posts a sales receipt to QuickBooks Online through the API with OAuth2 auth
• Separate branches handle existing and new customers for clean mapping and fewer errors
• Uses the QuickBooks sandbox endpoint for safe end to end testing

• Reduce manual entry from 30 minutes per payment to under 2 minutes
• Improve data accuracy by up to 95 percent by removing copy paste steps
• Connect Stripe and QuickBooks so revenue data is always in one place
• Handle 10 times more payment volume without extra admin work
• Create customers on the fly to keep records complete and consistent

1. Import the template into n8n: Create a new workflow in n8n > Click the three dots menu > Select 'Import from File' > Choose the downloaded JSON file.
2. You'll need accounts with Stripe and QuickBooks Online. See the Tools Required section above for links to create accounts with these services.
3. In the n8n credentials manager, create a Stripe credential. If unsure, double click the Stripe nodes, open the Credential to connect with menu, click Create new credential, and follow the on screen steps. Use your Stripe test secret key for testing and live key for production.
4. In the n8n credentials manager, create a QuickBooks Online credential. Double click the QuickBooks nodes, choose Create new credential, and sign in with your Intuit account to approve access.
5. Open the Stripe Trigger node and make sure the event payment_intent.succeeded is selected. Save and activate the workflow so n8n can register the webhook.
6. Open the Get Stripe Customer node and confirm the customer field references the customer ID from the incoming Stripe event.
7. Open the GET QuickBooks Customer node and confirm the query uses the Stripe customer email. Replace the company ID in the URL with your own QuickBooks company ID if needed.
8. Open the Create QuickBooks Customer node and check that name, email, and balance fields are mapped from the Stripe data. Adjust any optional fields to match your account setup.
9. Review both POST Sales Receipt nodes. Verify the endpoint matches your QuickBooks company and region, and that description, tax code, and line details meet your accounting rules.
10. Test in Stripe test mode. Create a test payment for a new email and check the QuickBooks sandbox to confirm a customer and a sales receipt are created. Repeat with an existing customer email to confirm the match path works.
11. If no email is present or mapping fails, update the If and Merge nodes to handle a fallback field. Check the n8n executions log for errors and fix missing fields before going live.
12. Once validated, switch the Stripe credential to live keys and point the QuickBooks requests to your production company. Activate the workflow and monitor the first few runs.