feat(quickbooks): add core webhook triggers - #6245
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub. |
PR SummaryMedium Risk Overview Introduces a fixed The QuickBooks block is enabled for triggers; integration metadata and docs describe the seven triggers and setup (Intuit callback URL + verifier token). Reviewed by Cursor Bugbot for commit 28c04b1. Bugbot is set up for automated code reviews on this repo. Configure here. |
Greptile SummaryThe PR adds authenticated QuickBooks webhook ingestion and durable fanout to deployed workflows associated with the affected company.
Confidence Score: 5/5The PR appears safe to merge. The previously reported batch-termination failure is fixed: target and page failures no longer prevent later events from being processed, while stable per-target event idempotency prevents successful workflow executions from repeating during retries. No blocking failure remains.
|
| Filename | Overview |
|---|---|
| apps/sim/background/quickbooks-webhook-ingress.ts | Processes every target and event before surfacing aggregate failures; the prior batch-stranding issue is resolved and successful redispatches are deduplicated downstream. |
| apps/sim/background/quickbooks-webhook-targets.ts | Resolves active QuickBooks targets by exact parsed company identity using bounded keyset pagination and workspace/deployment constraints. |
| apps/sim/app/api/webhooks/quickbooks/route.ts | Adds bounded raw-body ingestion, signature verification, schema validation, admission control, and durable acceptance semantics. |
| apps/sim/lib/webhooks/providers/quickbooks.ts | Adds QuickBooks authentication, event matching, normalized trigger input, and stable event-ID extraction for execution idempotency. |
| apps/sim/triggers/quickbooks/utils.ts | Defines shared QuickBooks trigger configuration, event-type parsing, matching, and output schemas for the seven new triggers. |
| apps/sim/blocks/blocks/quickbooks.ts | Enables trigger support on the existing QuickBooks block and exposes the seven registered trigger options. |
Sequence Diagram
sequenceDiagram
participant QB as QuickBooks
participant API as Webhook Route
participant Ingress as Ingress Job
participant DB as Target Resolver
participant Dispatch as Webhook Dispatcher
participant Workflow as Workflow Execution
QB->>API: Signed event batch
API->>API: Verify HMAC and validate envelope
API->>Ingress: Durably enqueue bounded batch
API-->>QB: 200 OK
loop Each event and target page
Ingress->>DB: Resolve targets by realm ID
DB-->>Ingress: Active deployed targets
loop Each target
Ingress->>Dispatch: Dispatch event
Dispatch->>Workflow: Enqueue idempotent execution
end
end
Reviews (3): Last reviewed commit: "fix(quickbooks): bound webhook ingress j..." | Re-trigger Greptile
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes using high effort and found 1 potential issue.
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit 937ec78. Configure here.

Summary
Validation
Live Intuit delivery remains dependent on configuring the public callback and QUICKBOOKS_WEBHOOK_VERIFIER_TOKEN; signed raw-body fixtures cover ingress locally.