Maximize efficiency with updated webhook behaviour
Written by Owner
Updated at August 20th, 2025
- Tables
-
Product updates
Product updates: January 2023 Product updates: March 2023 Product updates: February 2023 Product updates: April 2023 Product updates: May 2023 Product updates: June 2023 Product updates: July 2023 Product updates: August 2023 Product updates: September 2023 Product updates: October 2023 Product updates: November 2023 Product updates: December 2023 Product updates: January 2024 Product updates: February 2024 Product updates: March 2024 Product updates: April 2024 Product updates: May 2024 Product updates: June 2024 Product updates: July 2024 Product updates: August 2024 Product updates: September 2024 Product updates: October 2024 Product updates: November 2024 Product updates: December 2024 Product updates: January 2025 Product updates: February 2025 Product updates: March 2025 Product updates: April 2025 Product updates: May 2025 Product updates: June 2025 Product updates: July 2025 Product updates: August 2025
- Zaps
- Your Zapier account
- Interfaces
- Canvas
- Chatbots
- Getting started
- Agents
- MCP
- Built-in tools
- Lead Router
- Apps
NoteThis information was accurate at the time of publication. Please check out the latest product update notes for any updates or changes.
Previously, all Webhook by Zapier triggers returned a 200 response, regardless of whether there was a Zap behind the webhook or if the Zap was on or off. This is now changing for static webhook URLs, specifically Catch Hook and Catch Raw Hook triggers.
What's new:
- If your Zap is off or deleted, Zapier will return a 404 response for incoming webhooks directed at that Zap.
- There might be a short delay after a Zap is turned off, where it briefly returns a 200 response.
- Once reactivated, your Zap will resume, returning a 200 response.
This update provides you with more control and clearer feedback on your Zaps' status. Learn more about triggering Zaps from webhooks.