Back to TimeTuna

Zapier duplicate rows

One TimeTuna booking ends up creating several rows in Google Sheets, Notion, or another connected app.

Symptom

  • One new booking produces two or three rows in your Google Sheet.
  • Slack messages or Notion entries repeat the same booking multiple times.
  • The duplicates always include the most recent past bookings, not just the new one.

Why it happens

Older versions of the TimeTuna Zapier app re-polled the recent-bookings list on every push, so each new booking triggered the action three times. The current version of the app delivers exactly one item per booking event.

Separately, turning a Zap off and on or rebuilding it could leave several registered webhook subscriptions for the same Zap on your account. Each one delivered the booking once, so a single booking produced two or three rows even on the fixed app version. TimeTuna now keeps exactly one active subscription per Zap hook URL; duplicates that already existed were deactivated automatically, with no action needed from you.

How to fix

  1. Open your Zap in Zapier.
  2. If Zapier shows an Update available banner on the TimeTuna trigger step, accept it. This pulls in the fix.
  3. Save and turn the Zap back on.
  4. Create one test booking and confirm only one row is added downstream. Then open Webhooks in your TimeTuna dashboard, click Logs on the Zapier-created subscription, and confirm exactly one delivery was recorded. See the Zapier integration docs for more on the logs panel.
Clean up existing duplicates
The fix only affects future bookings. Past duplicates in your sheet or destination app have to be removed by hand. Sort by booking ID to spot rows that share the same id.

Still not working?

Open the webhook logs and copy the delivery timestamps for one booking. If you see one delivery but multiple downstream rows, the duplication is happening inside Zapier or the action app and we can help debug it. Reach with the booking ID and a screenshot of the logs.