Skip to main content

Replace an automation's secret

An event automation that receives requests, such as a webhook or GitHub automation, trusts a request only when it is signed with, or carries, the automation's secret. If that secret leaks or nobody has it any more, replace it here.

Who can do this: requires the org admin role. Automations are listed under Audit, which only Org Owners and Admins see.

Not every automation has one. A webhook that takes an API key holds no secret. A Sentry or PagerDuty automation signs with the vendor's own secret: paste the new one into Sentry Client Secret or PagerDuty signing secret under Endpoint and select Save instead.

Replace it​

  1. In the sidebar, select Audit, then the Automations tab.
  2. Select the automation's name. Its page opens beside the list, on the Setup tab.
  3. Find Endpoint at the top of the tab. If it shows Reveal secret (one time), the secret has never been shown: select it to see the current secret once, and go to step 5.
  4. Select Rotate secret. A dialog with the automation's name says the old secret stops working at once. Select Rotate secret again to confirm, or Cancel to keep the old one.
  5. Store this secret now shows the new secret. Select Copy secret and keep it somewhere safe: this is the only time it is shown.
  6. Select I’ve stored it to close the dialog.
  7. Paste the new secret into every sender that posts to this automation, such as the Secret field of a GitHub webhook. If you rotated, the old secret has stopped working.
  8. To check a sender that signs its requests, select Check signature beside Rotate secret, paste the secret, a request body and its signature header, and select Check.

The next request a sender makes with the new secret shows as a run on the automation's Runs tab.