Keep project scope aligned across tools
Make an agreed scope decision easier to act on by carrying it from the Notion record into the matching Moco project.
Trigger
Page Properties Updated
Triggers when properties of a Notion page are updated. Customer optionally scopes with at most one of: - data_source_id: any row in this data source - page_id: this specific page - parent_page_id: any page whose immediate parent is this page With none set, fires for any property change in the workspace the integration has access to. Adding a column to a data source fires this trigger once per existing row. Customers can branch on `data.updated_properties` (array of property IDs) to filter downstream.
Action
Update Project
Tool to update an existing project. use when you need to modify project details after confirming the project id.
Why this helps
Scope decisions can get buried in notes while the project record still describes the old plan.
- Keep project context current after a decision.
- Reduce reliance on remembering a second update.
- Make handoffs clearer for collaborators.
Setup
Build it in a few focused steps.
- 1Connect Notion and Moco to Notis once through the portal.
- 2Create an automation in Automations or describe the workflow to Notis conversationally.
- 3Write one instruction to update the matching Moco project when a Notion project record documents an agreed scope change.
- 4Choose the Notion Page Properties Updated trigger and the channel for run reports.
- 5Test with one agreed change and review the updated project.
Questions about this workflow
Can this distinguish a proposal from an agreed change?
Tell Notis what wording or project status indicates approval, and have it ask for review when the decision is unclear.
Does it update project descriptions?
Ask for the specific project detail to be updated in plain language and verify the result with a real example.
When this happens · Trigger
Do this · Action
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.
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.