Create tasks from new bugs
When a new bug is reported in Gleap, create a task in Shortcut.
Google for Startups AcceleratorHow Knit builds this workflow
The Agent researches both APIs and wires the trigger on one side to the action on the other — no pre-built connector required. Here is the vocabulary it has to work with.
Shortcut Explore Shortcut →
TriggersFires when a new task, job or item is created in Shortcut.
Fires when a task in Shortcut is marked complete.
Fires when a task's due date in Shortcut is coming up.
Fires when a task, job or project changes status in Shortcut.
Creates a new task, job or item in Shortcut.
Updates a task's status or assignee in Shortcut.
Posts a comment on a task in Shortcut.
Assigns a task in Shortcut to a team member.
Gleap Explore Gleap →
TriggersFires when a new bug or issue is reported in Gleap.
Fires when a test run or build passes or fails in Gleap.
Fires when someone comments on a bug in Gleap.
Creates a new bug or issue in Gleap.
Updates the status or details of an issue in Gleap.
Adds a comment to a bug in Gleap.
More Shortcut + Gleap workflows
See all Shortcut + Gleap integrations → · Browse the full workflow library →
Enterprise-grade security
Common questions
Can Knit build “Create tasks from new bugs” between Shortcut and Gleap?
Yes — describe it in the box above and Knit's Integrations Agent researches Shortcut and Gleap's public API docs (or your own uploaded docs) and builds a working workflow, whether or not either app already has a pre-built connector.
How long does it take to build?
Minutes to a first working version, not weeks — you test it against real data before it goes anywhere near production.
Why connect a bug tracker to a project management tool?
Testers work in Gleap, but the team plans in Shortcut. Syncing bugs between them means fixes are prioritized with the rest of the work.
Can completed tasks mark bugs as fixed?
Yes. When a task is completed in Shortcut, you can update the linked bug in Gleap so testers know to verify it.