Manage Teml
Connect tools and notification delivery
Connect external tools, create delivery channels, and verify alerts can reach responders.
Connections authorize Teml to interact with another product. Notification channels define a concrete delivery destination used by alert rules. A connection alone does not route any alert.
Connect an external tool
Open Connections and choose a provider:
- Slack, GitHub, Jira, and Linear use an authorization flow;
- PagerDuty accepts an Events API v2 routing key.
Complete the provider flow, return to Teml, and confirm the provider shows Connected. A Needs reauth state means the saved authorization can no longer be used. Disconnect a provider only after checking alert routes and linked ticket workflows that depend on it.
Create a notification channel
Open Settings → Notifications → Notification channels. Create a channel for webhook, Slack, email, or PagerDuty delivery. Select the connected provider or enter the required destination, save, then choose Test on the saved channel.
Only attach a channel to an alert rule after the test succeeds. When deleting a channel, update every rule that routes to it; those rules will otherwise stop delivering to that destination.
Configure personal contact methods
In Settings → Notifications → My contact methods, add an email address or Slack DM destination. Those are the personal methods that deliver today; SMS and phone are shown as coming soon and cannot be selected. Slack DM requires an active Slack connection. Contact methods belong to the signed-in member, while notification channels belong to the organization.
After adding a contact method, confirm it is available when building the relevant on-call and escalation workflow.
Troubleshoot delivery
- Test the saved notification channel directly.
- Confirm its connection is active and the destination still exists.
- Confirm the alert rule is enabled and routes to that exact channel.
- Check whether the alert actually entered the firing state.
- For on-call paging, confirm the active schedule, escalation step, and responder contact method.
Never paste provider tokens or routing keys into support messages.