Similar to what I am seeing reported elsewhere in this forum specifically @Printerpart...
I have a Zap with a Quickbooks “New Payment” Trigger that is not working reliably. I noticed this yesterday, April 2nd. I attempted to turn the zap off and turn back on. This didn’t seem to work, so I recreated the flow in a new zap. This newly created zap is also experiencing the same issues.
Sometimes the Zap will trigger instantly, other times it will take multiple hours to trigger, other times it won’t trigger at all.
There are never any errored Zaps, it either works or it doesn’t show up in the Zap history at all.
I have spent a ton of time troubleshooting this and I am at my wits end.
The Trigger is supposed to always be an Instant Trigger, so it seems like the quickbooks API is simply not sending some of the New Payment Events.
This is part of a service fulfillment workflow so it’s pretty important for this Zap to work reliably.
Please advise on what can be done to mitigate.
Hi @JoeMoore,
Welcome to the Community.
If you're having trouble with the QuickBooks "New Payment" trigger in your Zap, try these troubleshooting steps: check the status of the QuickBooks API for known issues, ensure connectivity between Zapier and QuickBooks by reconnecting your account, review your Zap history for patterns, and confirm you're not hitting QuickBooks API rate limits. If the issue persists, contact QuickBooks support for further assistance with their API or integration.
I hope this helps. If you have any other questions or need further clarification, please don't hesitate to ask.
I also am experiencing recent issues with the new payment trigger. It has not been working for a week. Have tried all of the troubleshooting suggestions provided above, and via zapier’s ai chatbot.
I did read that zapier updated it’s Quickbooks app last week. I’m guessing that is the culprit. @JammerS can you confirm that that happened?
Would really love to get this working again.
I'm having the same issue, and this is a critical part of my workflow. I'll be following the troubleshooting here closely.
The Quickbooks “instant triggers” aren’t working across the board it seems. I’ve had issues with the “New Estimate” not triggering. But I can still pull the records manually from editing the Zap.
We’ve been dealing with QBO issues for the past week as well. ‘New Estimate’ triggers are critical for our workflow and Zapier is not receiving the triggers until DAYS after the action is performed. Support has told us that this issue is top priority, but they aren’t getting any help from Intuit.
You would think Zapier would have a direct line to someone in their support department.
At this point, I’m really not understanding why they aren’t going back to a polling option where the Zap runs every so often and grabs the information from QB rather than the “instant” kind that’s relying on the QB webhook to make the zap fire. It’s my understanding that the legacy polling zaps that integrate with QB are still working.
It’s been a week….
Reported in several other threads like this one, but there’s no movement or solution. It’s INCREDIBLY frustrating…
Hi friends,
We sincerely apologize, but there is an open ticket regarding all QBO (QuickBooks Online) triggers not receiving or delayed hooks. It’s currently being investigated, and rest assured that we will update everyone once it is available.
I am having this issue too. New Purchase order instant trigger is not working for me. Very frustrating. Hope they can fix soon!
Hi @Jen Spencer,
I’ve added you to the list of affected users, and we’ll notify you via email once an update is readily available. Thanks.
Please add me to the list of effected users
Hi @James Hogan,
I’ve added you to the list of affected users, and we’ll notify you via email once an update is readily available. Thanks.
Hi @JammerS
Can you also add me to the list please. Are you able to give us some sort of status?
Hi friends,
It looks like QuickBooks Online has deployed a fix and hooks have now come in again.
Could you please confirm if the bug is now fixed on your end?
The fix seems to be working
That’s great news @James Hogan! Glad to hear that the issue is now resolved!
If you have any other questions, please don’t hesitate to reach out to the Community. We’re always happy to help! 
