Publish public release notes upon production deployment
When a deployment is tracked in GitHub, automatically create a CMS item in Blatt 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.
Blatt Explore Blatt →
TriggersFires when a new page or post is published on Blatt.
Fires when a form on Blatt is submitted.
Fires when a CMS item is updated on Blatt.
Publishes or updates a page on Blatt.
Creates a new CMS item on Blatt.
Updates existing content on Blatt.
GitHub Explore GitHub →
TriggersFires when a new error or issue is captured in GitHub.
Fires when an issue's status changes in GitHub.
Fires when a new deployment is tracked in GitHub.
Creates or updates an issue in GitHub.
Assigns an issue in GitHub to a teammate.
Resolves or mutes an issue in GitHub.
More Blatt + GitHub workflows
See all Blatt + GitHub integrations → · Browse the full workflow library →
Enterprise-grade security
Common questions
Can Knit build “Publish public release notes upon production deployment” between Blatt and GitHub?
Yes — describe it in the box above and Knit's Integrations Agent researches Blatt and GitHub'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 GitHub with Blatt 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 Blatt, an issue can automatically be created in GitHub for developer investigation.