Connect Notion to Cdr platform
When something happens in Notion, Notis takes the next step in Cdr platform. Describe what you want in plain English, or start from one of the examples below.
When this happens · Trigger
Do this · Action
Ways Notis can move work from Notion to Cdr platform
Estimate a carbon removal budget
When a new Notion sustainability task calls for an estimate, check the CDR cost for the stated method and amount and report the result for review.
Price a removal idea from a comment
When a Notion comment asks for a carbon removal price and gives a method and amount, retrieve an estimate and share it for follow-up.
Refresh an estimate after a plan changes
When the content of a scoped Notion planning page changes, check the revised carbon removal method and amount against CDR pricing.
Reprice a changed removal quantity
When properties on a scoped Notion budget record change, retrieve a new estimate if the method or amount has been revised.
Check billing details from a Notion discussion
When a Notion comment asks about fees or billing thresholds, retrieve current CDR pricing and billing information and report the relevant details.
Review billing as a sustainability project starts
When a new Notion sustainability project page is created, retrieve CDR billing information so budget constraints are visible early.
Check billing for a new removal plan
When a new Notion plan is added to a carbon removal database, retrieve CDR fees and billing thresholds for planning.
Check CDR service before project kickoff
When a Notion carbon removal project page is created, check CDR service and database connectivity and report the status.
Check CDR health after setting up a planning data source
When a Notion data source is created, run a CDR health check and report whether the service and database are reachable.
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.
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 recurring schedule, and soon, your own database.
Integration triggers
Fire when something happens inside a connected app. New Notion page, Stripe charge, Linear issue: any of 1,000+ apps can start a workflow.
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.
Recurring triggers
Cron-style schedules run a workflow on the clock. Daily standups, hourly syncs, business-hours-only digests: the workhorse of Notis.
Database triggers
Watch a row, query, or threshold in your own database and fire the moment the data changes. Row inserted, value crosses a limit, query starts matching.
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.
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:
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.
- Full run history with inputs, outputs and traces
- Replay any run with edited inputs
- Approval inbox, confirm via chat in one tap
- Audit logs for compliance teams
Automations
Inbox
Migrate background jobs to a durable queue You can cancel it through Stripe
3 daysNotis v3 release update This one’s v3: Notis Manager (desktop app with …
8 daysAdd multi-tenant RBAC User initiates a voice call
13 daysDraft pricing v (tiers, limits, overages) and sanity-check margins
2 weeksVerify analytics events for new features That’s a really interesting automat…
1 monthEverything in the box.
Whatever starts the workflow, the platform underneath is the same: a thinking brain, full visibility, and you in control.
AI in the middle
Every step can include an LLM call: summarise, classify, extract, rewrite.
Full observability
Every run, every step, every input, all replay-able from Mission Control.
Human in the loop
Pause for approval. Notis pings you in chat with one-tap approve.
Self-healing
When an API changes shape, Notis adapts the parser. Less midnight fire-fighting.
More ways to connect Notion and Cdr platform
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.