Get current Bugsnag event context from an incident comment
Ask for evidence in the incident discussion, then have Notis retrieve the relevant Bugsnag events for your review.
Trigger
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.
Action
List Events on Project
Tool to list events for a project. use when you need to retrieve all error occurrences (events) for a given project after confirming its id. example: "list events for project 515fb9337c1074f6fd000003".
Why this helps
Incident discussion and event evidence live in different tools, so gathering context interrupts the conversation.
- Start an event lookup directly from an incident discussion.
- See recent event evidence in a run report without a separate manual search.
- Keep the request attached to the page conversation that prompted it.
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 to set it up.
- 3Write one instruction describing how a new incident comment should prompt a relevant Bugsnag event lookup.
- 4Select the Notion Comment Created trigger, optionally scoped to the incident page, and choose a run-report channel.
- 5Test by adding a real comment that requests event context and reviewing the returned report.
Questions about this workflow
Does this trigger need Notion comment access?
Yes. The Notion integration needs the Read comments capability. If enabled after authorization, reauthorize the connection.
Can the trigger listen on one page?
Yes. The Comment Created event can be scoped to a specific page.
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.