Skip to content
Notis

Check the price of a planned removal option on a schedule

Have Notis refresh an estimate for a specified method and amount at a cadence that fits your planning.

Trigger

Recurring schedule

Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.

Action

Get CDR Price

Tool to retrieve the cost of carbon dioxide removal. use after specifying cdr methods and amounts to estimate pricing.

Why this helps

When a plan spans several weeks, its price estimate can become stale while nobody remembers to revisit it.

  • Refresh a planned estimate on a dependable cadence.
  • Keep cost review from becoming a forgotten task.
  • Receive the estimate in a channel you already check.

Setup

Build it in a few focused steps.

  • 1Connect Notion and Cdr platform to Notis once in the portal.
  • 2Create an automation in Automations -> New Automation or ask Notis conversationally.
  • 3In one instruction, specify the planned removal method and amount and ask Notis to retrieve and report its price on a recurring basis.
  • 4Choose a recurring schedule and a channel for run reports.
  • 5Test one run and confirm the estimate matches the planning question.

Questions about this workflow

Can this read the current plan from Notion?

Use a prompt that identifies the relevant Notion planning context and gives Notis enough detail to request the estimate; a schedule is the trigger for this workflow.

Does it place a purchase?

No. It retrieves a price estimate only.

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.

TriggerScheduled

Get CDR Price

Tool to retrieve the cost of carbon dioxide removal. use after specifying cdr methods and amounts to estimate pricing.

ActionInstant

Webhook trigger

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

TriggerInstant

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.

ActionInstant

All Page Events

Triggers when any Notion page is created or updated across the workspace.

TriggerPolling

Get Pricing and Billing Info

Tool to get current pricing, fees, and billing thresholds for carbon removal. use when calculating costs before purchase.

ActionInstant

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.

TriggerInstant

Post CDR Purchase

Tool to initiate the purchase of carbon dioxide removal credits. use after confirming cost and methods to finalize the order.

ActionInstant

New Comment

Triggers when a new comment is added to a specified Notion block or page.

TriggerPolling

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.

TriggerInstant

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.

TriggerInstant

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.

TriggerInstant

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.