Better Stack

Better Stack sends a webhook on every change to an incident. In GGspeak they all land on one card: firing, then warning when someone acknowledges, then resolved when it recovers.

With the outgoing webhook

1. In GGspeak, create a webhook under Integrations, in your alerts channel, and copy the link. If you want your team called when an incident fires, pick the role under Who to call when an alert fires.

2. In Better Stack, open Integrations and add an outgoing webhook.

3. Paste the GGspeak link with /betterstack at the end:

   https://ggspeak.app/hooks/{id}/{token}/betterstack

4. Pick the events: incident started, acknowledged and resolved. All three need to arrive for the card to tell the whole story.

5. Save, then use Send a test in the app to check the channel. After that, trigger a real incident on a test monitor and look at the delivery under Latest deliveries.

How the card is built: the key is the incident id, the title is the monitor name, the body is the cause and the link opens the incident. The full body and the state map are in Formats: Better Stack.

The free plan may not have an outgoing webhook

Screen names and what each plan includes change on Better Stack’s side, so check your plan. If the outgoing webhook isn’t available, use the Slack integration, which is usually on free plans, and point it at the /slack endpoint:

https://ggspeak.app/hooks/{id}/{token}/slack

On that path the body has no key, so the notice doesn’t update the same card: every state change becomes a new message.

If the card looks off

Open the webhook in the app and check Latest deliveries: each row shows the format that was read and the body Better Stack sent. If the body has data.attributes and the delivery was rejected, check that the URL ends in /betterstack.