Connect 0CodeKit to Cdr platform

When something happens in 0CodeKit, 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

Build an automation Browse examples

Examples

Ways Notis can move work from 0CodeKit to Cdr platform

View example

Estimate carbon removal price from an intake request

Receive a project request by webhook and return an estimated price for the stated removal method and amount.

View example

Check current billing terms before setting a removal budget

Use a webhook request to retrieve current Cdr platform pricing, fees, and billing thresholds for budget planning.

View example

Verify Cdr platform health before a sustainability report

Run a service health check from a webhook before starting a reporting workflow or stakeholder update.

View example

Purchase approved carbon removal credits from a webhook

Turn a confirmed purchase request into a Cdr platform order after the method, amount, and approval are supplied.

View example

Run a daily Cdr platform readiness check

Check Cdr platform service and database connectivity on a schedule and report any issue before work begins.

View example

Review Cdr platform pricing and billing every week

Retrieve current fees, pricing, and billing thresholds on a weekly schedule for finance and sustainability planning.

View example

Watch weekly carbon removal prices

Retrieve a scheduled price estimate for a specified method and amount and summarize the result for planning.

View example

Run a scheduled approved removal purchase

Initiate a planned CDR purchase on a schedule when the automation instruction contains confirmed order details and approval.

View example

Compare price estimates for two removal scenarios

Accept a planning request by webhook and retrieve price estimates for the scenarios named in the request.

Supported Triggers and Actions

Notis builds workflows that link 0CodeKit to Cdr platform. A trigger fires from one place; an action lands in another.

0CodeKit 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

Get Pricing and Billing Info

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

ActionInstant

Post CDR Purchase

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

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 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.

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

Recurring triggers

Cron-style schedules run a workflow on the clock. Daily standups, hourly syncs, business-hours-only digests: the workhorse of Notis.

Daily · 8:00HourlyWeekdays only

Coming soon

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.

Row insertedValue > limitQuery match

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.