Datadog
Tellspin can follow a Datadog On-Call schedule you already use. Datadog remains the source of truth for the rotation. Tellspin reads who is currently on-call and keeps a Slack contact method (usually a user group such as @dev-on-call) pointed at that person.
This gives your team a non-incident way to reach the on-call engineer without opening Datadog.
How it works
- Connect with a Datadog API key and application key. An application key scoped to
on_call_readis enough. Pick the Datadog site that matches your Datadog URL (for example US1 (app.datadoghq.com)). - Datadog has no list-schedules API, so you paste the schedule URL or ID from On-Call → Schedules instead of choosing from a dropdown.
- Tellspin re-syncs every minute. The App Home shows the handle, current on-call user, Datadog sync schedule name, upcoming shifts, and a Syncs with Datadog On-Call every minute note.
User mapping
Matches by email are pre-filled when you create the link. Anyone whose email differs between Datadog and Slack has to be mapped by hand. After the schedule exists, use Edit → Change User Mappings → Edit Users. If the Datadog schedule has no members yet, add people to a layer in Datadog, then map them from Edit.
Reminders and keys
Datadog-synced reminders default to When a Datadog shift begins. If the keys are revoked or the site is wrong, open Datadog Connect again and paste a new API key and application key. Synced schedules keep their last known on-call until the next successful sync.