Skip to content
Notis

Set up a matching Bugsnag review search

When a bug tracking source is added in Notion, ask Notis to create a Bugsnag saved search for the review your team needs.

Trigger

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.

Action

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.

Why this helps

Adding a new tracking source often creates another manual setup task that gets delayed or forgotten.

  • Turn a new bug tracking source into a prompt to set up a review search.
  • Reduce the chance that a new process launches without useful saved filters.
  • Capture the intended search routine in the automation prompt.

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.
  • 3In one instruction, state when a new Notion data source warrants a Bugsnag saved search and describe the intended search criteria in plain language.
  • 4Choose the Notion Data Source Created trigger and a channel for run reports.
  • 5Test with a real new bug tracking data source and review the created search.

Questions about this workflow

Will Notis infer every search criterion from the source name?

The prompt should clearly state the search intent. Review the result after the test run.

Does a template create multiple triggers?

A template can create multiple data sources, and this workspace-wide trigger can fire for each one.

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.

TriggerScheduled

Bulk Update Errors

Tool to bulk update multiple errors in a project. use when batching identical updates across many errors.

ActionInstant

Webhook trigger

Notis starts this workflow when an external tool or custom backend sends an HTTP request.

TriggerInstant

Configure Integration

Tool to configure a new integration for a bugsnag project. use after selecting integration key and preparing credentials.

ActionInstant

All Page Events

Triggers when any Notion page is created or updated across the workspace.

TriggerPolling

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.

ActionInstant

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.

TriggerInstant

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..."

ActionInstant

New Comment

Triggers when a new comment is added to a specified Notion block or page.

TriggerPolling

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.

ActionInstant

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.

TriggerInstant

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.

ActionInstant

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.

TriggerInstant

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.

ActionInstant

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.

TriggerInstant

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.

ActionInstant

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.