FullStory sees what users do in your app: dead clicks piling up, a mobile crash, a custom event such as a failed checkout. FlowMattic posts those signals to Slack so product managers, designers and engineers find out while the session is still fresh. Notes written in FullStory reach the team too, so findings are shared instead of sitting in one account.
4 triggers 14 actions 6 example workflows 2 ready-made templates Unlimited runs
When this happens in FullStory4 triggers
Do this in Slack14 actions
1. TriggerSegment Alerts2. ActionSend Channel MessageWhen FullStory fires Segment Alerts, 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 templateWhen dead clicks on a segment pass your threshold, the product channel hears about it with the segment name, so someone can watch the sessions and find the broken element.
Segment AlertsSend Channel Message
View the template Each crash FullStory detects goes to the on-call channel with the device and app version, so the engineer on duty can open the session that led to it.
Mobile App CrashSend Channel Message
Researchers write notes on sessions in FullStory. Posting each new note to the design channel turns a private observation into something the team can discuss.
Note CreatedSend Channel Message
A Router reads the event name, such as checkout failed or signup error, and posts it to payments, growth or support, so each alert reaches the owners of that flow.
Custom EventRouterSend Channel Message
Set Channel Topic writes the time and app version of the latest crash into the header, so the on-call engineer sees at a glance when the last one happened.
Mobile App CrashDate/Time FormatterSet Channel Topic
A Counter tracks crashes as they arrive and a Filter posts only every tenth one, so a crash loop on one build does not bury the channel in identical messages.
Mobile App CrashCounterFilterSend Channel Message
At the end, each FullStory segment alert is posted to your product channel with the segment and a link to the sessions.
Open Connects in FlowMattic and add Slack for the workspace where the product team talks.
Create a workflow, choose FullStory and Segment Alerts, and follow the instructions shown to send FullStory alerts to it.
Trigger a test alert from FullStory, or wait for the next real one, so FlowMattic records the fields.
Add Send Channel Message, choose the channel and include the segment name and session link. Test it and switch the workflow on.
1. Trigger in FullStory
Segment Alerts
2. Action in Slack
Send Channel Message
Fields mapped from the earlier steps (a typical setup)
| From FullStory | To Slack |
|---|---|
| Segment name | Message: segment |
| Alert name | Message: alert |
| Session link | Message: watch |
| Alert time | Message: when |
A trigger starts a workflow. An action is something FlowMattic does in the app as a step.
FullStory and Slack connect through FlowMattic on your own site, with no separate automation account in the middle and no charge per run.
Dead clicks, crashes and failed flows show up in Slack for product and engineering, not only in a dashboard someone has to remember to open.
Notes written on sessions reach the design channel, so research turns into conversation and decisions.
FlowMattic runs on your own WordPress site with unlimited runs, so a noisy release week costs the same as a quiet one.
Connect Slack in FlowMattic, create a workflow with the FullStory Segment Alerts trigger and add Send Channel Message. Include the segment and session link in the message, capture a sample alert and switch the workflow on.
Yes. Build a separate workflow with the Mobile App Crash trigger and point it at your on-call or mobile channel. Each FullStory event can have its own workflow and channel.
Add a Counter and a Filter so only some alerts are posted, or a Filter on the app version so known issues are left out. You can also raise the alert threshold in FullStory.
Yes. The Custom Event trigger starts a workflow for events your app sends to FullStory. Use a Router on the event name to decide which channel each one goes to.
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. FullStory integration 1.0.0, Slack integration 1.0.
