
Next Gen Zaps can now diagnose failures, test a repair and publish a working version without waiting for a person to rebuild the workflow. In one week, the feature saved 100,000 tasks that would otherwise have failed, according to the LinkedIn post.
Zapier uses the name Next Gen Zaps for workflows built by asking AI tools such as Claude, ChatGPT, Muse and Grok Bot. Builders may not have assembled those workflows step by step, but until now they were still responsible for repairing them when something broke.
- Tasks saved
- 100,000
- tasks that would have failed
- Measurement period
- 1 week
- following the feature's introduction
How Next Gen Zaps Repair Themselves
A repair can start when an app changes something a Zap relies on. Zapier gives the example of an app renaming a field, which causes the workflow to fail because its existing configuration points to the old field.
An agent then handles the repair loop. It reads the error, works out a fix and tests the proposed change. If the test passes and the change is considered small, the agent publishes a new version of the Zap automatically.
- 1
Read the error
identify why the workflow failed
- 2
Work out a fix
update the affected workflow configuration
- 3
Test the change
check that the revised Zap works
- 4
Publish the version
put the repaired Zap live
- 5
Report the repair
email the user with what changed
Once the revised version is live, Zapier emails the user with details of the change. This replaces the previous process where a failure email told the user that the Zap had broken and needed manual attention.
Approval Stays in Place for Bigger Changes
The agent does not publish every proposed repair on its own. Small fixes can go through automatically, while it asks the user whenever a repair would make a big change or touch a login.
That leaves two repair routes. Routine configuration changes can be tested and published by the agent. Changes involving greater scope or account access pause for approval before proceeding.
Zapier also directs builders to connect Zapier MCP wherever they build with AI. The MCP connection lets AI tools work with Zapier while creating these workflows, including tools such as Muse, which is also covered in Zapier Connector Brings 9,000+ Apps to Meta Muse.
Frequently asked questions
What are Zapier Next Gen Zaps?
Next Gen Zaps are workflows customers build by asking AI tools such as Claude, ChatGPT, Muse or Grok Bot. They can now use an agent to diagnose, test and publish repairs when the workflow breaks.
How do self-healing Next Gen Zaps work?
An agent reads the workflow error, works out a repair and tests it. It can publish small fixes automatically, then emails the user with what changed. Bigger changes and repairs that touch a login require user approval.
Which Zapier plans include self-healing Next Gen Zaps?
Zapier has not listed plan availability or pricing for self-healing Next Gen Zaps in the announcement. The post directs builders to connect Zapier MCP wherever they build with AI.
Sources
4 checkedHow we cover tool news: Create With's tool desk drafts these reports with AI from the sources listed above and checks them against those sources before publishing.







