Make every GitHub release easier to hand off
A published release can trigger a Carbone document from your existing template. Notis carries the release details into a repeatable brief, so you spend less time assembling launch notes by hand.
Trigger
GitHub Release State Changed
Fires when a GitHub release changes.
Action
Generate Carbone Report
Generates a report from a Carbone template and JSON data, and returns its render ID.
Why this helps
Release information is already in GitHub, but copying notes into a separate document creates one more manual handoff and another chance to miss a detail.
- Start a release document from the GitHub release event, including its title, notes, tag, and published details.
- Use a Carbone template to keep recurring release briefs consistent.
- Reduce the copy-and-paste step between shipping in GitHub and sharing a release summary.
Setup
Build it in a few focused steps.
- 1Connect GitHub and Carbone to Notis once, and prepare a Carbone template for your release brief.
- 2Create an automation in the portal or ask Notis conversationally; describe that a published GitHub release should produce a brief from its available release details.
- 3Choose the GitHub release state-changed trigger for the release you want to monitor, select a channel for run reports, and create the automation.
- 4Test with a real published release and review the generated document for accurate notes and tag details.
Questions about this workflow
Does every edit to a release create a brief?
The trigger monitors changes to a specified release, including its title, notes, draft and prerelease flags, publication time, target, and assets. In your instruction, have Notis proceed only when the release is published and the relevant publication condition is met.
Do I need a Carbone template?
Yes. Generate Carbone Report renders a document from a template and JSON data, so prepare the brief template before enabling this workflow.
When this happens · Trigger
Fires when a GitHub release changes.
Do this · Action
Generates a report from a Carbone template and JSON data, and returns its render ID.
Supported Triggers and Actions
Notis builds workflows that link GitHub to Carbone. A trigger fires from one place; an action lands in another.
GitHub triggers
Carbone actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Delete Carbone Template
Deletes a Carbone template or version; the file is removed after a storage retention delay.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Download Template
Downloads the original template file.
New Workflow Artifact Created
Fires when a new GitHub Actions workflow artifact is created in a repository.
Generate Carbone Report
Generates a report from a Carbone template and JSON data, and returns its render ID.
Branch Changed
Fires when a branch’s commits or protection status or settings change.
Get Carbone Server Status
Checks the server’s current status and health.
New Branch Created
Fires when a new branch is created in a GitHub repository.
List Templates
Retrieves templates stored in the workspace.
Check Run Status / Conclusion Changed
Fires when a GitHub check run’s status or conclusion changes.
Set Carbone API Version
Sets the Carbone API version for subsequent requests.
Check Suite Status / Conclusion Changed
Fires when a GitHub check suite changes status or conclusion for a reference.
List Template Categories
Lists categories used to organize deployed Carbone templates.
New Code Scanning Alert Created
Fires when a new code scanning alert is created in a repository.
Upload a template
Uploads a template for document generation.
Connect any two apps with Notis in the middle.
GitHub and Carbone, or any other combination from 1,500+ integrations.
When this happens · Trigger
Do this · Action
Save your first hour today.
7-day trial of any paid plan, with $20 of usage included.
No card. Works with personal or business Carbone.