Connect BrowserStack and Slack

BrowserStack's Percy visual reviews only help if someone looks at them. FlowMattic posts each build event to Slack: a new build started, snapshots are ready for review, changes were requested, the build was approved. Front-end teams and QA reviewers see what needs their eyes in the channel where they already discuss releases.

Try FlowMattic free See example workflows

6 triggers 14 actions 6 example workflows 2 ready-made templates Unlimited runs

Try a pairing

When this happens in BrowserStack6 triggers

Do this in Slack14 actions

1. TriggerBuild Created

2. ActionSend Channel Message

When BrowserStack fires Build Created, FlowMattic runs Send Channel Message in Slack with the data from that event.

You build this in the FlowMattic workflow builder on your own site. See the setup steps

BrowserStack and Slack workflows you can build

Each one uses only triggers and actions the two integrations ship today, plus FlowMattic's own tools. Where the library has a ready-made template, import it instead of building from scratch.

Ready-made template

Post each new BrowserStack build to the dev channel

The project, branch and build number appear when the build is created, so the team knows a visual review is on its way for that pull request.

Build CreatedSend Channel Message

View the template

Ask reviewers to look when snapshots are ready

Build Finished means the snapshots have been processed. A Router posts builds with visual changes to the QA channel and builds with none to a quiet log.

Build FinishedRouterSend Channel Message

Tell the author when changes are requested

A requested change blocks the merge. The developer who opened the build is found by email and gets a direct message with the build link.

Build Changed RequestedFind User by EmailSend Direct Message

Post approved builds to the release channel

An approved build is ready to merge from a visual point of view. The release channel sees which branch passed review and who approved it.

Build ApprovedSend Channel Message

Remind the reviewer about a build back in review

Build Unreviewed fires when a build goes from changes requested back to unreviewed, usually after a fix. Slack adds a reminder for the reviewer to take another look.

Build UnreviewedAdd Reminder

Record webhook setting changes for the platform team

Ping fires when the webhook configuration of a project is created or updated. A private channel post tells the platform team that someone changed the setup.

PingSend Private Channel Message

Set up: new builds to Slack

At the end, every new build in your BrowserStack project is posted to your dev channel with the branch and build link.

Connect Slack
In FlowMattic, open Connects and add a Slack connection with an account in the dev channel.
Start with Build Created
Create a workflow with the BrowserStack Build Created trigger and follow its instructions to add the workflow's webhook to your project.
Run a test build
Push a commit that runs your visual tests, so FlowMattic captures the build fields.
Post the build
Add Send Channel Message, choose the channel and write the text from the project, branch, build number and URL. Test it and switch on.

Import the ready-made template Beginner, about 5 min to set up

Slack app icon — Built on the FlowMattic canvas. Test each step with real data, then switch the workflow on.

From BrowserStack	To Slack
Project name	Message: project
Branch	Message: branch
Build number	Message: build
Build URL	Message: review link

Triggers and actions in this pair

A trigger starts a workflow. An action is something FlowMattic does in the app as a step.

Good to know

These events come from Percy visual review builds in BrowserStack, so they describe snapshot review, not every automated test run.
Webhooks are added per project. Add the workflow's URL to each project you want to hear from, or use one workflow per project with its own channel.
Build Created and Build Finished fire for every build, including drafts on feature branches. Add a Filter on the branch name if only main or release branches matter.

BrowserStack

Integration page

Triggers (6)

Build CreatedTriggers when a build has been created.
Build ApprovedTriggers when a build has been approved.
Build FinishedTriggers when a build has finished processing.
Build Changed RequestedTriggers when a build has changes requested.
PingTriggers when a webhook configuration has been created or updated for the current project.
Build UnreviewedTriggers when the state of a Percy builds changed from "Changes requested" to "Unreviewed".

Slack

Integration page

Actions (14)

Send Channel MessagePost or Schedule a new message to a specific #channel
Add ReminderAdds a reminder for the user
Create ChannelCreates a new channel
List All ChannelsRetrieve list of all channels
Set Channel TopicSets the topic on a selected channel
Set StatusSets your Slack status to the given text and emoji
Invite User To ChannelInvite an existing User to an existing Channel. You must be a member of the channel to invite someone to it
Find User by EmailFinds a user by matching against their email instead of their username
Find User by IDFinds a user by their ID.
Send Direct MessageSend a direct message to a user or yourself from the Slackbot. Can also schedule a message for later
Send Private Channel MessagePost a new message to a private channel you choose. Can also schedule a message for later
Update ProfileUpdate basic profile fields such as name or title
Find MessageFinds a Slack message using the Slack Search feature
Upload FileUpload file to your slack workplace

Why run this pair with FlowMattic

BrowserStack and Slack connect through FlowMattic on your own site, with no separate automation account in the middle and no charge per run.

Visual reviews do not stall

Reviewers hear when snapshots are ready and authors hear when changes are requested, which keeps pull requests moving.

Release managers see approvals

Approved builds post to the release channel, so the person cutting the release knows the visual checks have passed.

Every build at no extra cost

FlowMattic runs on your WordPress site with unlimited runs, so a team that builds dozens of times a day pays the same.

Common questions

How do I send BrowserStack build notifications to Slack?

Create a FlowMattic workflow with the BrowserStack Build Created or Build Finished trigger, add its webhook to your project and run a build. Then add Send Channel Message with the branch and build link and switch it on.

Can only failed or changed builds be posted?

Yes. Use Build Finished with a Router or Filter on the build's review state, so builds with no visual changes go to a log channel or nowhere.

Can the developer get the message instead of the channel?

Yes, when the build data includes the author's email. Find User by Email looks them up in Slack and Send Direct Message sends it to them.

Can several projects share one channel?

Yes. Point each project's webhook at the same workflow and include the project name in the message, or route by project with a Router if each team wants its own channel.

Did not find your answer? You can browse the help center or ask us directly.

Start automating BrowserStack and Slack

Install FlowMattic, connect both accounts and import a template. Every run stays on your own server.

Try FlowMattic free See pricing

30-day money-back guarantee Unlimited workflows and runs Self-hosted

Reviewed 27 Oct 2026. The example workflows are written with AI from the real triggers and actions of both integrations and checked against them. BrowserStack integration 1.0.0, Slack integration 1.0.