Zapier

What the integration does

Once Zapier is connected to your TimeTuna account, your Zaps can use TimeTuna in three different roles.

Triggers (TimeTuna starts the Zap)

• New booking fires when a guest confirms a booking on one of your booking pages.
• Booking cancelled fires when a previously confirmed booking is cancelled, by you or the guest.
• Booking rescheduled fires when a booking is moved to a new time.

Actions (Zapier writes to TimeTuna)

• Create a booking on a booking page you own, with a guest name, email, start time, and optional form responses.
• Cancel a booking by its booking ID.
• Reschedule a booking to a new start time, by booking ID.

Searches (Zapier reads from TimeTuna)

• Find booking pages powers the booking-page dropdowns inside the Zap editor, so you do not have to paste IDs.
• Find available times returns the open slots on a given booking page for a given date. Useful as a step before Create a booking when the upstream app does not already know a real open slot.

What TimeTuna does not do via Zapier

• It does not expose data from booking pages you do not own.
• It does not stream partially filled forms, only confirmed bookings.
• It does not change your availability, working hours, or connected calendars.
• It does not let Zapier act on your behalf in connected providers (Google, Microsoft, Zoom).

Permissions we request

The Zapier OAuth app uses one scope:

• bookings read recent bookings on booking pages you own, and create, cancel, or reschedule bookings on your behalf. This scope does not grant access to other users' data.

Connecting TimeTuna to Zapier

Before you start: make sure you are on the Executive plan and that you have at least one booking page set up. Zapier needs a booking page to show in dropdowns when you build a Zap.

1. Sign in to TimeTuna at timetuna.com/signin.
2. Open zapier.com/apps and search for TimeTuna.
3. Start a new Zap and add a TimeTuna step (either a trigger like New booking, or an action like Create a booking).
4. When Zapier asks you to choose an account, click Connect a new account. Zapier will open a TimeTuna authorize screen in a new window.
5. Review the requested permission and click Authorize. You are returned to Zapier with the account connected.
6. The Zap step now lists your booking pages in any dropdown that needs one, powered by the Find booking pages search.

Building a Zap with TimeTuna as the trigger

1. In Zapier, create a new Zap and pick TimeTuna as the trigger app.
2. Choose the event: New booking, Booking cancelled, or Booking rescheduled.
3. Select the connected TimeTuna account.
4. Optionally narrow to a specific booking page from the dropdown. If you leave it blank, the trigger fires for bookings on every page you own.
5. Test the trigger. Zapier will pull a recent sample booking so you can map fields.

Delivery is near real-time: TimeTuna posts the event to Zapier within seconds of the booking. Each event payload includes the guest name and email, start and end time, timezone, booking page, meeting link (Zoom or Google Meet, when applicable), and any form responses the guest filled in.

Building a Zap with TimeTuna as the action

Create a booking

1. Add a TimeTuna action step and pick Create a booking.
2. Pick the booking page from the dropdown. The list comes from Find booking pages.
3. Provide the guest's name and email.
4. Provide the start time in ISO 8601 format (for example 2026-06-01T14:00:00Z). If the upstream step does not already know a real open slot, add a Find available times search step before this one and map its output here.
5. Optionally map any form responses the booking page expects.

Cancel a booking

Provide the booking ID. You can get this from the New booking trigger, from a previous Create a booking step, or by storing it in your own database when the booking is first made.

Reschedule a booking

Provide the booking ID and a new start time, same format as Create a booking.

Where Zapier-created webhooks show up in TimeTuna

Every Zap that uses a TimeTuna trigger registers a webhook subscription on your account. You can see them in Booking page → Webhooks. Subscriptions registered by Zapier are labelled Created by Zapier, so you can tell them apart from any custom webhooks you added by hand.

When a Zap is deleted or its hook URL stops existing, Zapier answers our deliveries with HTTP 410 and TimeTuna automatically deactivates that subscription, so it disappears from the Webhooks list. Turning the Zap back on re-registers it.

Inspecting webhook delivery logs

Open Booking page → Webhooks and click Logs next to a Zapier-created subscription to see the last 30 days of deliveries: timestamp, response status, duration, the JSON payload TimeTuna sent, and the response body Zapier returned.

Use this to confirm that a single new booking produced exactly one delivery. If the logs show one delivery but your downstream app received multiple rows, the duplication is happening inside Zapier or the action app; see Zapier duplicate rows for the fix.

Disconnecting Zapier

You can disconnect at any time, from either side.

From Zapier

1. Sign in to zapier.com and open My Apps.
2. Find TimeTuna, then click the menu and choose Disconnect.
3. Any Zap that used that connection will pause until you reconnect or pick a different TimeTuna account.

From TimeTuna

1. Open Booking page → Webhooks.
2. Delete the webhook subscriptions labelled Created by Zapier. This immediately stops event delivery to that Zap.
3. To revoke the underlying OAuth token entirely, ask us through chat; we delete the token row, which deactivates every Zap using that connection in one step.

What we delete, and what stays

On disconnect TimeTuna deletes the row in our oauth_tokens table that stores the access and refresh tokens for that Zapier connection, and deactivates every webhook subscription tied to it. Already-delivered events stay in Zapier's task history. Bookings that were created through Zapier remain on your account exactly as if you had created them yourself; disconnecting does not delete bookings.

Troubleshooting

Zapier says my TimeTuna account is not connected

The OAuth token was revoked, or your account is no longer on the Executive plan. Reconnect from inside any TimeTuna step in Zapier. If you are no longer on Executive, upgrade from your dashboard first.

My Zap is not firing on new bookings

1. Open Booking page → Webhooks and confirm a subscription labelled Created by Zapier exists for the event you expect.
2. Check that the booking actually completed. Bookings that are still waiting on payment do not fire New booking; they fire only after payment is captured.
3. In Zapier, open the Zap's history. If the event arrived but the Zap errored on a later step, the Zap is the issue, not the connection.

Create a booking fails with “no available time”

The start time you passed is outside the booking page's availability, conflicts with another booking, or is in the past. Add a Find available times search step before Create a booking and map one of its returned slots into the start-time field.

I disconnected by accident

Reconnect from any TimeTuna step in Zapier. Re-enable the Zap; Zapier will re-register the webhook subscription with TimeTuna automatically the next time the Zap turns on.

Still stuck?

Open the chat in the bottom-right with your TimeTuna account email, the Zap name, and (if possible) a screenshot of the Zap step that is failing. The chat is open to everyone, no sign-in required. We reply within one business day.