When release published in ReleaseNotes, sync it to GitHub.
When a release is published in ReleaseNotes, create or sync the release details in GitHub.
See all ReleaseNotes + GitHub integrations or talk to a human
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.
ReleaseNotes Explore ReleaseNotes →
TriggersFires when a user completes an onboarding checklist in ReleaseNotes.
Fires when ReleaseNotes tracks a product event for a user.
Fires when a user leaves feedback, a feature request or a survey answer in ReleaseNotes.
Fires when a changelog entry, release note or announcement is published in ReleaseNotes.
Adds or updates a user and their properties in ReleaseNotes.
Sends a product event to ReleaseNotes.
Publishes a checklist, tour or announcement in ReleaseNotes.
GitHub Explore GitHub →
TriggersFires when a job, build or file conversion finishes in GitHub.
Fires when a job, build or API request fails in GitHub.
Calls an GitHub endpoint with data from an earlier step.
Creates a PDF, image or converted file with GitHub.
Checks or enriches a phone number, address or IP with GitHub.
More ReleaseNotes + GitHub workflows
See all ReleaseNotes + GitHub integrations → · Browse the full workflow library →
Enterprise-grade security
Common questions
Can Knit build “When release published in ReleaseNotes, sync it to GitHub.” between ReleaseNotes and GitHub?
Yes — describe it in the box above and Knit's Integrations Agent researches ReleaseNotes 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.
What's the most common Developer Tools + Project Management automation?
Marking the linked task in ReleaseNotes complete (or moving it to review) automatically when a pull request merges in GitHub.
Does this need commit messages to reference the task ID?
That's the most reliable way to match them, though the Agent can also match on branch name or a manually linked reference depending on your workflow.