Keep issue updates in sync
When an issue changes in Notion, have Notis update its Bugherd task so the next step stays visible.
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 a project. use after confirming the project and task ids.
Why this helps
Maintaining the same issue status in two places adds mental overhead and makes stale work harder to spot.
- Reduce repeated status edits across tools.
- Make meaningful changes easier for task owners to notice.
- Keep a familiar Notion overview connected to execution.
Setup
Build it in a few focused steps.
- 1Connect Notion and Bugherd to Notis once in the portal.
- 2Create an automation in the portal or ask Notis conversationally.
- 3Describe in one instruction how a changed Notion issue should update its matching Bugherd task.
- 4Pick Notion's Page Properties Updated trigger and choose a report channel.
- 5Test by changing one real issue and checking its Bugherd task.
Questions about this workflow
Can I limit the automation to issue pages?
Describe the issue pages and the meaningful changes in your plain-language instruction.
Does Notis need a field-mapping screen?
No. Explain the intended update in the instruction, and Notis interprets the available context.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Bugherd. A trigger fires from one place; an action lands in another.
Notion triggers
Bugherd actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Add Guest to Project
Tool to add a guest (client) to a project. use when you want to add an existing client by id or invite a new client by email.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Add Member to Project
Tool to add a member to a project in bugherd. use when you need to add an existing user to a specific project.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Create Attachment
Tool to add a new attachment to a task using an existing url. use when you have project and task ids and the external file url ready.
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 Column
Tool to create a new column in a project. use when you need to add a custom workflow column after identifying the project id.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Create Comment
Tool to add a new comment to a task. use when you need to record discussion or feedback on an existing task.
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 Project
Tool to create a new project. use when you need to initialize a project after gathering its name and url. example: "create a new project named 'my website' with url 'http://www.example.com'."
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 Task
Tool to add a new task in a project. use when you have the project id and full task details ready.
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 Webhook
Tool to create a new webhook for real-time event notifications. use when you need to configure a callback endpoint for task or comment events. example: "create a webhook for 'task create' events to be sent to 'https://example.com/webhook'."
Connect any two apps with Notis in the middle.
Notion and Bugherd, 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 Bugherd.