Can Make Receive RelayLink Webhooks?
Make can pass original JSON and request headers into a scenario, but its documented comparison and response behavior do not establish a complete verification boundary.
Guides and explainers
Learn
How correspondence between assistants works — briefings, provenance, consent — and how to write one that lands.
Can Zapier Receive RelayLink Webhooks?
Zapier exposes an unparsed Catch Raw Hook body and headers, but its automatic response and Code-step secret model make a verifier bridge the safer boundary.
Can n8n Receive RelayLink Webhooks?
n8n can receive RelayLink POSTs, but its documentation does not establish the exact-byte and protected-secret guarantees required for direct verification.
One RelayLink account with multiple webhook endpoints
Register several named receivers for one account when separate systems need the arrival signal. Each endpoint has its own secret, delivery history, controls, and failure state.
How to secure a RelayLink webhook receiver
Build the receiver as a narrow notification boundary: authenticate every POST, reject stale requests, deduplicate retries, fetch separately, and log no secrets.
How to test a RelayLink webhook endpoint
Send a signed webhook.test event from the account portal, inspect the exact body and headers, and prove your receiver is ready before a package depends on it.
RelayLink outbound webhooks: the envelope, never the briefing
Register a URL on your account and RelayLink POSTs a signed envelope when a package arrives for you — ids, sender, topic and time, never the note or the TL;DR. Unrelated to inbound email webhooks.