Skip to main content

I have a Zap with a Quickbooks “New Invoice” Trigger that is not working reliably.
 

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.

Because of this it is my suspicion that something is going wrong on Quickbooks end, so there isn’t much I can do to troubleshoot.

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 Invoice Events.

The Zap is sending invoice information to our Airtable for Order Processing purposes, so if an invoice doesn’t get sent via the zap it can cause an order to go missing. So it’s pretty important for this Zap to work reliably.

Has anyone else experienced this and is there anything I can do to mitigate it?
 

Please add me to the list. 
 

Same issue for over 20 apps. New Bill, New Invoice, New Account, and New Expense - none of my Quickbooks zaps are works. Stopped around 4/1. Extremely frustrating. 


Please add me to the list.

This started 2 April for me - have tried everything from turning off/on to creating a brand new zap. Everything is needing to be done manually for my business now which is unacceptable after 3 full days.

Anyone else try any alternate solutions such as n8n? Will explore that now.

 


Same for Quickbooks Estimates. Sketchy since Apr 1, completely fail since Apr 3.

Based on comments here it sounds like nearly all of QB’s Instant Updates are non-functional. Does Zapier itself have any kind of SLA with QB, and/or does the QB API have any guarantees?

This is costing a lot of people a lot of money and with no accountability as to what is happening.


Same here. No zaps from QB new invoices since March 31.


Hi there, ​@corus, ​@AaronPRSL, ​@JoeMoore, ​@Sommerfly and ​@CA1 👋

Really sorry that these issues are still occurring—I totally understand the frustration here. The team are still working on this and unfortunately, I can’t give any sort of timeframe for when it will be resolved. You’ve all been added to the list, so you’ll definitely get an email notification from us once a fixed has been rolled out. 

As ​Sommerfly mentioned, if you still have Zaps that used a legacy version of a trigger that was previously a polling, rather than instant type of trigger, duplicating or repurposing those other Zaps may get around the issue in the meantime. Thanks for sharing that potential workaround ​@Sommerfly, it’s much appreciated! 🤗

Another option (if it’s possible for QuickBooks to send you an email notification when an invoice is added/updated, or when there’s a new payment etc.) is to create a copy of your Zap and use Email Parser as the trigger. This would allow you to trigger the Zap based on the information parsed from those emails. Check out our Trigger Zaps from new parsed emails guide to learn more. That said, if those email notifications don’t include all the data you need, you could add a search step to retrieve the missing information from the invoice, payment, etc. Not an ideal solution, I know—but hopefully it helps as a temporary workaround to keep your workflows running while we work on a fix. 🤞 

I no longer have the legacy zap that used the Polling rather than Instant trigger.  I deleted it when the new kind became available.

 

If that fixes the issue, why doesn’t Zapier just make that option (polling) available again?


@CA1  It's a longshot but check your trash folder. If any legacy polling zap is still there, move to main folder and edit as needed. 

Yes, they need to make polling options available as soon as possible. 

They can apologize all they want but there doesn't seem to be any urgency to getting this fixed or even creating a temporary workaround by activating polling option. 

 


Hi ​@inmotion, ​@opsGA, ​@campbeji, and ​@Salidokit,

I have added you to the list of affected users. We will keep you updated via email once the bug has been fixed.

I appreciate your patience and understanding.


Has been a week… any positive news for a fix?


I am also running into this issue where a new invoice does not trigger my zap. I can manually push through the “New Invoice” so it is gathering the data from QB, but it doesn’t trigger the actual zap. 


Add me to the list as well.  This is killing our invoicing! We processed invoices on firday and the ZAP didnt do anything until Sunday!


I had a zap trigger this morning on an Estimate I created in Quickbooks last Wednesday.  5 days later.  

If my subscription was month to month, I already would’ve canceled it.


Glad to see that this was not just me. I run a smaller operation so this doesn’t cost us a LOT of money/time, but I can’t imagine how it must be for those of you with larger organizations. Hopefully this is resolved as soon as possible, but it appears to me that this is on Quickbooks’ side as well. 


Add me to the list, it is not working for our organization either.


Hi, you can add me also to the list of people having this issue. As for me, the zap is simply not catching it. Last one that did work was on 03/31 


Hi friends,

I've added you all to the list of affected users. Unfortunately, the bug is still open. Our engineers are actively investigating it. We’ll keep you updated via email as soon as there’s any progress.

I appreciate your patience and understanding.


The same here. The last time any Zap connected to Quickbooks worked 1st April. Since then nothing. We tried to reconnect. No luck. Do we know if anyone is working on this?


Please add me to the list as well. This happens all the time now (started 5-6 weeks ago). I have a workaround for invoices that are send. I have a backup zap that kicks in later (works really well) but this doesn’t help me when invoices are NOT send only saved. And the delays are more than 24 hours. I have an invoice I created on 4/7/2025 at 1PM Eastern and so far ZAP has not triggered. 

Instead of telling us (@zapier) that you have a ticket with Quickbooks, it would be far more useful for us to get the info you have (proof of the delays) so WE (people who pay for QB’s) can all contact QB’s and ask them for a status on this. Can you maybe help? It is useless to contact QB’s without any details and proof for us users. 

thanks

 

claus

 


Is there an actual update available? This has been down for more than a week and the only tech responses are acknowledgments of the issue.
 

This will reach over $60,000 in business disruptions by the end of this week. I can’t imagine what larger entities are experiencing. Is there no SLA with QBO? I’ve called and spoken with my QBO pro support and they don’t seem to have any idea what I’m talking about. It is not acceptable for an integration company to drop its connections and provide nothing in the way of solutions for over a week. Absolutely unheard of. 


I also contacted the QuickBooks development team and asked them for an update. I got the same response. They had no idea what I was talking about and there are another way of any issues with the API or webhooks. 

I have seen problems on and off since March maybe even February. But now it seems to have stopped working completely. 


Yes, this is affecting us also — please add us to the list as well.


How about one of zapier engineers reaching out by phone to Quickbooks as they say there is no issue????


Hi, you can add me to this list as well, we have noticed this starting April 1st as well.   Its April 8th and this continues to be a big issue for us.  Any updates or work-arounds? 


Hi friends,

 

We sincerely apologize for the inconvenience. We're currently working on resolving the issue as soon as possible. Hence, I’ve added everyone to the list of affected users, and we’ll notify everyone via email once an update is readily available. Thanks.


What’s the update on this? It’s been over a week with no resolution.


Hey folks!

Just wanted to share a quick update from the team on where things currently stand:

“QuickBooks has advised us that are investigating the cause of the delayed webhooks on their side and will let us know once the issue is resolved.”

We appreciate how frustrating it is to wait on a fix, and we’re really sorry for the disruption this is causing to everyone’s workflows. We’ll keep you posted as soon as we have any further updates to share. 

Thanks for bearing with us in the meantime. 🙏