Skip to content
Notis

React to Browserbase run checkpoints in Slack

When a Browserbase run reaches a checkpoint worth noticing, send a webhook to Notis and let it add the agreed reaction to the relevant Slack message.

Trigger

Webhook received

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

Action

Add reaction to message

Adds a specified emoji reaction to an existing message in a slack channel, identified by its timestamp; does not remove or retrieve reactions.

Why this helps

Useful browser run updates can get buried while you are focused elsewhere, leaving teammates unsure whether anyone has seen them.

  • Acknowledge a checkpoint without leaving your current task.
  • Keep a lightweight signal attached to the relevant Slack message.
  • Use a webhook to start the workflow when the browser run reports an update.

Setup

Build it in a few focused steps.

  • 1Connect Browserbase MCP and Slack once in Notis.
  • 2Create an automation by telling Notis the outcome you want, or use Automations, New Automation in the portal.
  • 3In one instruction, say which reported checkpoint should receive a reaction and how Notis should identify the Slack message.
  • 4Pick a webhook trigger and choose where run reports should go.
  • 5Test with one real Browserbase checkpoint and confirm the intended Slack message receives the reaction.

Questions about this workflow

Does Browserbase MCP provide a trigger event for this workflow?

No Browserbase trigger events are listed here. A Notis webhook starts the workflow when an HTTP request arrives.

Can the workflow react to a Slack message if the webhook does not identify it?

Notis needs enough information to identify the intended existing Slack message. Include that reference in the webhook payload or instruction; do not assume Notis can infer unavailable history.

When this happens · Trigger

Do this · Action

Supported Triggers and Actions

Notis builds workflows that link Browserbase MCP to Slack. A trigger fires from one place; an action lands in another.

Browserbase MCP triggers

Slack actions

Recurring trigger

Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.

TriggerScheduled

Set snooze duration

Deprecated: turns on do not disturb mode for the current user, or changes its duration. use `set dnd duration` instead.

ActionInstant

Webhook trigger

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

TriggerInstant

Add a custom emoji to a Slack team

Deprecated: adds a custom emoji to a slack workspace given a unique name and an image url. use `add emoji` instead.

ActionInstant

Add an emoji alias

Adds an alias for an existing custom emoji in a slack enterprise grid organization.

ActionInstant

Add a remote file

Adds a reference to an external file (e.g., google drive, dropbox) to slack for discovery and sharing, requiring a unique `external id` and an `external url` accessible by slack.

ActionInstant

Add a star to an item

Stars a channel, file, file comment, or a specific message in slack.

ActionInstant

Add call participants

Registers new participants added to a slack call.

ActionInstant

Add emoji

Adds a custom emoji to a slack workspace given a unique name and an image url; subject to workspace emoji limits.

ActionInstant

Add reaction to message

Adds a specified emoji reaction to an existing message in a slack channel, identified by its timestamp; does not remove or retrieve reactions.

ActionInstant

Connect any two apps with Notis in the middle.

Browserbase MCP and Slack, 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 Slack.