Move project decisions into delivery
A clear go-ahead can become a working Moco project without leaving the next setup step to memory.
Trigger
Page Created
Triggers when a new Notion page is created. Customer optionally scopes with at most one of: - data_source_id: new row in this data source - parent_page_id: new sub-page under this page (immediate parent only) With neither set, fires for any new page in the workspace the integration has access to. Notion sends ~60s aggregation latency on most events.
Action
Create Project
Tool to create a new project in moco. use when you need to provision a project with validated parameters.
Why this helps
Approved work can sit idle after the decision because no one has time to repeat the setup details.
- Shorten the gap between approval and project setup.
- Keep the project decision linked to delivery work.
- Call out missing setup context early.
Setup
Build it in a few focused steps.
- 1Connect Notion and Moco to Notis once through the portal.
- 2Create an automation in the portal or ask Notis conversationally.
- 3Write one instruction to create a Moco project only when a new Notion page records a clear go-ahead, and report missing essentials.
- 4Choose the Notion Page Created trigger and a channel for run reports.
- 5Test with one real approved project page and review the new project.
Questions about this workflow
How does it know that work is approved?
Describe the approval signal clearly in the prompt and tell Notis to flag uncertain cases for review.
Can it create a project without a full brief?
Set the instruction to create only when required details are present and otherwise report what is missing.
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.