Start a Cody conversation for every new project brief
When a project brief is added to a Notion database, start a Cody conversation focused on the work so the founder can move from capture to clear next steps without rebuilding context.
When something happens in Notion, Notis takes the next step in Cody. Describe what you want in plain English, or start from one of the examples below.
When this happens · Trigger
Fires when a new comment is created in the accessible workspace.
Do this · Action
Starts a new conversation with a bot.
When a project brief is added to a Notion database, start a Cody conversation focused on the work so the founder can move from capture to clear next steps without rebuilding context.
When a Notion decision page is created, add its content to Cody as a document so important calls are easier to find and reuse later.
When meeting notes are edited, create a Cody conversation that helps the founder pull out decisions, open questions, and follow-ups from the updated context.
When a Notion comment arrives, start a Cody conversation that reviews the comment in its page context and helps clarify the requested response or follow-up.
When a task's Notion properties change, start a Cody conversation to help assess the updated context and identify a manageable next step.
When a new subpage is added beneath a project hub, add it to Cody's knowledge base to keep project context together and easier to search.
When a Notion view is created, open a Cody conversation to consider what work the view is meant to surface and whether its context is clear.
When a data source schema changes, start a Cody conversation to assess how the structural update affects the way the team captures and finds work.
When a new Notion data source is created, create a Cody folder to provide a place for related knowledge as the workspace grows.
Notis builds workflows that link Notion to Cody. A trigger fires from one place; an action lands in another.
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Starts a new conversation with a bot.
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Creates a text-based document in the knowledge base.
Fires when a new comment is created in the accessible workspace.
Creates a Cody knowledge-base document from an uploaded file.
Fires when a new database container is created.
Creates a knowledge base document from a public webpage.
Fires when a new data source is created in the workspace.
Creates a folder to organize documents or conversations.
Fires when a data source’s columns are added, removed, or renamed.
Permanently deletes a conversation.
Fires when the body content of an accessible page is updated.
Deletes a document.
Fires when a new page is created in the accessible workspace.
Retrieves details of a Cody conversation.
A trigger is the event that kicks a workflow off. Notis supports four kinds: an event in a connected app, an inbound webhook, a schedule (recurring or one-time), and a change in one of your Notis databases.
Fire when something happens inside a connected app. New Notion page, Stripe charge, Linear issue: any of 1,500+ apps can start a workflow.
A unique URL per workflow. Anything that can send an HTTP POST can start an automation, including no-code tools that speak webhooks.
Run a workflow on the clock, on a recurring schedule or once at a set date and time. Daily standups, hourly syncs, a one-off launch reminder: the workhorse of Notis.
Fire when a row in one of your Notis databases is added or edited, with optional filters on its properties. New lead added, status changed, value crosses a limit.
Same triggers and actions, smarter middle. AI handles the fuzziness that breaks traditional Zapier-style workflows the moment a field gets renamed.
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:
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.
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 monthWhatever starts the workflow, the platform underneath is the same: a thinking brain, full visibility, and you in control.
Every step can include an LLM call: summarise, classify, extract, rewrite.
Every run, every step, every input, all replay-able from Mission Control.
Pause for approval. Notis pings you in chat with one-tap approve.
When an API changes shape, Notis adapts the parser. Less midnight fire-fighting.
Notion and Cody, or any other combination from 1,500+ integrations.
When this happens · Trigger
Do this · Action
7-day trial of any paid plan, with $20 of usage included.
No card. Works with personal or business Cody.