Keep Nozbe tasks aligned with Notion changes
A changed priority or status in Notion can cue Notis to refresh the corresponding Nozbe task, keeping the team oriented around the current plan.
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 Task
Tool to update a task in Nozbe Teams. Use when you need to modify task properties such as name, project, responsible user, due date, or other attributes. All fields except the task ID are optional - only provide fields you want to update.
Why this helps
Teams can act on stale task information when a priority or status changes in Notion but is not carried into execution.
- Makes important plan changes visible where work is tracked.
- Reduces the chance of acting on outdated task details.
- Avoids repeatedly notifying teammates by hand.
Setup
Build it in a few focused steps.
- 1Connect Notion and Nozbe Teams to Notis once in the portal.
- 2Describe in one plain-language prompt which Notion property changes should update the related Nozbe task.
- 3Select Page Properties Updated for the relevant data source and choose a run-report channel.
- 4Change a real item's priority or status and verify the matching task update.
Questions about this workflow
Can this trigger on a particular database?
Yes. Page Properties Updated supports an optional data source filter.
Will every property update need a task change?
Use the prompt to explain which changes matter and what Notis should do for each relevant update.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Nozbe Teams. A trigger fires from one place; an action lands in another.
Notion triggers
Nozbe Teams actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Create Attachment
Tool to add attachment metadata to a comment. Use when you need to create attachment metadata for a file associated with a comment. This creates the metadata record; actual file upload may be a separate step depending on the workflow.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Create Comment
Tool to add a comment to a task in Nozbe Teams. Use when you need to add feedback, notes, or updates to a specific task.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Create Project Section
Tool to create a new project section in Nozbe Teams. Use when you need to add a section to organize tasks within a project.
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.
Create Reminder
Tool to add a reminder to a task in Nozbe Teams. Use when you need to set up a notification for a specific task at a given time.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Create Tag Assignment
Tool to add a tag assignment to a task. Use when you need to tag or label a task for organization or categorization purposes.
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.
Create Task
Tool to create a new task in Nozbe Teams. Use when you need to add a task to a project or personal task list. Only the task name is required; all other fields are optional.
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.
Create Team Member
Tool to add a team member in Nozbe Teams. Use when you need to add an existing user to a team with a specific role and status. The user must already exist in the system before they can be added to a team.
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.
Create User
Tool to create a new placeholder user in Nozbe Teams. Use when you need to add a placeholder user to the system. Note: Only placeholder users can be created via API - attempting to create non-placeholder users will fail with a 400 error.
Connect any two apps with Notis in the middle.
Notion and Nozbe Teams, 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 Nozbe Teams.