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