Flag failed test runs
When a test run fails in Userback, create a high-priority task in Bonsai.
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.
Userback Explore Userback →
TriggersFires when a new bug or issue is reported in Userback.
Fires when a test run or build passes or fails in Userback.
Fires when someone comments on a bug in Userback.
Creates a new bug or issue in Userback.
Updates the status or details of an issue in Userback.
Adds a comment to a bug in Userback.
Bonsai Explore Bonsai →
TriggersFires when a new task, job or item is created in Bonsai.
Fires when a task in Bonsai is marked complete.
Fires when a task's due date in Bonsai is coming up.
Fires when a task, job or project changes status in Bonsai.
Creates a new task, job or item in Bonsai.
Updates a task's status or assignee in Bonsai.
Posts a comment on a task in Bonsai.
Assigns a task in Bonsai to a team member.
More Userback + Bonsai workflows
See all Userback + Bonsai integrations → · Browse the full workflow library →
Enterprise-grade security
Common questions
Can Knit build “Flag failed test runs” between Userback and Bonsai?
Yes — describe it in the box above and Knit's Integrations Agent researches Userback and Bonsai'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 Userback, but the team plans in Bonsai. 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 Bonsai, you can update the linked bug in Userback so testers know to verify it.