Find project experts from a new Notion subpage
Describe the missing expertise in the subpage and let Orbit find people who may be able to help.
Trigger
Page Added to Page
Fires when a new subpage (a `child_page` type block) is added under a specified parent Notion page.
Action
Find People
Find people from a description, criteria or identity signals, with source-backed context.
Why this helps
A project can stall when locating the right specialist becomes an unplanned research task.
- Start research from the project context itself.
- Find people based on the expertise the work actually needs.
- Keep the search connected to the project hub.
Setup
Build it in a few focused steps.
- 1Connect Notion and Orbit to Notis once through the portal.
- 2Create the automation in the portal or tell Notis what it should accomplish.
- 3Write one instruction asking Orbit to find people whose expertise matches each new project subpage.
- 4Select the Notion Page Added to Page trigger for the relevant project hub and choose a report channel.
- 5Test with one subpage describing a real expertise gap.
Questions about this workflow
What should the subpage describe?
State the expertise needed and any relevant industry, experience, or identity clues that would make someone a fit.
Does Orbit select or hire the expert?
No. Orbit finds people and provides context for your review.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Orbit. A trigger fires from one place; an action lands in another.
Notion triggers
Orbit actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Find People
Find people from a description, criteria or identity signals, with source-backed context.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Read Person Profile
Read the stored profile for one person: identity, contacts, history, sections, sources.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Batch Enrich Profiles
Build up to 20 people's profiles to partial or full depth in one call.
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.
Enrich Person Profile
Build one person's profile to partial or full depth from live web and public sources.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
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.
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.
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.
Connect any two apps with Notis in the middle.
Notion and Orbit, 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 Orbit.