QuickBooks webhooks for non-developers
A QuickBooks webhook is QuickBooks telling another app, on its own, that something you care about just changed. You do not need to write code to understand it or to set it up. This guide explains the idea in plain language, shows who does what, and walks through every click. When you want the field-by-field reference, it is in How do I set up QuickBooks Online webhooks?
What a webhook is
A webhook is one service notifying another app when a chosen event happens. For example: an invoice is created or a payment is applied in QuickBooks, and a moment later your app is told.
Compare the alternatives:
- Checking by hand. Someone opens QuickBooks and looks for changes. It works until they forget.
- Polling. Your app asks QuickBooks “anything new?” every few minutes. Most answers are “no”, and a change can wait until the next ask.
- A webhook. QuickBooks knocks on your door only when something happened.
The three roles
| Role | What it does |
|---|---|
| QuickBooks | The accounting source. It notices the change and sends a notification. |
| Slashbin | Receives the notification, checks it really came from QuickBooks, and routes it onward. |
| Your app | Does the business action: send a thank-you email, update a dashboard, start a workflow. |
Slashbin does not replace QuickBooks, and it does not build your app. It is the dependable middle step between them.
Set it up
Each step says what to do and why.
1. Choose the event
Decide what should trigger something, such as “a new invoice is created”. Why: you will pick matching events on the Intuit screen later, and a clear choice keeps you from being flooded with notifications you do not need.
2. Create a QuickBooks data stream in Slashbin and copy its Ingestion URL
In Slashbin, create a new data stream and select QuickBooks. Copy the Ingestion URL it shows you. Why: the Ingestion URL is the address QuickBooks will send notifications to.
3. Open the matching tab under Webhooks
In the Intuit Developer dashboard, open your app and go to Webhooks. You will see two tabs, Development and Production. Choose the one that matches the QuickBooks company you are connecting. Why: Development and Production settings are separate. Filling in one does nothing for the other, so repeat these steps on the second tab when you move to real company data.
4. Paste the Endpoint URL, choose events, keep the cloud event format on, and Save
- Paste your Ingestion URL into Endpoint URL.
- Choose your Subscribed events.
- Keep Enable cloud event payload format switched on.
- Click Save.
Why: the Endpoint URL tells Intuit where to send things, and Subscribed events tell it what to send. The cloud event format is required by Intuit, and Slashbin reads the type of each event from it. Slashbin does not offer the other format as a setup, so leave it on.
5. Show the verifier token and paste it into Slashbin
Still on the Webhooks screen, click Show verifier token and copy the Verifier Token. In Slashbin, paste it into the QuickBooks Inbound Secret field of your data stream. Why: this shared secret lets Slashbin confirm each notification really came from QuickBooks. Note the two names: Intuit calls it a Verifier Token, Slashbin’s field is labelled QuickBooks Inbound Secret. They are the same value under different names. You do not write any verification code; Slashbin does the checking.
6. See the first event in Slashbin
Change a record in a QuickBooks company that is connected to your app, for example create a test invoice, and watch the event appear in your data stream in Slashbin. Why: a first real event proves the whole chain works before anything depends on it.
Two things that trip people up
- A company must be connected. QuickBooks only sends notifications for companies that have been connected to your app through OAuth 2.0, the standard “sign in and allow access” step. Choosing events alone produces no notifications.
- Notifications are pointers. A notification says what changed and where, not the whole accounting record. Your app uses it as a signal to go and look at the current record in QuickBooks.
How this compares with GitHub
If you have set up a webhook in GitHub, the idea is the same, but the details differ.
| QuickBooks | GitHub | |
|---|---|---|
| Where | Intuit Developer dashboard, under Webhooks | A repository’s or organization’s settings |
| Environments | Separate Development and Production settings | One set of settings |
| Who is covered | Companies connected to your app through OAuth 2.0 | The repository or organization you add it to |
| Credential | Verifier Token | A shared secret you choose |
| Choosing events | Subscribed events | Event types you tick |
| Payload | Cloud event format, with the event type inside it | A JSON object, with the event type in a header |
Next
- Field-by-field reference, including how events are routed and mapped: How do I set up QuickBooks Online webhooks?
- Setting up the same thing for GitHub: How do I debug a failed GitHub webhook delivery?
- Why a signature check matters: How do I verify a webhook signature?