GrowthBook controls your feature flags and A/B tests. FlowMattic posts each change to Slack: a flag created, edited or removed, an experiment started, changed or deleted. Engineers can link a sudden error spike to a flag change, product managers follow tests, and support knows which customers see a new feature.
6 triggers 14 actions 6 example workflows 2 ready-made templates Unlimited runs
When this happens in GrowthBook6 triggers
Do this in Slack14 actions
1. TriggerFeature Created2. ActionSend Channel MessageWhen GrowthBook fires Feature 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
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 templateEvery new flag appears with its key and owner, so the team knows what is being built behind flags and who to ask before touching it.
Feature CreatedSend Channel Message
View the template Feature Updated posts each change to a flag-log channel with the time. When errors spike, the on-call engineer can see which flag changed just before.
Feature UpdatedDate/Time FormatterSend Channel Message
New experiments post to the product channel with the hypothesis and variations, so designers and analysts know a test is coming and can check the setup.
Experiment CreatedSend Channel Message
Feature Deleted usually means a feature is fully rolled out or retired. A post to the support channel tells agents which behaviour customers will now see.
Feature DeletedSend Channel Message
A Filter keeps only changes that affect your production environment, and a private channel for leads gets those, separate from day-to-day staging edits.
Feature UpdatedFilterSend Private Channel Message
When an experiment is updated, Slack sets the owner a reminder two weeks later to check the results and remove the losing variation, so stale tests do not pile up.
Experiment UpdatedFind User by EmailAdd Reminder
At the end, every feature flag created in GrowthBook is posted to your dev channel with its key and description.
Open Connects in FlowMattic and add Slack with an account in the engineering channel.
Create a workflow, pick GrowthBook and Feature Created, and follow the instructions shown to send GrowthBook events to the workflow.
Add a test feature in GrowthBook so FlowMattic captures the feature fields.
Add Send Channel Message, pick the channel and map the feature key, description and owner. Test, then switch on.
1. Trigger in GrowthBook
Feature Created
2. Action in Slack
Send Channel Message
Fields mapped from the earlier steps (a typical setup)
| From GrowthBook | To Slack |
|---|---|
| Feature ID | Message: flag |
| Description | Message: what |
| Owner | Message: owner |
| Default value | Message: default |
A trigger starts a workflow. An action is something FlowMattic does in the app as a step.
GrowthBook and Slack connect through FlowMattic on your own site, with no separate automation account in the middle and no charge per run.
A channel of every flag and experiment change makes it easier to explain what changed when something breaks.
Product, design and support hear about new tests and retired flags without needing a GrowthBook login.
FlowMattic runs on your own WordPress site with unlimited runs, so a week of many flag edits does not change what you pay.
Connect Slack in FlowMattic, start a workflow with a GrowthBook trigger such as Feature Created or Experiment Created, and add Send Channel Message. Map the fields you want, test with a real change and switch it on.
Yes. Each GrowthBook event is its own trigger, so build one workflow for feature events and another for experiment events and point them at different channels.
Yes, if the change data shows the environment. Add a Filter after Feature Updated that continues only for production, and post those to a private channel.
Yes. Use the Feature Deleted trigger. It is useful for telling support and product that a feature is now fully on or removed.
Did not find your answer? You can browse the help center or ask us directly.
Slack and Google Sheets149 shared templates
Slack and Airtable44 shared templates
Slack and Fluent Forms42 shared templates
Slack and FluentCRM35 shared templates
Slack and ClickUp28 shared templates
Slack and Fluent Support21 shared templates
Slack and WooCommerce18 shared templates
Slack and Notion17 shared templatesInstall FlowMattic, connect both accounts and import a template. Every run stays on your own server.
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. GrowthBook integration 1.0.0, Slack integration 1.0.
