A Next Gen Zap starts on its own when something happens in an app, on a schedule, or when a webhook receives a request. You can also run it on demand. You choose how a workflow starts when you build it, and you can change it in a draft at any time. By the end of this tutorial, you'll have set how your Next Gen Zap starts, published it, and confirmed that Zapier set up its trigger.
Available on plans:
Free
Professional
Team
Enterprise
Next Gen Zaps is in early access by request. Sign up at https://zapier.com/workflow/early-access. If you’re on a Team plan, the request must come from an account owner or admin. If you’re on an Enterprise plan, contact Support for access. This feature has limited availability and is in active development.
Ways a Next Gen Zap can start
The event that starts a Next Gen Zap is its trigger. A Next Gen Zap has one trigger, or no trigger.
| How it starts | Trigger app | Example |
|---|---|---|
| An app event | The app the event happens in | A new row is added to a Google Sheets spreadsheet. |
| A schedule | Schedule by Zapier | Every Monday at 8 AM. |
| A webhook | Webhooks by Zapier | Another app or system sends data to the workflow's URL. |
| On demand only | None | You run the workflow yourself. |
If you imported the workflow from a Classic Zap that starts with a webhook, the Next Gen Zap has a new webhook URL. The trigger panel lists the original URL and the new one. Update the app or system that sent data to the original URL, so it sends data to the new one.
You can run any published Next Gen Zap on demand while it is turned on, whether or not it has a trigger. A Next Gen Zap with no trigger runs only on demand.
Before you begin
- You need a Next Gen Zap. To build one, read Get started with Next Gen Zaps.
- You must be able to edit the workflow. Only the workflow's owner, a super admin, or the account owner can edit a Next Gen Zap.
- To start the workflow from an app event, connect the app to Zapier first.
Set or change the trigger
- In the Zapier left sidebar, click Automations, then select Next Gen Zaps in the second sidebar.
- Select your workflow. It opens in the Workflow Manager.
- If a published version is open, click Edit Zap on the right of the bar above the canvas. A draft opens.
- On the canvas, select the trigger step. If the workflow has no trigger, click Add a trigger instead. A new dialog box will open.
-
In the App field, search for and select an app.
- For a schedule, choose Schedule by Zapier.
- For a webhook, choose Webhooks by Zapier.
- In the Trigger Event field, select the event that you want to start the workflow.
- In the Authentication field, click Choose. A dropdown menu will open.
-
Select an existing account, or click + Connect a new account to connect a new app account.
- Some apps, such as Webhooks by Zapier, do not need one.
- In the Input Fields section, enter values for each field.
- On the right of the bar above the canvas, click Publish. A dialog box will open.
- Click Publish. The workflow turns on and uses the new version.
- In the Zapier left sidebar, click Automations, then select Next Gen Zaps in the second sidebar.
- Select your workflow. It opens in the Workflow Manager.
- In the top right of the top menu, click Chat. The Chat panel opens on the right.
- Describe how the workflow should start. For example, "Run this workflow every Monday at 8 AM" or "Start this workflow when a new row is added to my Google Sheets spreadsheet."
- Review the change. Zapier makes it in a draft, not in the published version.
- On the right of the bar above the canvas, click Publish. A dialog box will open.
- Click Publish. The workflow turns on and uses the new version.
- In your AI tool, describe how the workflow should start. For example, "Change my lead routing workflow to run every Monday at 8 AM." Your AI tool changes the trigger in a draft through Zapier MCP.
- Ask your AI tool to publish the draft and turn the workflow on. If you ask it only to publish, the workflow stays on or off, as it was before. In the Workflow Manager, Publish always turns the workflow on.
You cannot change the trigger in the code editor. Zapier saves the trigger with each draft and version, not in the workflow's code.
Run on demand
You can run a Next Gen Zap on demand. It will use the published version. The workflow must be turned on.
- In the Zapier left sidebar, click Automations, then select Next Gen Zaps in the second sidebar.
- Select your workflow. It opens in the Workflow Manager.
- On the right of the bar above the canvas, click the version or draft dropdown menu, then select the live version. It has an On tag.
- In the top right of the top menu, click Run. The Run dialog box opens.
-
Enter the inputs for the run.
- Use the Form tab to fill in each field, or the JSON tab to enter the data as JSON.
- Click Run. The run starts.
You can also ask your AI tool to run the workflow through Zapier MCP, or call it from your own code with the Zapier SDK. To build a workflow that runs only on demand, tell Zapier or your AI tool that the workflow has no trigger.
To try a change before it goes live, test a draft instead. A test does not use the trigger, so you enter the input yourself.
Confirm that Zapier set up the trigger
When you publish a workflow that has a trigger, Zapier sets up the trigger. This can take a few minutes.
- After you publish, wait while the Workflow Manager displays Turning on your Zap.
- When the trigger is set up, a message confirms that your Zap is on.
- If Zapier cannot set up the trigger, Your Zap couldn't turn on appears, and the workflow does not run. Click Review trigger, then fix the trigger or its connection.
Limitations
- A Next Gen Zap can have only one trigger.
- While a Next Gen Zap is off, its trigger does not receive events. Zapier does not run those events after you turn the workflow back on.
Next steps
You set how your Next Gen Zap starts, published it, and confirmed that Zapier set up its trigger.
- Read Get started with Next Gen Zaps to build your next workflow.
- Create Next Gen Zap drafts and versions to test a change to the trigger before you publish it.
- Learn how to prevent duplicate data in Next Gen Zaps when a trigger fires several times close together.
- Read Next Gen Zap limitations before you build a larger workflow.