What QuickBooks sends — and what ReviewNudger requires
The integration starts from a specific provider event, then resolves only the payment and customer facts listed here.
Accepted provider event
Payment — Create or Update
ReviewNudger handles QuickBooks Online webhook notifications for a Payment entity on Create or Update. This means a customer payment was recorded or changed; it does not necessarily mean a related invoice is fully paid.
Payment amount and customer reference
The Payment record must include TotalAmt and CustomerRef so ReviewNudger can identify both the paid amount and the referenced customer.
Primary customer contact
The referenced QuickBooks customer must have a usable PrimaryEmailAddr or PrimaryPhone value.
A usable sending route
The location must have automation enabled, and the customer must pass cooldown, do-not-contact, and channel opt-out checks.
See the connection and its latest event
The connected-apps view shows whether QuickBooks is connected, whether ReviewNudger has received an event, and whether that event was processed or needs attention.
Illustrative product walkthrough using fictional Summit Plumbing data — not a customer case study.
From paid event to request, every step stays visible
The request journey records the trigger, initial delivery, follow-ups, stops, and outcomes in one timeline.
- 1Connect QuickBooks Online to ReviewNudger through Intuit's standard OAuth authorization. Your books stay in QuickBooks; ReviewNudger only listens for payment events.
- 2When a customer payment is recorded in QuickBooks Online, ReviewNudger receives the event, resolves the customer's contact details, and applies your sending rules. It can then send one neutral Google review request by SMS or email.
- 3Every send is tracked with delivery status, opt-outs, and review click-through, all visible from one dashboard.
Illustrative product walkthrough using fictional Summit Plumbing data — not a customer case study.
What happens when the clean path is not available
Skipped and failed events are recorded with a reason. Nothing silently guesses a customer or sends around an opt-out.
Retries collapse onto one journey
Provider retries and repeated updates reuse the same provider payment identity. They cannot create a second ReviewNudger review-request journey.
Missing facts fail visibly
ReviewNudger requires the provider's amount and customer contact facts. If either is missing, the incoming event records the failure and no customer is guessed.
Sending rules can suppress the request
Disabled automation, an active cooldown, do-not-contact state, or an opt-out on the usable channel suppresses the request with a visible reason.
Refunds do not create or rewind journeys
Refund and reversal events do not create another request. They also do not automatically cancel a journey that already exists; an operator can cancel a queued request or stop later follow-ups.
Recorded payment is the boundary
ReviewNudger does not infer invoice balance from a Payment webhook. If your workflow records partial payments, those records are evaluated by the same sending rules.
Create and Update share one identity
QuickBooks may notify ReviewNudger again when the same Payment changes. The QuickBooks company and Payment IDs keep both notifications tied to one journey.
Email can carry the first request while SMS waits
A newly registered SMS number must be approved before it can send customer messages. ReviewNudger never sends from a number that is still pending.
Use email when it is allowed and usable
If the customer has email, the location has email enabled, and the required business address is configured, email carries the initial request while SMS is under carrier review.
Otherwise, keep the event recoverable
If no usable email route exists, the event is visibly suppressed as sms_not_ready. After SMS approval, an operator can recover it from recent events instead of asking the provider to send it again.
Connect QuickBooks and prove the trigger end to end
Have these provider and ReviewNudger details ready before you connect.
Before you start
- A QuickBooks Online company and permission to approve the Intuit OAuth connection.
- Primary email or phone saved on customers whose Payment records should start requests.
- A completed ReviewNudger location with its Google review destination and sending channels configured.
- 1Start a ReviewNudger trial and finish the short signup.
- 2Choose QuickBooks as your payment trigger and approve the Intuit OAuth connection.
- 3Record a real customer payment in QuickBooks to confirm the trigger end to end.
- 4Done. Each recorded customer payment can now start one automatic review request under your sending rules.
QuickBooks integration questions
Do I need a Zapier account to connect QuickBooks?
No. The QuickBooks integration is native: you connect it directly inside ReviewNudger, with no middleware account, no per-task automation fees, and no field mapping to maintain.
What exactly triggers a review request?
Each time a customer payment is recorded in QuickBooks Online, ReviewNudger records the event and evaluates it against your per-location send delay, cooldown, contact, and channel rules. One matching event can create one review-request journey by SMS or email.
Can a retry or duplicate webhook double-text a customer?
No. Every incoming event is deduplicated before any message is sent, and each event can create at most one review request. Provider retries and replays collapse onto the same request instead of sending twice.
What about customers who opt out?
SMS recipients can reply STOP at any time and email recipients can unsubscribe. Opt-outs are recorded per customer and honored across every future QuickBooks-triggered event.
Does this wait for the related invoice to be fully paid?
No. The trigger is a QuickBooks Online Payment record being created or updated. That records customer payment activity, but it does not prove that every related invoice is fully paid. ReviewNudger does not add an invoice-balance rule that QuickBooks did not send.
Questions before you start? Email support@reviewnudger.com and a human will answer.