Carry ownership decisions into project resourcing
When a person is named to own the work, make their involvement visible in the project plan.
Trigger
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Action
Add Resources to Project
Tool to add resources to a project by project ID. Use when you need to associate one or more resources with a specific project.
Why this helps
Ownership can be agreed in a comment but never reflected in the resourcing tool.
- Make ownership visible where project capacity is managed.
- Reduce manual handoff steps after a decision.
- Keep the original discussion available as context.
Setup
Build it in a few focused steps.
- 1Connect Notion and Hub Planner to Notis once through the portal; enable Notion comment access and re-authorize if needed.
- 2Create an automation for project ownership decisions.
- 3Write one prompt asking Notis to add a resource only when a comment clearly names an owner and the matching project is identifiable.
- 4Choose the Notion New Comment trigger for the relevant page or block, select a run-report channel, and test with one owner comment.
Questions about this workflow
Does this require comment permissions?
Yes. Comment triggers require Read comments access, and older connections may need re-authorization.
Will an ambiguous mention assign someone?
The prompt should tell Notis to act only on an explicit ownership decision and to report uncertain matches.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Hub Planner. A trigger fires from one place; an action lands in another.
Notion triggers
Hub Planner actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Add Clients to Project
Tool to add clients to a project by project ID. Use when you need to associate one or more clients with a specific project.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Add project custom field choices
Add choices to a project custom field template of SELECT, RADIO, or CHECKBOX type. Use when you need to add new options to an existing dropdown, radio button, or checkbox custom field in Hub Planner projects.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Add Projects to Group
Tool to add projects to a project group in Hub Planner. Use when you need to associate one or more projects with a specific project group.
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.
Add Project Tags
Tool to add tags to a Hub Planner project. Preserves existing tags and appends new ones. Use when you need to add one or more tags to a project without removing existing tags.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Add Resource Custom Field Choices
Tool to add choices to a resource custom field template of SELECT, RADIO, or CHECKBOX type. Use when you need to add new selection options to an existing custom field template.
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.
Add Resources to Project
Tool to add resources to a project by project ID. Use when you need to associate one or more resources with a specific project.
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.
Add Resources to Resource Group
Tool to add resources to a resource group by group ID. Use when you need to associate one or more resources with a specific resource group.
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.
Add Resource Tags
Tool to add tags to a resource in Hub Planner. Preserves existing tags and appends new ones. Use when you need to categorize, label, or organize resources using tags.
Connect any two apps with Notis in the middle.
Notion and Hub Planner, 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 Hub Planner.