Publish public release notes upon production deployment
When a deployment is tracked in Orshot, automatically create a CMS item in Unbounce 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.
Orshot Explore Orshot →
TriggersFires when a job, build or file conversion finishes in Orshot.
Fires when a job, build or API request fails in Orshot.
Calls an Orshot endpoint with data from an earlier step.
Creates a PDF, image or converted file with Orshot.
Checks or enriches a phone number, address or IP with Orshot.
Unbounce Explore Unbounce →
TriggersFires when a new page or post is published on Unbounce.
Fires when a form on Unbounce is submitted.
Fires when a CMS item is updated on Unbounce.
Publishes or updates a page on Unbounce.
Creates a new CMS item on Unbounce.
Updates existing content on Unbounce.
More Orshot + Unbounce workflows
See all Orshot + Unbounce integrations → · Browse the full workflow library →
Enterprise-grade security
Common questions
Can Knit build “Publish public release notes upon production deployment” between Orshot and Unbounce?
Yes — describe it in the box above and Knit's Integrations Agent researches Orshot and Unbounce'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 Orshot with Unbounce 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 Unbounce, an issue can automatically be created in Orshot for developer investigation.