Skip to content
Notis

Connect Coda to Control d

When something happens in Coda, Notis takes the next step in Control d. Describe what you want in plain English, or start from one of the examples below.

When this happens · Trigger

Do this · Action

Examples

Ways Notis can move work from Coda to Control d

View example

Provision a Control D profile from a new Coda project document

Create a Control D profile whenever a new Coda project document appears, using the document brief to name and describe it.

View example

Create Control D rules from a new Coda security page

Translate a newly added Coda security page into reviewed custom rules for a chosen Control D profile.

View example

Update Control D custom rules when a Coda policy page changes

Review a changed Coda policy page and modify matching Control D custom rules while reporting conflicts.

View example

Bulk update Control D filters from a changed Coda filtering policy

Apply clearly stated filter enable or disable changes from an updated Coda page to a Control D profile.

View example

Create a Control D schedule from a new Coda maintenance page

Create a profile schedule in Control D when a Coda page documents a recurring maintenance window.

View example

Update a Control D schedule when its Coda maintenance page changes

Update an existing Control D schedule from a changed Coda maintenance page after identifying the profile and schedule.

View example

Update a Control D service rule from a changed Coda service policy

Apply explicit service blocking, bypass, spoofing, or redirect decisions from an updated Coda page.

View example

Create a Control D device from a new Coda device request

Provision a Control D device when a new Coda document contains a complete device request and resolver context.

View example

Remove an unused Control D profile when its Coda document is deleted

Delete a Control D profile after a Coda document deletion when the document mapping and enforcement checks are explicit.

Supported Triggers and Actions

Notis builds workflows that link Coda to Control d. A trigger fires from one place; an action lands in another.

Coda triggers

Control d actions

Recurring trigger

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

TriggerScheduled

Delete Device by ID

Tool to delete a Control-D device. Use when you need to remove a device by its identifier after confirming the device_id.

ActionInstant

Webhook trigger

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

TriggerInstant

Delete Profile by ID

Tool to delete a profile. Use when you need to remove a profile by its ID after ensuring it is not enforced by any device.

ActionInstant

Coda Document Deleted Trigger

Triggers when a Coda document is deleted.

TriggerPolling

Delete Profile Rule by Hostname

Tool to delete a specific custom rule by hostname from a profile. Use after confirming profile_id and hostname.

ActionInstant

New Coda Document Trigger

Triggers when a new Coda document is created.

TriggerPolling

Delete Profile Rule by Rule ID

Tool to delete a specific custom rule by its ID within a profile. Use after confirming profile_id and rule_id.

ActionInstant

New Coda Page Trigger

Triggers when a new page is added to a Coda document.

TriggerPolling

Delete Profile Rule in Folder

Tool to delete a specific custom rule within a folder. Use after confirming profile_id, rule_id, and folder_id.

ActionInstant

Specific Coda Page Updated Trigger

Triggers when a specific page within a Coda document is updated.

TriggerPolling

Delete Profile Schedule

Tool to delete a specific schedule within a profile. Use after confirming profile_id and schedule_id.

ActionInstant

List Known Access IPs

Tool to list known IPs associated with the account. Use when you need to retrieve recent access IPs for device resolver queries.

ActionInstant

Get Analytics Endpoints

Tool to list analytics storage regions and their endpoints. Use after authenticating to retrieve available analytics regions.

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.

Notis

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.

  • 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

All12Manager5Telegram1Messages0Whatsapp2Email4Slack8

Migrate background jobs to a durable queue You can cancel it through Stripe

3 days

Notis v3 release update This one’s v3: Notis Manager (desktop app with …

8 days

Add multi-tenant RBAC User initiates a voice call

13 days

Draft pricing v (tiers, limits, overages) and sanity-check margins

2 weeks

Verify analytics events for new features That’s a really interesting automat…

1 month

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

Related pairs

More ways to connect Coda and Control d

Connect any two apps with Notis in the middle.

Coda and Control d, 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 Control d.