Know whether Carbone is ready for document generation
A quick scheduled health check can surface an availability issue before it interrupts a batch of important documents.
Trigger
Recurring schedule
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Action
Get Carbone Server Status
Tool to retrieve the current status and health of the carbone server. use before generating reports to ensure the service is operational.
Why this helps
Finding out that document generation is unavailable only after starting a time-sensitive task adds avoidable stress.
- See server health before planned document work.
- Reduce surprises during report preparation.
- Get run results in a channel you already check.
Setup
Build it in a few focused steps.
- 1Connect Carbone to Notis once in the portal.
- 2Create an automation with a plain-language instruction to check and summarize Carbone server health each workday.
- 3Select a Notis cron trigger and set the desired schedule.
- 4Choose a channel for run reports, then test with one manual run.
Questions about this workflow
Does this generate a report?
No. This workflow checks the Carbone server status and reports the result.
Can I schedule it less often?
Yes. Choose a recurring schedule that matches your document workload.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Carbone. A trigger fires from one place; an action lands in another.
Notion triggers
Carbone actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Delete Carbone Template
Tool to delete a template from the carbone server. use after confirming you have the correct template id.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Download Template
Tool to download a template from carbone by template id. use when you need to retrieve the original template file.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Generate Carbone Report
Tool to generate a carbone report from a template and json data. use when you need to render documents in various formats.
Comment Created
Triggers when a new comment is created in Notion. Optional `page_id` filter scopes to comments on a specific page. When omitted, fires for any new comment in the workspace the integration has access to. Requires the 'Read comments' capability on the Notion integration. If a connection was authorized before that capability was enabled, the user must re-authorize the connection for comment events to flow.
Generate Template ID
Tool to generate a unique template id for a new template. use when you need the template identifier before uploading.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Get Carbone Server Status
Tool to retrieve the current status and health of the carbone server. use before generating reports to ensure the service is operational.
Database Created
Triggers when a new Notion database (the container) is created. A database is the post-2025-09-03 container that holds one or more data sources. This trigger fires for the container's creation event (`database.created`), distinct from `NOTION_DATASOURCE_CREATED` which fires when a new data source is added to an existing database. Most customers calling Notion's `POST /v1/databases` (the legacy API) or creating a database via the Notion UI will see this event. Adding a new data source to an existing database fires `data_source.created` instead — use `NOTION_DATASOURCE_CREATED` for that. Notion's payload puts `entity.type: "block"` (the container is a `child_database` block in the content tree) and `entity.id` is the database id.
Set Carbone API Version
Tool to set the carbone api version to be used for subsequent requests. use before rendering or managing templates to ensure correct version is applied.
Data Source Created
Triggers when a new Notion data source is created. Fires workspace-wide. The payload's `data.parent` carries the data source's tree parent (typically the teamspace) for downstream filtering. A single template-based database creation can fire multiple `data_source.created` events at once — one per data source the template instantiates.
Upload a template
Tool to upload a template to the carbone server. use when you need to add or replace a template by providing its content.
Data Source Schema Updated
Triggers when a Notion data source's schema is updated. Fires on column add / remove / rename. Payload includes `data.updated_properties: [{id, name, action}]` so consumers can discriminate the kind of change downstream. Optional `data_source_id` filter scopes to schema changes on a single data source. When omitted, fires for any schema change in the workspace the integration has access to. Note: adding a column also fires `page.properties_updated` once per existing row in the data source. Customers wanting a single structural-change signal should use this trigger.
Connect any two apps with Notis in the middle.
Notion and Carbone, or any other combination from 1,000+ 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.