[mintlify]

The Trigger automation webhook API reference now shows that every error response includes success: false next to the error message, and it lists the 500 response.

The endpoint now returns a consistent envelope: success: true with a runId on 202, and success: false on 400, 402, 404, 500 and 503. Integrators can now check one field instead of relying on the status code alone. The reference previously showed only an error field for failures and did not list 500.

Based on a merged API change by Nathan Tang that adds the success: false flag to all automation webhook error responses. The shared Error schema used by other endpoints is unchanged.

Duplicate check: no open docs PRs mention webhook or automation, none by the source author or Ethan cover this, and nothing merged since Oct 20 touches this endpoint.

---

Note

Low Risk
OpenAPI documentation only; no runtime or implementation changes in this PR.

Overview
Updates the Trigger automation webhook OpenAPI spec so success and error bodies match the API’s consistent envelope.

202 documents that success is always true alongside runId. 400, 402, 404, 503, and a newly documented 500 now reference a dedicated AutomationWebhookError schema (success: false plus error) instead of the generic Error type. The shared Error schema used elsewhere in the Admin API is unchanged.

^{Reviewed by Cursor Bugbot for commit 2fbe005. Bugbot is set up for automated code reviews on this repo. Configure here.}

[mintlify]

Preview deployment for your docs. Learn more about Mintlify Previews.

Project	Status	Preview	Updated
Mintlify Docs	🟢 Ready	View Preview	Oct 21, 2026, 11:55 PM