Inbound webhook
Push normalized compliance evidence to us from approved n8n, Zapier, Make, or CI workflows. We mint a secret URL; POST normalized JSON and it lands as evidence.
What this connector audits
Checks this connector runs once it's connected. This is the full list; we don't claim coverage beyond what's implemented.
- Per-integration secret token
- Normalizes pushed JSON to assets
What we need
Field labels only. We never show secret values here. Credentials are encrypted at rest and used only to run the checks above.
Which frameworks this evidence supports
Inbound webhook evidence feeds into controls for any framework you run that requires this check type; the same synced evidence can satisfy more than one framework's requirements instead of being collected per audit.
Don't see your system?
Tell us what you use and what it needs to prove. We'll follow up about adding a connector.
Wire in Inbound webhook evidence
Get a guided demo, or start by scanning any domain for free.