← All N8N workflows
Business & commerceHTTP RequestIfMergeQuickbooksStripe

post sales receipt and get quickbooks customer and get stripe customer

Configured with HTTP Request, Quickbooks, Stripe, Stripe Trigger. Review the connections and setup before adapting this template.

Workflow preview
Web / APIPOST Sales ReceiptHTTP RequestWeb / APIGET Quickbooks CustomerHTTP RequestIntegrationGet Stripe CustomerStripeTriggerNew PaymentStripe TriggerRoutingIf Customer ExistsIfTransformUse Stripe CustomerMergeIntegrationCreate QuickBooksCustomerQuickbooksTransformMerge Stripe andQuickBooks DataMergeTransformMerge Payment andQuickBooks CustomerMergeWeb / APIPOST Sales Receipt ToQuickBooksHTTP Request

Node categories in this workflow

  • Web / API
  • Integration
  • Trigger
  • Routing
  • Transform

Icons describe general node roles, inferred from node types. Inspect the parameters for the configured action.

Drag to pan; use + and − to zoom. Reconstructed from the exported node positions; nothing runs here. Dashed lines represent non-main connections. Full node names and notes appear below.

How it works

The exported workflow contains the following configured nodes. Their connections are shown above; inspect the JSON for the complete logic, expressions, and external actions.

Workflow node names, types, and operations
NodeCategoryTypeOperation
POST Sales ReceiptWeb / APIHTTP RequestPOST
GET Quickbooks CustomerWeb / APIHTTP RequestSee node parameters
Get Stripe CustomerIntegrationStripecustomer
New PaymentTriggerStripe TriggerSee node parameters
If Customer ExistsRoutingIfSee node parameters
Use Stripe CustomerTransformMergeSee node parameters
Create QuickBooks CustomerIntegrationQuickbookscreate
Merge Stripe and QuickBooks DataTransformMergeSee node parameters
Merge Payment and QuickBooks CustomerTransformMergeSee node parameters
POST Sales Receipt To QuickBooksWeb / APIHTTP RequestPOST

Setup

  1. Download the JSON and import it into an isolated n8n instance. Leave the workflow inactive.
  2. Connect your own credentials through n8n’s credential store. Replace REPLACE_WITH_* values with your resource identifiers.
  3. Inspect API destinations, Code nodes, database queries, file paths, and outbound actions.
  4. Run with synthetic data and harmless destinations. Enable triggers only after checking the actual outputs.

Requirements

An n8n instance with the listed node types and compatible versions. Service-connected workflows may require accounts, credentials, or paid APIs.

Credential types declared in the source

  • httpCustomAuth
  • quickBooksOAuth2Api
  • stripeApi

Workflow notes

post sales receipt and get quickbooks customer and get stripe customer

post sales receipt and get quickbooks customer and get stripe customer

Purpose and structure

This folder contains the post sales receipt and get quickbooks customer and get stripe customer workflow. Its executable nodes use httpRequest, if, merge, quickbooks, stripe, stripeTrigger. The table and connection map below are derived from the JSON, not an inferred guarantee of behavior.

Setup

Import inactive. Configure your own credentials and replace REPLACE_WITH_* values. Review external destinations and Code nodes before running.

Entry points

New Payment

Verification

Sanitized source candidate; not runtime-tested. This overview is generated from node metadata. Read the folder README for the connection map, credential types, and license.

Attribution

https://github.com/Zie619/n8n-workflows/blob/94007c1445d9258a7da116646b79473e7c7c3282/workflows/Http/0707_HTTP_Stripe_Create_Webhook.json MIT; preserve source notices.

More in Business & commerce