Open issues from app requests
When a new request record is created in Bubble, create an issue in 0CodeKit.
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.
0CodeKit Explore 0CodeKit →
TriggersFires when a job, build or file conversion finishes in 0CodeKit.
Fires when a job, build or API request fails in 0CodeKit.
Calls an 0CodeKit endpoint with data from an earlier step.
Creates a PDF, image or converted file with 0CodeKit.
Checks or enriches a phone number, address or IP with 0CodeKit.
Bubble Explore Bubble →
TriggersFires when a new record is added to an app built in Bubble.
Fires when a record changes in an Bubble app.
Fires when a record is deleted in an Bubble app.
Adds a new record to an app built in Bubble.
Updates an existing record in an Bubble app.
Removes a record from an Bubble app.
More 0CodeKit + Bubble workflows
See all 0CodeKit + Bubble integrations → · Browse the full workflow library →
Enterprise-grade security
Common questions
Can Knit build “Open issues from app requests” between 0CodeKit and Bubble?
Yes — describe it in the box above and Knit's Integrations Agent researches 0CodeKit and Bubble'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.
Can a record in Bubble create an issue in 0CodeKit?
Yes. When a record such as a bug report or request is created in Bubble, 0CodeKit can open an issue or run a workflow.
Can developer events update my app?
When an issue closes or a deploy finishes in 0CodeKit, the related record in Bubble can be updated automatically.