Run a Bugbug check when a milestone is completed
Close the milestone with a check on the work that just shipped, so validation does not become another loose end.
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
Run test
Execute a test in bugbug and return the test run details. this action allows you to run a specific test with optional configuration for browser, device, viewport, and variable overrides. it returns detailed information about the test run including step-by-step execution status.
Why this helps
Completed milestones can feel finished before the related quality check is actually done.
- Add a validation step to milestone closeout.
- Reduce open loops between marking work complete and checking it.
- Get a short result report without starting another manual search.
Setup
Build it in a few focused steps.
- 1Connect Notion and Bugbug to Notis once in the portal.
- 2Create the automation in the portal or ask Notis conversationally.
- 3Write one prompt asking Notis to identify and run a relevant existing Bugbug test when a milestone is completed, then summarize the result.
- 4Select the Notion Page Properties Updated trigger for the milestone data source and choose a reporting channel.
- 5Test with one completed milestone and review the test selection and outcome.
Questions about this workflow
Will it run for every completed milestone?
The prompt can ask Notis to act only when the completed milestone involves testable software work and a suitable test exists.
Does it create a milestone report?
It reports the Bugbug run result through the channel selected in the automation.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Bugbug. A trigger fires from one place; an action lands in another.
Notion triggers
Bugbug actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Get test run details
Get detailed information about test runs from bugbug. this action retrieves test run details with optional filtering parameters.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
List suites
List all available test suites in the bugbug platform. this tool makes a get request to the /suites/ endpoint and returns a list of available test suites with pagination support.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
List tests
Retrieves a list of all available tests in the bugbug account. this action provides access to all tests in the account with pagination support. it returns basic information about each test including its id, name, description, and timestamps.
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.
Run test
Execute a test in bugbug and return the test run details. this action allows you to run a specific test with optional configuration for browser, device, viewport, and variable overrides. it returns detailed information about the test run including step-by-step execution status.
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 Bugbug, 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 Bugbug.