When new page in Siteleaf, sync it to GitHub.
When a new page is published in Siteleaf, commit or sync the page content to GitHub.
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.
Siteleaf Explore Siteleaf →
TriggersFires when a new page or post is published on Siteleaf.
Fires when a form on Siteleaf is submitted.
Fires when a CMS item is updated on Siteleaf.
Publishes or updates a page on Siteleaf.
Creates a new CMS item on Siteleaf.
Updates existing content on Siteleaf.
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 Siteleaf + GitHub workflows
See all Siteleaf + GitHub integrations → · Browse the full workflow library →
Enterprise-grade security
Common questions
Can Knit build “When new page in Siteleaf, sync it to GitHub.” between Siteleaf and GitHub?
Yes — describe it in the box above and Knit's Integrations Agent researches Siteleaf 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 Siteleaf 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 Siteleaf, an issue can automatically be created in GitHub for developer investigation.