# Zapier Won't Turn On a Zap? Work Through These Checks

**By StackTrekker Editorial** · Published October 5, 2026
When the Publish button refuses to click or a Zap flips straight back to Draft the moment you switch it on, Zapier is enforcing one of six rules. Inside the Zap itself, a step can be unfinished: an app event was never picked, a required field is empty, or a warning is still sitting on the step. On the account side, the Zap can trip a plan limit, sit above your task allowance, live in a folder you do not own, or fall under an administrator's publishing restriction. The first four checks take under a minute each, so run them in order. You do not need to rebuild the Zap or start again from a template. Every cause here is fixable in place, and the fix is always in the editor or in Settings rather than in a support ticket.

## Why won't Zapier let you turn on the Zap?

Zapier allows a Zap to be switched on only when every part of it can actually run. The editor holds the Zap as a draft until all of its steps are valid, and the Publish button stays disabled while any step is incomplete. When the button does click but the Zap drops back to Draft, the same rule is being applied from the other direction: Zapier took the click and then refused to keep the Zap running.

Two situations are worth separating before you start. A Zap that cannot be turned on is not the same as a Zap that turns on and then fails every run. This page covers the first case, where the switch itself is blocked. If your Zap is already on and the runs are failing, skip to the last section, which points at different tools.

## 1. A step in the Zap is unfinished

Open the Zap and read every step in the left-hand outline. A step that is not ready carries a warning marker, and the Publish button will not activate until that marker clears. Four things produce it:

- An app event was never selected, so the step shows the app name and nothing else.
- A required field is empty, for example a spreadsheet or a target folder that was never picked.
- The trigger was never tested, so there is no sample data to map the later steps against.
- A mapped field points at a step you deleted or reordered, so the reference goes nowhere.

Fix each warning in place and retest the step. The Publish button comes back on its own once the last marker is gone.

## 2. The Zap uses something your plan does not include

The Free plan covers a Zap with one trigger and one action. As soon as the Zap needs a second action, an app marked Premium, or a logic step such as a Filter, publishing is blocked. The editor still lets you build the Zap, which is why the block shows up at the very end, when you try to turn it on.

If the blocked step is a Filter, the editor gives no hint that the plan is the problem. Our guide to [Zapier filters not working](/zapier-filter-not-working/) covers that case in full, including the plan requirement behind a locked step.

## Which plan limits block the Publish button?

The table below maps what a Zap contains to whether it can be published.

| What The Zap Uses | Free Plan | Paid Plans |
|---|---|---|
| One Trigger And One Action | Publishes | Publishes |
| Two Or More Actions | Blocked | Publishes |
| An App Marked Premium | Blocked | Publishes |
| A Filter Or Path Step | Blocked | Publishes |

Building a Zap and turning it on are separate permissions in Zapier. You can assemble a multi-step Zap on Free, test every step, and only meet the limit at publish time. If the workflow genuinely needs the second action, the plan is the fix, not the editor.

## 3. Your account is over its task limit or on a billing hold

Zapier pauses Zaps when an account passes the task allowance included in its plan, and a failed payment puts the account on hold the same way. Both conditions sit in one place. Open Settings, then Billing, and look for a red banner about task usage or an outstanding invoice. A plan upgrade or a corrected payment clears the hold and the Zap can be switched back on.

## 4. The Zap lives in a folder you do not own

Zapier ties the right to turn a Zap on to ownership. If a teammate shared a Zap with you as view-only, or you were removed from the folder that held it, the switch is not yours to flip. The editor will open the Zap, and the Turn on control stays out of reach.

The fix here is social rather than technical. Ask the owner to switch the Zap on or to give you edit access to the folder. If you would rather hold your own version, duplicate the Zap into a folder you control and publish the copy instead.

## How do you tell a plan limit from a permission problem?

The two look identical at the button, so use the shape of the Zap to tell them apart. A plan limit lands on one specific step: the second action, the premium app, or the Filter. Everything else in the Zap is valid. A permission or account problem blocks the whole Zap no matter how simple it is, and it follows the Zap rather than any single step. If a fresh one-trigger, one-action Zap also refuses to turn on, the cause is the account or the folder, not the plan.

## 5. An administrator has locked publishing

On Team and Enterprise accounts, an administrator can switch on publishing restrictions. When that setting is active, a Zap that uses a restricted app or an unapproved version cannot be published by anyone below the required role. If the Turn on button is missing on an otherwise valid Zap and you are on a company account, this setting is worth a check with whoever manages the workspace.

## 6. An app connection has expired

If you changed the password on a connected account, or the app revoked the access token, the step shows a connection warning. Zapier blocks publishing while that warning stands, because a Zap that cannot authenticate would fail on its first run anyway. Open the step, click the account field, and reconnect. Repeat the step for any other step that uses the same app.

## Work through the checks in order

1. Fix the warnings in the step outline until the Publish button comes back.
2. Match the blocked step against your plan limits and the table above.
3. Check Settings, then Billing for a task or payment hold.
4. Confirm you own the Zap, or ask the owner to turn it on.
5. Ask an administrator whether publishing restrictions are on.
6. Reconnect any account that shows a connection warning.

## What if the Zap turns on but every run fails?

If the Zap accepted the switch and is now running with errors, the problem has moved from publishing to execution. Open Zap history and read the failing step. Three targets cover the ground: a step that returns no result, a mapped field that arrives empty, and a destination that rejects the data. If your Zap writes rows, the fixes overlap with the field-mapping traps in [Zapier and Google Sheets workflows](/zapier-google-sheets-workflows/). If it receives its data through a webhook, the failure order is different again, and our guide to [webhooks not firing](/zapier-webhook-error-fix/) walks it through step by step.

## FAQ

**Why is my Zapier Publish button greyed out?**

A step in the Zap is unfinished. An app event was never selected, a required field is empty, or the step was never tested, and the editor keeps the Publish button disabled until every warning clears. Open each step in the outline, fix the warning, and the button activates again.

**Why does my Zap go back to Draft right after I turn it on?**

Zapier accepted the click and then applied a rule the editor does not show as an error, usually a plan limit such as a second action, a premium app, or a Filter step on the Free plan. An account that has passed its task limit behaves the same way. Check the Billing area and the plan requirement for the blocked step.

**Can I publish a multi-step Zap on the Free plan?**

No. The Free plan covers one trigger and one action. A second action, an app marked Premium, and logic steps such as Filter or Path all require a paid plan, and the block only appears at publish time, after the Zap is built.

**The Turn on button is missing on a team account. Why?**

An administrator may have switched on publishing restrictions. That setting stops Zaps that use a restricted app or an unapproved version from being published. Ask the workspace owner to check the setting for your account.

## Sources

- [Zapier: Can't turn on or publish a Zap](https://help.zapier.com/hc/en-us/articles/8496199466125-Can-t-turn-on-or-publish-Zap)
- [Zapier: create Zap drafts and versions](https://help.zapier.com/hc/en-us/articles/9693520498445-Create-Zap-drafts-and-versions)
- [Zapier: enable publishing restrictions in your Enterprise account](https://help.zapier.com/hc/en-us/articles/21705940108941-Enable-publishing-restrictions-in-your-Enterprise-account)
- [Zapier: plans and pricing](https://zapier.com/pricing)

---

Source: https://stacktrekker.com/zapier-cant-turn-on-zap/