Integrations Automation
When this happens in Keel, do that anywhere else.
Switchyard wires Keel’s triggers (issue created, status changed, cycle closed) to actions in 600 other apps, and their triggers to Keel’s actions. Built and maintained by the Switchyard team, reviewed by ours.
Nov 2 – Nov 13 · 36 points
Cycle 24 · Backlog
- Cycle 24 closes Friday at 18:00Keel
- Trigger fires: “Cycle closed” with scope, done and carry-overrun #2,114Switchyard
- Adds a row to the team’s planning sheetSheet: Cycles 2026Switchyard
- Emails the report to leadership3 recipientsSwitchyard
- 3 carried-over issues land in Cycle 25 with a commentKeel
What it does
Switchyard, wired into the work.
9 triggers
Issue created, updated, status changed, commented, assigned; cycle started, closed; project update posted; request added.
7 actions
Create issue, update issue, comment, add label, add to cycle, add request, post project update.
Filters and paths
Run only for Urgent bugs, or branch by team. Switchyard handles retries.
Set it up
Three steps, about 5 min.
- 01Open Switchyard and search for Keel
- 02Connect with a Keel API key (Settings → API)
- 03Start from a template or build your own
Permissions
What it can see, in writing.
- reads
- what each run asks for, scoped to the API key’s teams
- writes
- only the actions you add
- support
- by Switchyard; Keel reviews every release
- available
- every plan
Questions
About Switchyard.
Often connected together
Connect Switchyard in 5 min.
Available on every plan, Free included. Start a workspace, then add it from Settings → Integrations.