Bring Bugsnag event context into Box discussions
When a teammate adds a comment to a Box file, get a focused Bugsnag event review to keep the discussion grounded in current occurrence data.
Trigger
New File Comment Added
Triggers when a new comment is added to a file in Box. This trigger monitors a specific Box file and fires when new comments are detected.
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
Bug discussions often lack recent event context, forcing teammates to open another tool and reconstruct the situation.
- Add current event context to a Box file discussion.
- Surface event patterns that may help clarify a reported issue.
- Keep investigation context in a run report.
Setup
Build it in a few focused steps.
- 1Connect Box and Bugsnag once in the Notis portal.
- 2Create an automation in Automations, New Automation, and name it for comment-driven event review.
- 3Tell Notis in one instruction to use the new comment's project and issue context to review Bugsnag events and summarize relevant findings.
- 4Pick the Box New File Comment Added trigger and choose where run reports should go.
- 5Test with one real comment that names a Bugsnag project or otherwise provides enough context.
Questions about this workflow
Can the workflow determine which Bugsnag project to check?
It can use project details in the comment or the instruction. If those details are absent, Notis should report that the project is unknown instead of guessing.
Does this change the Box comment?
No. The available Bugsnag action retrieves events for review; the run report can provide context for the discussion.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Box to Bugsnag. A trigger fires from one place; an action lands in another.
Box 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.
Collaboration Details Changed
Triggers when a collaboration's details change (e.g., role, status, expiration). This trigger monitors a specific collaboration and detects when any meaningful field changes, such as role, status, expiration date, access type, or acknowledgment status.
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 Changed
Triggers when a comment's content or details change in Box. This trigger monitors a specific Box comment and detects when any meaningful field changes, such as message text edits, tagged message changes, or modification timestamp updates.
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 File Comment Added
Triggers when a new comment is added to a file in Box. This trigger monitors a specific Box file and fires when new comments are detected.
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 Metadata Changed
Triggers when a file's metadata or properties change in Box. This trigger monitors a specific Box file and fires when changes are detected in key fields like name, description, size, modification time, parent folder, or status.
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 Shared Link Changed
Triggers when a file's shared link settings change in Box. This trigger monitors a specific Box file's shared link and fires when changes are detected in the shared link configuration, such as access level, permissions, password protection, expiration date, or vanity URL.
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.
New File Version Uploaded
Triggers when a new file version is uploaded to a file in Box. This trigger monitors a specific Box file and fires when new versions are detected.
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.
Box 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.