Connect Notion to Moco
When something happens in Notion, Notis takes the next step in Moco. 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 Moco
Turn approved client briefs into Moco projects
When a new client project brief appears in Notion, create a corresponding project in Moco using the details provided and report anything essential that is missing.
Carry Notion project status changes into Moco
When project properties change in Notion, update the matching Moco project details or status according to the instruction you give Notis.
Turn client commitments into Moco planning entries
When a new Notion task or commitment includes a clear client project and planned effort, ask Notis to create a Moco planning entry for it.
Reflect scope decisions in Moco projects
When a Notion project record marks an agreed scope change, ask Notis to update the corresponding Moco project details so delivery context stays aligned.
Review Moco deals when a Notion lead is added
When a new lead page appears in Notion, have Notis check Moco deals for a likely match and summarize the existing pipeline context for follow-up.
Update Moco deal stage from a Notion decision
When a Notion lead record reflects a confirmed sales-stage decision, have Notis update the matching Moco deal and report the change.
Check Moco invoices for a new billing note
When a new Notion billing note is added, have Notis list relevant Moco invoices and summarize their statuses for the client or project.
Prepare Moco invoices from approved Notion billing records
When a Notion billing record is marked ready and includes complete invoice details, have Notis create the corresponding Moco invoice and flag anything incomplete.
Reserve capacity for a new client commitment
When a new Notion commitment specifies a client project and a realistic time allocation, have Notis create a Moco planning entry to reserve capacity.
Supported Triggers and Actions
Notis builds workflows that link Notion to Moco. A trigger fires from one place; an action lands in another.
Notion triggers
Moco actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
List Activities
Tool to retrieve activities. use when you need to list time entries with filters like date range, user, project, or billing status.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Get Activity
Tool to retrieve a single activity by id. use when you need to fetch details for a specific activity after confirming the activity id.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Update Activity
Tool to update an existing activity. use when you need to adjust details of a recorded time entry after confirming the activity exists.
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.
List comments
Tool to retrieve a list of comments. use after confirming the resource type and id.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Create Company
Tool to create a new company. use when you need to add a company after gathering required fields.
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.
Delete a company
Tool to delete a company. use when you need to remove a company from moco after confirming no active dependencies.
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.
List Contacts
Tool to retrieve a list of contacts. use when you need to list contacts optionally filtered by tags, term, or phone after confirming criteria.
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.
List Deal Categories
Tool to list deal categories with their ids and probabilities. use when you need a reference of available deal category types after authenticating.
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 Moco
Connect any two apps with Notis in the middle.
Notion and Moco, 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 Moco.