Connect GitHub to Carbone

When something happens in GitHub, Notis takes the next step in Carbone. Describe what you want in plain English, or start from one of the examples below.

When this happens · Trigger

Fires when a new GitHub Actions workflow artifact is created in a repository.

Do this · Action

Deletes a Carbone template or version; the file is removed after a storage retention delay.

Build an automation Browse examples

Examples

Ways Notis can move work from GitHub to Carbone

View example

Generate a release brief when a GitHub release is published

Turn a GitHub release update into a consistent Carbone-rendered release brief using its title, notes, tag, and publication details.

View example

Create a Carbone deployment report from GitHub status updates

Render a deployment record from GitHub deployment status changes, keeping the environment, state, description, links, and timing together.

View example

Turn GitHub code scanning alerts into Carbone security reports

Render a focused security finding report when GitHub creates a code scanning alert, including its rule, severity, tool, and location details.

View example

Keep a Carbone template in sync with its GitHub source file

When a designated file changes in GitHub, upload its current content to Carbone so a version-controlled document template stays aligned.

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.

TriggerScheduled

Delete Carbone Template

Deletes a Carbone template or version; the file is removed after a storage retention delay.

ActionInstant

Webhook trigger

Notis starts this workflow when an external tool or custom backend sends an HTTP request.

TriggerInstant

Download Template

Downloads the original template file.

ActionInstant

New Workflow Artifact Created

Fires when a new GitHub Actions workflow artifact is created in a repository.

TriggerPolling

Generate Carbone Report

Generates a report from a Carbone template and JSON data, and returns its render ID.

ActionInstant

Branch Changed

Fires when a branch’s commits or protection status or settings change.

TriggerPolling

Get Carbone Server Status

Checks the server’s current status and health.

ActionInstant

New Branch Created

Fires when a new branch is created in a GitHub repository.

TriggerPolling

List Templates

Retrieves templates stored in the workspace.

ActionInstant

Check Run Status / Conclusion Changed

Fires when a GitHub check run’s status or conclusion changes.

TriggerPolling

Set Carbone API Version

Sets the Carbone API version for subsequent requests.

ActionInstant

Check Suite Status / Conclusion Changed

Fires when a GitHub check suite changes status or conclusion for a reference.

TriggerPolling

List Template Categories

Lists categories used to organize deployed Carbone templates.

ActionInstant

New Code Scanning Alert Created

Fires when a new code scanning alert is created in a repository.

TriggerPolling

Upload a template

Uploads a template for document generation.

ActionInstant

Trigger Types

Four ways to start an automation.

A trigger is the event that kicks a workflow off. Notis supports four kinds: an event in a connected app, an inbound webhook, a schedule (recurring or one-time), and a change in one of your Notis databases.

Integration triggers

Fire when something happens inside a connected app. New Notion page, Stripe charge, Linear issue: any of 1,500+ apps can start a workflow.

New Notion pageStripe chargeCalendar event

Webhook triggers

A unique URL per workflow. Anything that can send an HTTP POST can start an automation, including no-code tools that speak webhooks.

Any HTTP POSTCustom backendIoT event

Works with

ZapierPipedream

Most used

Scheduled triggers

Run a workflow on the clock, on a recurring schedule or once at a set date and time. Daily standups, hourly syncs, a one-off launch reminder: the workhorse of Notis.

Daily · 8:00Weekdays onlyOnce · Dec 13

Beta

Database triggers

Fire when a row in one of your Notis databases is added or edited, with optional filters on its properties. New lead added, status changed, value crosses a limit.

Row addedProperty editedValue > limit

Why AI automation

Classic automation breaks. AI adapts.

Same triggers and actions, smarter middle. AI handles the fuzziness that breaks traditional Zapier-style workflows the moment a field gets renamed.

Classic automationAI automation

Cost

$ · pay per run

$$ · AI models per run

Reliability

Breaks on schema change

Adapts to format changes

Setup

Click 8 dropdowns

Describe it in English

Handles fuzzy

Hard-coded fields only

Reads intent, summarises

Human in loop

Bolted on

Built in · approval inbox

Maintenance

You own every break

Self-heals · we own it

Ease of use

Describe it. Notis builds it.

Skip the visual builder. Tell Notis what you want, in plain English. It writes the workflow, you review and deploy.

You · in the Notis Builder

NEW

“When a row gets added to the Q4 OKRs Notion database and the status is Blocked, send a Telegram message to the owner with a summary of what's blocking, and ping me if there's no reply within 24 hours.”

Notis built this automation:

TriggerRow added to "Q4 OKRs"

Condition✦Status = "Blocked"

AI step✦Summarise the blocker in plain English

ActionDM the row owner with summary

Timeout✦No reply in 24h → ping you

Observability

Watch every run.

Notis Desktop is Mission Control for your AI automations. See every run, replay, edit, or rewind. Set approval gates so Notis pauses before destructive actions.