Connect Notion to Hub Planner
When something happens in Notion, Notis takes the next step in Hub Planner. 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 Hub Planner
Turn a Notion project brief into a Hub Planner project
When a project brief is added to Notion, have Notis create a corresponding project in Hub Planner so planning starts without re-entering the basics.
Create Hub Planner milestones from Notion deliverables
When a dated deliverable is created in Notion, ask Notis to add a matching milestone to the appropriate Hub Planner project.
Book project time when a Notion task becomes a priority
When Notion task properties change to signal committed work, have Notis create a Hub Planner booking for the relevant resource and project.
Log completed Notion work in Hub Planner
When a work log is added to a Notion page, have Notis create a corresponding Hub Planner time entry from the reported work.
Reserve recovery time when a Notion comment flags a blocker
When a comment flags blocked work and an agreed recovery slot, have Notis create a Hub Planner booking for the follow-up.
Add new client intake to Hub Planner
When a new Notion client intake page appears, have Notis create the matching client record in Hub Planner.
Label Hub Planner projects when Notion status changes
When a Notion project status changes, have Notis add a matching status tag to the corresponding Hub Planner project.
Track client commitments as Hub Planner milestones
When a new Notion page records a dated client commitment, have Notis create a milestone on its Hub Planner project.
Create Hub Planner resources from contractor onboarding pages
When a contractor onboarding subpage is added in Notion, have Notis create a corresponding Hub Planner resource record.
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.
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 Hub Planner
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.