Check CDR service health when a project starts
Run a service health check as you open the project, then see the status in your chosen channel.
Trigger
Page Created
Triggers when a new Notion page is created. Customer optionally scopes with at most one of: - data_source_id: new row in this data source - parent_page_id: new sub-page under this page (immediate parent only) With neither set, fires for any new page in the workspace the integration has access to. Notion sends ~60s aggregation latency on most events.
Action
Get Health Check
Tool to perform a health check of the cdr platform service. use when you need to verify api and database connectivity and core service status.
Why this helps
A service issue discovered during a time-sensitive task can create unnecessary uncertainty and interruptions.
- See service and database status at the start of a project.
- Catch connectivity issues before planning depends on the service.
- Get the check result in your normal reporting channel.
Setup
Build it in a few focused steps.
- 1Connect Notion and Cdr platform to Notis once in the portal.
- 2Create an automation in the portal or ask Notis conversationally.
- 3Use one instruction to run the CDR health check when a new carbon removal project page is created and report its status.
- 4Select Page Created and scope it to the carbon removal project parent page.
- 5Choose a channel for run reports and test with one real project page.
Questions about this workflow
What does the health check verify?
It checks the CDR service, API and database connectivity, and core service status.
Can it purchase credits if the service is healthy?
No. This workflow only runs the health check.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Cdr platform. A trigger fires from one place; an action lands in another.
Notion triggers
Cdr platform actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Get CDR Price
Tool to retrieve the cost of carbon dioxide removal. use after specifying cdr methods and amounts to estimate pricing.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Get Health Check
Tool to perform a health check of the cdr platform service. use when you need to verify api and database connectivity and core service status.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Get Pricing and Billing Info
Tool to get current pricing, fees, and billing thresholds for carbon removal. use when calculating costs before purchase.
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.
Post CDR Purchase
Tool to initiate the purchase of carbon dioxide removal credits. use after confirming cost and methods to finalize the order.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
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.
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.
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 Cdr platform, 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 Cdr platform.