Tellagen
← Back to Support Center

Set up and manage webhooks

Send new incident events to your tools. Add a destination in Settings, save its signing secret, and manage delivery.

GuideOpen Markdown version
On this page

Before you start

Intended audience

Workspace managers and the team that runs the receiving service.

Required permissions

You need permission to manage workspace settings. You do not need an API key for this setup.

Prerequisites

  • Get a public HTTPS receiver URL from your integration team. Use HTTPS port 443. Local and private addresses are not supported.
  • Ask your integration team to prepare the receiver with the webhook developer guide. The receiver must answer verification requests and check signatures before it processes events.
  • The preview sends only Incident created events. A workspace can have up to 10 active or paused webhooks.

Procedure

Add a webhook

  1. Step 1 of 9

    Open Webhooks

    In your workspace, open Settings. Under Operations, select Webhooks.

  2. Step 2 of 9

    Add a destination

    Select Add webhook. Enter a name, such as Incident archive. Paste the full Destination URL from your integration team.

    Add webhook form with the name Incident archive, an example HTTPS destination, and the Incident created event.
    Enter a name and the full HTTPS destination URL. This example uses Incident archive. Open full-size image(opens in a new tab)

  3. Step 3 of 9

    Create the webhook

    Check the destination and the Incident created event. Select Create webhook. The webhook stays inactive until the receiver passes a check.

  4. Step 4 of 9

    Save the signing secret

    Copy the secret into your receiver configuration. Store it securely. Select I saved this secret. Tellagen does not show it again.

    Signing secret dialog with a copy button and the I saved this secret button.
    Copy your secret before you close this dialog. The image shows an example value, not a working secret. Open full-size image(opens in a new tab)

  5. Step 5 of 9

    Check the receiver

    Ask your integration team to add the verification response from the developer guide. Open the webhook actions. Select Verify receiver. A successful check starts delivery.

Manage webhooks when needed

  1. Step 6 of 9

    Check delivery

    After the next incident is created, select Refresh. Check Last success and Last failure. Ask your integration team to check the receiver logs.

  2. Step 7 of 9

    Pause or resume delivery

    Open the webhook's actions. Select Pause or Resume and read the confirmation. New events are skipped during a pause.

  3. Step 8 of 9

    Replace a signing secret

    Open the webhook's actions. Select Replace signing secret. Copy the new secret into your receiver within 24 hours.

  4. Step 9 of 9

    Remove a webhook

    Open the webhook's actions. Select Remove webhook and confirm. To use that destination again, add a new webhook.

You are done when…

The webhook list shows your destination name, host, and status. The receiver gets events for incidents created while the webhook is active.

Troubleshooting

Webhooks is missing from Settings.

Ask a workspace admin for permission to manage workspace settings.

The destination URL is rejected.

Use a public HTTPS URL without a username, password, or fragment. Use the final address because Tellagen does not follow redirects.

The list shows only the destination host.

Tellagen hides URL paths and query values. Use the name and webhook ID to identify the destination. The full URL is still used for delivery.

The signing secret was lost.

Select Replace signing secret in the webhook's actions. Save the new secret in your receiver. The previous secret works for 24 hours.

The webhook needs verification.

Set up the signing secret and verification response in your receiver. Then select Verify receiver. Wait one minute between attempts.

The webhook is active but no event arrives.

Active means delivery is enabled. It does not prove that the receiver accepted a request. Only new incidents trigger events. Demo workspaces do not send webhooks.

Delivery failed.

Check the receiver URL, signing secret, and receiver logs. Tellagen stops after eight attempts or 24 hours. Five consecutive failures require another receiver check. See retries and delivery deadlines.

A paused webhook missed events.

Resuming does not replay events from the pause period. Queued deliveries can continue before their original deadlines. There is no manual replay action.

A request arrives after a pause or removal.

Tellagen cannot recall a request that it already sent.

Creation failed and the result is unclear.

Close the form and refresh the list before you try again. If the webhook exists, replace its signing secret.

The destination URL needs to change.

Remove the old webhook and add a new one with the correct URL. Set up the new signing secret in your receiver.

Related articles