Keep your versioned document template aligned with Carbone
If your team maintains a Carbone-compatible template in a GitHub repository, a change to that file can trigger an upload to Carbone. Notis retrieves the current file and updates the intended template, reducing drift between source and renderer.
Trigger
Repository Content Changed
Fires when a file or directory’s content changes in a GitHub repository.
Action
Upload a template
Uploads a template for document generation.
Why this helps
Maintaining one template in GitHub and another in the document renderer invites version drift and uncertainty about which copy is current.
- Use the repository as the maintained source for a selected template file.
- Update the corresponding Carbone template after monitored file changes.
- Reduce manual re-uploading and uncertainty over template versions.
Setup
Build it in a few focused steps.
- 1Connect GitHub and Carbone to Notis once, and confirm the target Carbone template identifier and repository file are the intended pair.
- 2Create an automation in the portal or by asking Notis; instruct it to retrieve the changed file from GitHub and upload its content to replace the specified Carbone template.
- 3Choose the repository content changed trigger for the exact file path and branch, and select a channel for run reports.
- 4Test with a reviewed template change and verify the Carbone template was updated as intended.
Questions about this workflow
Does the GitHub change event include the full file contents?
The trigger description guarantees change events and file metadata, not the complete file contents. The prompt should have Notis retrieve the current file from GitHub before using Carbone's upload-template action.
Can this publish every edit straight to Carbone?
The upload action can add or replace a template. Restrict the trigger to the intended path and branch, and use a reviewed source file because the workflow updates the specified Carbone template.
When this happens · Trigger
Fires when a file or directory’s content changes in a GitHub repository.
Do this · Action
Uploads a template for document generation.
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.