Per-pair page

Connect Slack to Browserbase in two minutes.

Real-time triggers from Slack, ready-made actions in Browserbase. Filter, transform, and route without writing a line of code.

Connect Slack to Browserbase — start free See reverse direction

Trigger app

Slack as the trigger

Workflows fire when something happens in Slack.

See all 13 triggers →

Action app

Browserbase as the action

Workflows do something in Browserbase, instantly.

Connect Slack to Browserbase — start free

Both directions

Pick the way that fits your stack.

Pair pages are mirrored. Each direction gets its own dedicated page.

Slack → Browserbase

When something happens in Slack, do it in Browserbase.

13 Slack triggers wired to 6 Browserbase actions. Most-used pairing: App Home Opened → Close Session.

Browserbase → Slack

Or fire it the other way around.

0 Browserbase triggers wired to 45 Slack actions downstream.

Use any trigger in the catalog as the upstream.

See Browserbase → Slack →

Popular pairings

Common Slack → Browserbase workflows.

Pick a pairing to set it up in two minutes. Each one is a fully editable recipe.

Showing 9 of 78 combinations

When app home opened in Slack, close session in Browserbase.

Fires when a user opens your Slack app's Home tab or DM. Useful for refreshing the Home view, lazy-loading user-specific data, or tracking app engagement.

When app home opened in Slack, create browser session in Browserbase.

Fires when a user opens your Slack app's Home tab or DM. Useful for refreshing the Home view, lazy-loading user-specific data, or tracking app engagement.

When app home opened in Slack, get debug url in Browserbase.

Fires when a user opens your Slack app's Home tab or DM. Useful for refreshing the Home view, lazy-loading user-specific data, or tracking app engagement.

When app home opened in Slack, get session recording in Browserbase.

Fires when a user opens your Slack app's Home tab or DM. Useful for refreshing the Home view, lazy-loading user-specific data, or tracking app engagement.

When app mentioned in Slack, close session in Browserbase.

Fires when your Slack app is mentioned in a message. The standard hook for chatbots that answer when summoned with @your-app.

When app mentioned in Slack, create browser session in Browserbase.

Fires when your Slack app is mentioned in a message. The standard hook for chatbots that answer when summoned with @your-app.

When app mentioned in Slack, get debug url in Browserbase.

Fires when your Slack app is mentioned in a message. The standard hook for chatbots that answer when summoned with @your-app.

When app mentioned in Slack, get session recording in Browserbase.

Fires when your Slack app is mentioned in a message. The standard hook for chatbots that answer when summoned with @your-app.

When new channel in Slack, close session in Browserbase.

Fires when a new Slack channel is created in the workspace. Useful for auto-adding the bot, welcome messages, or governance audit logs.

How it works

Connect Slack and Browserbase in five steps.

No code, no glue, no half-day setup. Each step is one click.

1
Connect
Authorize Slack and Browserbase
Open TinyCommand, authorize Slack and Browserbase once each. Both connections are available to every workflow on your account.
2
Trigger
Pick a Slack trigger
Drop the Slack → App Home Opened trigger onto the canvas. TinyCommand auto-registers the webhook.
POST /v1/webhooks/slack.trigger-app-home-opened
3
Transform
Add a filter or AI step
Optionally add a Filter node ("subject contains URGENT") or an AI step ("classify intent") between trigger and action.
4
Action
Add the Browserbase action
Drop the Browserbase → Close Session action below it. Map fields from the Slack payload into the Browserbase inputs.
browserbase.close-session
5
Publish
Publish and forget
Hit Publish. TinyCommand runs it in production from second one. Watch the run-log fill up.

FAQ

Questions about Slack + Browserbase.

How long does it take to connect Slack and Browserbase on TinyCommand?

Under two minutes. Authorize Slack and Browserbase once each, drop the Slack trigger and Browserbase action onto a workflow canvas, map a couple of fields, and publish. No code, no glue.

Is the Slack ↔ Browserbase integration real-time?

Yes. Both Slack and Browserbase expose webhooks, so events from one fire workflows in the other within seconds rather than on a polling interval.

Can I filter or transform data between Slack and Browserbase?

Yes. Add a Filter node to only pass through matching events, a Switch node to branch by value, or an AI / Code node to transform payloads before they hit Browserbase.

What Slack events can trigger a Browserbase workflow?

Any of the 13 Slack triggers, including "App Home Opened". Each fires in real time when the matching event happens in Slack.

Do I need a paid plan to use Slack with Browserbase?

No. Both integrations come on every plan, including Free, which includes 1,000 credits a month with no credit card. Each workflow step uses 1 credit, and paid plans include more credits and team seats when you need them.

What if I want Browserbase → Slack instead?

Build it the same way, in reverse. There's a dedicated /integrations/browserbase/with/slack page with the reverse-direction triggers and actions.

Other apps that pair well with Slack.

Slack + Gmail

Slack + Google Sheets

Spreadsheets & Databases

Spreadsheets & Databases

Connect Slack to Browserbase — start free