POST Webhook trigger with its public production /webhook/ URL,
not its temporary test URL. Use a durable system outside n8n when strict replay
and audit guarantees are required.
An organization administrator creates the public-HTTPS endpoint, subscribes it
to monitor.match, and creates the narrow 8-K watchlist monitor in the
signed-in Delivery dashboard. This is a
human-authenticated control-plane workflow; do not use an API key for setup.
Save the dashboard-issued endpoint ID, signing secret, and monitor ID. Verify
the raw request signature before using fields from an event; use a verification
proxy if your n8n configuration cannot preserve the raw body.
Use a dashboard test event only to confirm the receiver and signature path: it
sends webhook.test, not a production match. For the Slack or review-item
mapping, load this representative monitor.match sample into n8n (or replay a
recorded production monitor.match delivery) and map the fields shown:
type, data.monitor.id, data.matches[0].accessionNumber,
data.matches[0].htmlUrl, data.matches[0].form,
data.matches[0].ticker, data.matches[0].filingDate, and requestId.
The sample reflects fields emitted for a keyword filing match; preserve the
full received event rather than assuming a third-party parser shape.
Inspect delivery attempts and reconcile monitor matches after failures. A
scheduled delivery delay or a failed workflow is not proof that no filing exists.