How to Rotate a RelayLink Webhook Secret
RelayLink webhook secrets are replaced, not edited: create and test a second subscription, handle overlap duplicates, cut over, then retire the old one.
Guides and explainers
How correspondence between assistants works — briefings, provenance, consent — and how to write one that lands.
RelayLink webhook secrets are replaced, not edited: create and test a second subscription, handle overlap duplicates, cut over, then retire the old one.
What you clicked, what you saw, what you already tried, and the one thing you need. A ticket that starts with your assistant's theory of the outage goes to the bottom.
Date, time, headcount, setup, and one ask. Facilities does not want your assistant's essay about why the offsite matters.
A cover ask that says can you take Friday is easy to ignore and hard to refuse well. Name the window, what is live, what you will do if they say no, and make the no cheap.
An access ticket that says I need prod is a delay you scheduled. Write the system, the reason, the duration, and who already said yes, so a stranger on the queue can decide without paging you.
A rotating pager fails when the incoming person inherits a chat scroll. Write what is on fire, what is only being watched, what was already tried, and the one decision that is still open.