Publish public release notes upon production deployment
When a deployment is tracked in 0CodeKit, automatically create a CMS item in Ycode to showcase new updates on your product release page.
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.
Ycode Explore Ycode →
TriggersFires when a new page or post is published on Ycode.
Fires when a form on Ycode is submitted.
Fires when a CMS item is updated on Ycode.
Publishes or updates a page on Ycode.
Creates a new CMS item on Ycode.
Updates existing content on Ycode.
0CodeKit Explore 0CodeKit →
TriggersFires when a new error or issue is captured in 0CodeKit.
Fires when an issue's status changes in 0CodeKit.
Fires when a new deployment is tracked in 0CodeKit.
Creates or updates an issue in 0CodeKit.
Assigns an issue in 0CodeKit to a teammate.
Resolves or mutes an issue in 0CodeKit.
More Ycode + 0CodeKit workflows
See all Ycode + 0CodeKit integrations → · Browse the full workflow library →
Enterprise-grade security
Common questions
Can Knit build “Publish public release notes upon production deployment” between Ycode and 0CodeKit?
Yes — describe it in the box above and Knit's Integrations Agent researches Ycode and 0CodeKit'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 developer tools with a website CMS?
Connecting 0CodeKit with Ycode lets you automatically publish content updates from code deployments and route website feedback directly to your issue queue.
Can website form submissions log software issues automatically?
Yes, when a user submits a form in Ycode, an issue can automatically be created in 0CodeKit for developer investigation.