Bring the right incident responders into Bugsnag
When a responder roster is shared, Notis can turn an explicit invitation request into a Bugsnag collaborator invite.
Trigger
File Shared (Permissions Added)
Triggers when new sharing permissions are granted to a file or folder. Uses Drive's `changes.list` endpoint with inline `permissions` in the `fields` mask so each change carries the file's current permission set provider-atomically. We diff that against `seen_permission_keys` to identify newly added grants. Drive page tokens are the primary cursor; if Drive rejects a stored token, the trigger raises `PollingTriggerError` without clearing state rather than silently re-baselining and dropping events. Limitation: truly ephemeral permissions (added and revoked between two polls without any other file modification in between) are not detected. Drive Activity API would catch those but requires an additional OAuth scope and a different payload contract.
Action
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.
Why this helps
A shared responder roster does not automatically give a teammate access to the Bugsnag organization.
- Reduce the handoff between sharing a roster and inviting a responder.
- Require an explicit email and organization before sending an invite.
- Keep the invitation action tied to a newly shared roster.
Setup
Build it in a few focused steps.
- 1Connect Google Drive and Bugsnag once in the Notis portal.
- 2Create an automation in Automations, New Automation, and give it a clear name.
- 3Tell Notis to review a newly shared incident roster and invite only a person whose email and intended Bugsnag organization are explicitly stated.
- 4Pick the Google Drive File Shared trigger and choose where run reports should go.
- 5Test with one real roster that names the invitee email and organization.
Questions about this workflow
Does sharing the Drive file automatically invite everyone with access?
No. The instruction should require a named invitee email and an explicitly identified Bugsnag organization before Notis invites anyone.
What if the roster lists names but no emails?
Have Notis report that the invite details are incomplete and avoid guessing an email address.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Google Drive to Bugsnag. A trigger fires from one place; an action lands in another.
Google Drive 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.
Comment Added (Docs/Sheets/Slides)
Triggers when a new comment is added to Google Docs, Sheets, or Slides.
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.
File Created
Triggers when a new file is created in Google Drive.
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..."
File Deleted or Trashed
Triggers when a file is moved to trash or permanently deleted in Drive.
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.
File Shared (Permissions Added)
Triggers when new sharing permissions are granted to a file or folder. Uses Drive's `changes.list` endpoint with inline `permissions` in the `fields` mask so each change carries the file's current permission set provider-atomically. We diff that against `seen_permission_keys` to identify newly added grants. Drive page tokens are the primary cursor; if Drive rejects a stored token, the trigger raises `PollingTriggerError` without clearing state rather than silently re-baselining and dropping events. Limitation: truly ephemeral permissions (added and revoked between two polls without any other file modification in between) are not detected. Drive Activity API would catch those but requires an additional OAuth scope and a different payload contract.
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.
File Updated
Triggers when a file's metadata or content changes in Google Drive.
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.
Google Drive Changes
Triggers when changes are detected in a Google Drive.
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.
Google Drive 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.