Configure a Wiz automation rule to push issue findings to a webhook endpoint
domain: docs.wiz.io · 6 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
In the Wiz console, navigate to Settings > Integrations and create a new Webhook integration by providing your endpoint URL and an optional shared secret for payload validation.
Go to Policies > Automation Rules and create a new rule; set the trigger to Issue Created or Issue Updated and scope it by severity, resource type, or project.
Select the webhook integration as the action target and configure the payload template to include fields such as issue ID, severity, resource name, cloud provider, and a link to the Wiz console.
Save and test the rule by clicking Test Integration in the webhook configuration panel; inspect the HTTP request received by your endpoint.
Validate the shared secret on your endpoint by computing HMAC-SHA256 of the raw request body with your secret and comparing it against the X-Wiz-Event-Signature header.
Monitor rule execution in Settings > Automation Rules > Execution History and alert on delivery failures.
Known gotchas
Webhook payloads are delivered at-least-once; your endpoint must be idempotent, deduplicating on the issue ID to avoid creating duplicate tickets.
Wiz retries failed deliveries with exponential backoff; ensure your endpoint responds with HTTP 200 within the timeout window to avoid retries.
Automation rule conditions are evaluated on Wiz's backend; changes to rule scope take effect within a few minutes, not immediately.
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?