Check Bugsnag access when the on-call roster changes
A roster change can remind you to look at who currently has Bugsnag access before the next incident handoff.
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
List Collaborators
Tool to list collaborators in an organization. use when you need to retrieve all collaborators for a specified organization. example: "list collaborators for organization 515fb9337c1074f6fd000001".
Why this helps
Team changes create access review tasks that can fall behind when they are handled separately from the roster update.
- Prompt an access review as the roster changes.
- See current collaborators in a run report without a separate search.
- Keep security housekeeping attached to an operational handoff.
Setup
Build it in a few focused steps.
- 1Connect Notion and Bugsnag to Notis once in the portal.
- 2Create an automation in the portal or ask Notis conversationally.
- 3Write one instruction describing which on-call roster changes should prompt a Bugsnag collaborator list.
- 4Choose the Notion Page Properties Updated trigger for the roster data source and select a run-report channel.
- 5Test with one real roster update and review the collaborator list.
Questions about this workflow
Does this add or remove collaborators?
No. It lists collaborators so you can review access. Invite and removal actions require separate explicit workflows.
Can it run for only the roster database?
Yes. Scope the property update trigger to the roster's data source.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Bugsnag. A trigger fires from one place; an action lands in another.
Notion triggers
Bugsnag actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Bulk Update Errors
Tool to bulk update multiple errors in a project. use when batching identical updates across many errors.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Configure Integration
Tool to configure a new integration for a bugsnag project. use after selecting integration key and preparing credentials.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Invite Collaborator
Tool to invite a collaborator to an organization. use when you need to add a new user by email to grant them access. ensure the organization id is correct before calling.
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 Custom Event Field
Tool to create a custom event field for a project. use after confirming the project id to add a new filterable field. example: "create a field 'user.id' mapping to 'metadata.user.id' for project 515fb..."
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Create Saved Search
Tool to create a new saved search for a project. use when you need to persist a set of filters and sort order as a saved search for a project after confirming project details.
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.
Delete All Errors in a Project
Tool to delete all errors in a project. use when you need to remove all error and event data for a given project. use with caution after confirming the project id, as this action is irreversible and requires project owner or organization administrator permissions.
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.
Delete Collaborator
Tool to remove a collaborator from an organization. use when revoking collaborator access after confirming both organization and collaborator ids. requires organization administrator privileges.
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.
Delete a configured integration
Tool to delete a configured integration. use when you need to remove an existing integration from a project after confirming the integration id. this action cannot be undone and requires organization administrator or project owner permissions.
Connect any two apps with Notis in the middle.
Notion and Bugsnag, 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 Bugsnag.