How to Set Up Alert Notifications for a Team

How routing works

Every alert names a team. When it fires, Sigtake looks at that team's channels in the alert's project and delivers to each of them, and every member of the team also gets it in the app:

So the setup is four links: people into a team, the team into a project, a channel into that project, and the channel onto the team. The steps below make each one, then test the chain. For the model behind it, see routing alerts by team and how channels work.

Set it up

1. Create the team and add its members

   Go to Teams, create the team and give it a name people will recognize, such as Payments. Then add the people who should hear about its alerts.

   Sigtake generates a six-character team code, such as K7Q2XD, and shows it on the team's page. Your alerts will use it in the next steps. Operators and admins can do this step.

2. Add the team to the project

   On the team's page, under Projects, use Add to Project and pick the project its alerts come from, such as Production.

   Repeat for every environment the team covers. A team outside a project can't receive that project's alerts: they're rejected with TEAM_NOT_IN_PROJECT. This step needs an admin.

3. Create a channel in that project

   Switch to the project in the project switcher, open Channels and use Add Notification Channel. Pick the type:

   • Email: nothing else is required. It goes to the team's members, and you can add internal users or external addresses on top.
   • Slack: the first time, an admin connects your workspace from this form. Then pick the Slack channel. For a private channel, run /invite @Sigtake in it first.
   • Microsoft Teams: paste an incoming webhook URL, created in Teams from the channel's Incoming Webhook connector or a Power Automate HTTP flow.

4. Attach the channel to the team

   Back on the team's page, under Channels, assign the channel you just created. Channels are listed by project, so you'll see it under the project from step 2.

   This is the link that's easiest to forget. Until it exists the team's page warns that its alerts notify nobody, and the alert only shows up in the app. Attaching channels needs an admin.

5. Send a test alert

   Use an API key from the same project (API Keys in the sidebar) and send an alert with the team's code:

   curl -X POST https://api.sigtake.com/api/ingest \
     -H "X-Api-Key: $SIGTAKE_API_KEY" \
     -H "Content-Type: application/json" \
     -d '{
       "title": "Test alert: notification setup",
       "severity": "info",
       "source": "setup-check",
       "team_code": "K7Q2XD"
     }'

   A 201 response means the alert was accepted. The full request and response format is in the API docs.

6. Check it landed, then resolve it

   Within a few seconds the alert should appear in each place you set up: the Slack or Teams channel, the members' inboxes, and the bell icon for every member. Then open the alert in Sigtake and resolve it, so the next real alert with the same title starts a fresh incident.

If the alert didn't arrive

What to set up next

• A team per area of ownership, so each alert reaches the people who can fix it. Routing by team has patterns that work for small companies.
• Quieter channels in staging, by adding the same team to your staging project with its own Slack channel.
• A backup channel, such as email next to Slack, so an alert still lands if one destination breaks.