Hello there,
This is Patricia from the Zapier Support team, stepping in here to help.

From what I understand, your Zap triggers from QuickBooks when an invoice is emailed, then sends a Slack message, but sometimes it runs twice for the same invoice — both runs showing the same timestamp and identical data.

This kind of duplicate triggering can happen when QuickBooks sends multiple webhook events for the same invoice action (for example, one for the main recipient and another for CC recipients). Since the trigger data looks the same, Zapier treats each webhook as a separate event, which results in duplicate runs.

Here are a few ways you can minimize or prevent this:

1. Add a Filter step
   Include a “Filter by Zapier” step after the trigger to check for a unique value — such as the QuickBooks Invoice created and updated dates

2. Use a Deduplication step
   If you can identify a field that stays consistent per invoice (like the invoice number), you can use a “Storage by Zapier” step to store that value and prevent the same one from processing twice within a short time frame.

3. Apply a Delay and Recheck logic
   Add a short “Delay For” step (for example, 1 minute), then recheck against Storage to see if that invoice has already been processed. If it has, stop the Zap.

4. Check QuickBooks behavior
   If the duplicates are always at the exact same timestamp, that confirms it’s a double webhook delivery from QuickBooks. In that case, these extra steps in Zapier are the best way to guard against them, since Zapier can’t prevent triggers that the app itself sends.

Are you looking to also gain control over how often a Zap triggers? You can learn more on this here.

Kind regards

Hey there ​@Sergey Shch 👋

How did you get on with PatriciaF’s suggestions here - did they help you to filter out the duplicate invoices?

Let us know how it went, want to make sure you’ve got everything sorted! 🙂