ZenotiHelp

Configure zapier integration

ZTZenoti Docs Team Updated September 5, 2026 5 min readHow-to

Zapier connects Zenoti to thousands of third-party applications through automated workflows called Zaps. Use Zapier triggers and actions to sync data between Zenoti and tools such as Google Sheets, Slack, Mailchimp, or HubSpot without writing code. Zapier talks to Zenoti through the public Zenoti API using an API key you create in Zenoti.


On this page


Before you begin

Permission: Manage Apps under Api in the Administrator section of the security role is required to create or rotate the API application that Zapier uses. A Zenoti admin with access to Configuration > Integrations > Apps typically holds this permission.

  • Zapier account. You need a Zapier account (Free or paid, depending on task volume). Zaps run on Zapier's infrastructure β€” Zenoti does not run Zaps internally.
  • Decide what to integrate. Map out the specific trigger (for example, "new appointment booked") and action (for example, "append row to Google Sheet") before creating the Zap. Unused Zaps consume API calls and task quota.

External-system prerequisites

These steps happen in Zapier, not in Zenoti:

  • A Zapier workspace where you are an administrator or have permission to add new app connections.
  • The destination application (Google Sheets, Slack, Mailchimp, etc.) is already added to your Zapier workspace with valid credentials.
  • Sufficient Zapier task allowance on your plan for the expected event volume. Appointment and invoice events in high-volume centers can exceed free-tier quotas quickly.

Network requirements

Zapier calls the Zenoti public API from its own cloud; there is no direct connection from Zenoti to your network.

Direction Endpoint Port Purpose
Zapier β†’ Zenoti API https://<your-tenant>.zenoti.com/ 443 (HTTPS) Zapier polls Zenoti for triggers and pushes data via Zenoti actions
Zapier β†’ destination app Provider-specific (Google, Slack, etc.) 443 (HTTPS) Zapier to downstream app

No inbound traffic to your infrastructure is required. If your Zenoti tenant is IP-restricted (rare), whitelist Zapier's outbound IP ranges published on the Zapier documentation site.


Create an API application for Zapier

Create a dedicated API application in Zenoti β€” do not reuse a key shared with other integrations. A per-integration key is the only way to revoke Zapier access without breaking other consumers.

  1. Navigate to Configuration > Integrations > Apps.

  2. Select Add. The Create application wizard opens on 1 General.

  3. Enter:

    Field Source What to enter
    Application name Zenoti configuration (admin choice) Descriptive label β€” for example, "Zapier".
    Description Zenoti configuration (admin choice) What the Zap does and who owns it. Helpful for audit and offboarding.
    Scope Scope tab Grant only the endpoint groups Zapier needs, in the APIKey Groups list. Apply least-privilege.
  4. Save, then open the Credentials tab and select Generate API Key. Zenoti warns This will create a new apikey. NOTE : Please store the newly generated apikey safely, it won't be displayed later.

  5. Copy the key into your password vault immediately.

See Configure API applications for detailed application-management workflows including listing, editing, and revoking applications.


Connect Zenoti to Zapier

  1. Sign in to zapier.com.
  2. Create a new Zap.
  3. In the trigger step, search for and select Zenoti.
  4. Select a Zenoti trigger (for example, "New Appointment" or "New Guest").
  5. When prompted for authentication, paste the API key from the previous section and enter your Zenoti tenant URL.
  6. Zapier validates the key against Zenoti and saves the connection.
  7. Add the action step (for example, Google Sheets "Create Spreadsheet Row").
  8. Test the Zap using Zapier's built-in test feature.
  9. Enable the Zap once the test passes.

Build Zaps

After connecting, build Zaps to automate common workflows. Examples:

  • New appointment booked in Zenoti β†’ Append row to Google Sheet.
  • New guest created in Zenoti β†’ Add contact to Mailchimp.
  • Invoice closed in Zenoti β†’ Post notification to Slack.

Complex, low-latency flows are better served by direct API integration or webhooks; Zapier polls on its own schedule and is not real-time for most free-tier triggers.


Rotate or revoke the Zapier API key

Treat the API key like a password. Rotate it when Zapier integration ownership changes, when staff with key access leave, or on a scheduled cadence (at least annually).

  1. Navigate to Configuration > Integrations > Apps and open the Zapier application.
  2. On the Credentials tab, select Rotate to issue a new key (the old key expires a week later) or Remove beside the key to revoke it immediately without issuing a new one.
  3. Update the Zapier connection with the new key: in Zapier, open My Apps, find the Zenoti connection, and select Reconnect to paste the new key.
  4. Test a Zap after reconnecting to confirm the key change propagated.

Removal is immediate; rotation leaves the old key valid for a week so you can switch Zapier over. Schedule key changes during a low-activity window if you depend on always-on Zaps.


Failure paths

Failure mode User-visible symptom Resolution
API key invalid or revoked Zap fails with 401 Unauthorized in Zapier task history. Rotate or generate the key in Zenoti and reconnect in Zapier.
Scope missing for the Zapier trigger Specific Zap fails with 403 while others succeed. Grant the missing group under APIKey Groups on the application's Scope tab.
Zapier task quota exhausted Zaps pause and Zapier sends a quota-exceeded email. Upgrade the Zapier plan or reduce trigger frequency.
Destination app disconnected Zap fails in the action step, not the trigger step. Reconnect the destination app in Zapier β€” not a Zenoti-side issue.
Zenoti API rate limit exceeded Zaps intermittently fail with 429 Too Many Requests. Reduce Zap frequency or contact Zenoti Support about rate-limit adjustment.
Zap polling falls behind Delayed triggers β€” events appear in Zapier minutes or hours after happening in Zenoti. This is a Zapier polling-interval limitation on your plan, not a Zenoti issue. Use webhooks for real-time needs.

Tips

  • Use a separate API application per Zap owner or business function so revocation is surgical.
  • Use Zapier's built-in test feature to verify every Zap before turning it on.
  • Review your Zapier task usage monthly to stay within plan limits.
  • For real-time, low-latency needs, use webhooks directly to the Zenoti API or subscribe to webhook events through Zapier's webhook trigger rather than polling triggers.
  • Document each Zap's business owner so the API application can be deactivated when the owner leaves.

Was this article helpful?
Your feedback helps us improve our documentation.