Power Automate email trigger not firing: invoice workflow checklist
Power Automate email trigger not firing? Use this checklist to fix shared mailbox folders, permissions, filters, and SharePoint invoice dedup so intake won’t stop.
Fix duplicate QuickBooks invoices from Fulcrum via Zapier
Fix duplicate QuickBooks invoices from Fulcrum via Zapier: normalize product names, add de-dup checks, and make invoice creation idempotent and retry-safe.
TABLE OF CONTENTS
If your Fulcrum-to-QuickBooks Zap (via Zapier) is creating duplicate invoices (or invoices with the wrong line items), the fix is usually the same: make your invoice creation step idempotent, normalize the item names you’re matching on, and add a “does this invoice already exist?” check before you create anything.
Why duplicates happen in Fulcrum → Zapier → QuickBooks
Most duplicate-invoice issues come from one of these patterns:
- The trigger fires more than once for the same inspection
- “Record assigned” / “record updated” triggers can fire multiple times as a record changes.
- Mobile sync or edits after the fact can re-trigger the Zap.
- Zapier retries on a slow or flaky step
- If QuickBooks times out (or Zapier doesn’t get a clear success response), Zapier can retry the task, which can create a second invoice if the action isn’t protected.
- Product/service matching isn’t stable
- QuickBooks line items often require an exact match to an existing Product/Service name.
- If your Fulcrum value has prefixes (like “4. Pre-Drywall Inspection”) but QuickBooks doesn’t, your lookup step can fail and your invoice step can end up with missing or incorrect items.
Step 1: Confirm you’re using the right trigger (and the right “unique ID”)
Before you touch the QuickBooks steps, pick the one field you’ll treat as the “source of truth” identifier for an invoice.
Good options:
- Fulcrum record ID (best)
- A Fulcrum “invoice key” field you create (good)
- A composite key like:
record_id + invoice_type(sometimes)
Avoid:
- Customer name + date (not unique enough)
- Address (not unique enough)
Checklist
Trigger is intentional (record created vs updated vs assigned)
You can identify a single unique key for each invoice
You can pass that key into QuickBooks (as Doc Number, Private Note, or a custom field—whatever your setup supports)
Step 2: Normalize product/service names before you look anything up
If your Fulcrum item names contain numbering or prefixes, strip them before you do a QuickBooks product lookup.
Example:
"4. Pre-Drywall Inspection" → "Pre-Drywall Inspection"In Zapier, you can do this with:
- Formatter by Zapier → Text → Replace
- A Code by Zapier step (if you need more control)
Quick normalization rules that work well
- Remove leading digits, periods, and spaces
- Trim whitespace
- Keep the “human” name exactly as it appears in QuickBooks
Checklist
Normalized name exactly matches the QuickBooks Product/Service name
You’re not passing just the number (like “4”) into the invoice line item
The same normalization runs every time (no manual fixes)
Step 3: Add a de-dup check (before “Create Invoice”)
This is the single most important change.
Option A (best): Search QuickBooks for an existing invoice by your unique key
Before creating an invoice:
- QuickBooks → Find Invoice (or Search Invoices)
- Filter using the key you stored (Doc Number / Memo / Private Note)
If you find one, stop (or update it) instead of creating a new invoice.
Option B: Use Zapier Storage as your “already created” registry
If QuickBooks search is limited (or too slow), use:
- Storage by Zapier → Get Value
- If empty: create invoice, then Set Value with the invoice ID
- If exists: skip create
This turns your invoice creation into a “create once” operation even if the trigger fires repeatedly.
Checklist
There is a step that can tell you “invoice already exists”
The create step only runs when the de-dup check says “not found”
Your de-dup key is unique per invoice (not per customer)
Step 4: Make invoice creation safe for retries
Even with de-dup checks, retries can still bite you if the check and the create run too close together.
Add protections like:
- A short Delay After Queue (if concurrency is possible)
- A “lock” value in Zapier Storage (set lock → create invoice → clear lock)
- Logging: store record ID + QuickBooks invoice ID somewhere you can audit later
Checklist
Duplicate triggers don’t create duplicates
Zapier retries don’t create duplicates
You can audit which Fulcrum record created which QuickBooks invoice
Step 5: Validate your line-item mapping (1–4 items + calculated quantities)
If your invoices usually have 1–4 services, keep the mapping simple and predictable.
Common pitfalls:
- Missing product lookups create blank lines
- Quantity fields come through as text (e.g.,
"2"instead of2) - Calculated quantities (like number of AC units) aren’t available at trigger time
Checklist
Each line item has: product/service ID + quantity + rate (as needed)
Quantity is numeric and defaults to 1 when missing
Calculated quantities are present and correctly parsed before invoice creation
Common “gotchas” to check quickly
Your Zap is not turned on in two different copies (duplicate Zaps)
You’re not triggering on both “created” and “updated” for the same record
Your customer lookup is stable (same customer found every time)
Your Zap doesn’t create an invoice in a loop (invoice creation updates the record, which triggers again)
When you want this fixed fast
Fixing a Fulcrum → QuickBooks duplicate-invoice issue usually breaks at the de-dup check — knowing whether the invoice already exists before you create it, and keeping that check idempotent under retries. If you’ve hit that wall, book a ZoomFlow session — one of our consultants can debug the Zap with you live and ship the working version in the same call.
Related Posts
Arabic RTL invoice portal from Zoho Books via Zapier
Build a shareable Arabic RTL invoice link from Zoho Books via Zapier. Add social icons, paid status, and due/overdue day counts with a platform decision tree.
From Spreadsheet Chaos to 24/7 Operations: How a Language Access Nonprofit Built a System Their Linguist Network Could Actually Use
See how a language access nonprofit replaced spreadsheets with an Airtable portal and automated invoicing — recovering 150+ staff hours per year.
