Connect a signed webhook and inspect delivery
Send events to your backend while verifying signatures and avoiding duplicate processing.
- A controlled HTTPS receiver and integration-management permission.
Step-by-step walkthrough
- 01
Open Apps & integrations and choose the signed-webhook connector. Use an HTTPS receiver you control and subscribe only to events the integration needs.
- 02
Store the signing secret privately on the receiver and verify requests using the current delivery specification. Do not confuse a signing secret with a user-session token.
- 03
Use Queue test where available and inspect History. Verify the receiver records the event and responds successfully after durable acceptance.
- 04
Make your receiver idempotent so retries do not create duplicate work. Log safe event identifiers and outcomes rather than full customer payloads.
- 05
When pausing, disconnecting, or rotating a secret, coordinate the receiver change. A request already in flight may still arrive.
A closer look at the interface
These are actual product captures from a fictional demo workspace. Navigation and available controls can differ by role, configuration, or release.
Integration connections
- 1Check whether the connection is active or paused.
- 2Inspect History when delivery needs attention.
- 3Rotate a signing secret only with the receiving system prepared.
Expected result
A verified event delivery with signature checking and duplicate handling.
Important details
A connected configuration is not proof of successful delivery. Check both RelayDesk history and receiver evidence.
Need help with this workflow? Contact the team and include this guide’s title.