Keep deployment status and handoff details in one report
When GitHub records a deployment status, Notis can pass its status details into a Carbone template. Keep a dependable record of what changed without rebuilding the same handoff document each time.
Trigger
New Deployment Status Created
Fires when a new status is created for a GitHub deployment.
Action
Generate Carbone Report
Generates a report from a Carbone template and JSON data, and returns its render ID.
Why this helps
Deployment updates arrive amid other engineering notifications, and reconstructing the final state later means hunting through statuses, descriptions, and links.
- Capture the deployment status, environment, description, relevant URLs, and timestamps in one rendered report.
- Create a consistent handoff record for deployment transitions that matter to your team.
- Avoid manually collecting details across multiple GitHub deployment updates.
Setup
Build it in a few focused steps.
- 1Connect GitHub and Carbone to Notis once and prepare a Carbone template for deployment records.
- 2In Automations → New Automation, write a plain-language prompt to create a report for the deployment status transitions your team wants recorded; you can also ask Notis to set it up in conversation.
- 3Select the new deployment status trigger for the relevant deployment and choose where run reports should be delivered.
- 4Test using a real status update and check that the rendered report reflects the GitHub status, environment, description, links, and timestamps.
Questions about this workflow
Can I make a report only for successful deployments?
The event includes deployment status states such as success, failure, in progress, and queued. State the desired condition in the Notis prompt so the report is generated only for the transitions you intend to record.
Does this trigger monitor every deployment?
It monitors a specific deployment. Configure the GitHub trigger for the deployment you want to follow.
When this happens · Trigger
Fires when a new status is created for a GitHub deployment.
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.