When a FullStory mobile app crash occurs, create a ClickUp bug task and notify the team in Slack

When FullStory detects a crash in your mobile app, this workflow creates a task in ClickUp for it and then posts a message to a Slack channel, so the crash is tracked and your team hears about it.

FullStory

ClickUp

Slack

Download this workflow Browse more workflows

3 steps Setup ~5 min Used on 3.0k sites Productivity Free to import

The When a FullStory mobile app crash occurs, create a ClickUp bug task and notify the team in Slack workflow on the FlowMattic canvas, with 3 steps across FullStory, ClickUp, Slack — The workflow as it appears in the builder after import. Each step opens for editing.

What this workflow does

Crash reports that stay inside an analytics tool are easy to miss. Engineers need a task they can pick up, and the wider team needs to know something broke. This workflow does both from a single FullStory event.

The FullStory trigger fires when a mobile crash event is detected. FlowMattic passes the event data to ClickUp, which creates a new task in your workspace. You map the crash details into the task name and description. The last step posts a message to a Slack channel, and it can include data from both the crash and the new ClickUp task, such as the task link.

Every crash event creates its own task. If your app crashes many times for the same reason, you will see a task for each event, so think about adding a Filter before you turn it on for a busy app.

Bug triage for a small mobile team

A two-developer team gets a ClickUp task for each crash FullStory detects and a note in #mobile-bugs, so whoever is free picks it up.

Release-day monitoring

After shipping a new app version, the team watches the Slack channel for crash alerts and opens the matching ClickUp task to see the details.

Keeping product managers in the loop

A product manager who lives in Slack sees each crash message with a link to the ClickUp task, without opening FullStory.

How this workflow runs

What happens at each step once the workflow is on, and what you need before you import it.

Step 1Trigger
FullStory Mobile App Crash
Runs when FullStory detects a crash in your mobile app. The crash event data is passed on for mapping into the ClickUp task and the Slack message.
Step 2Action
ClickUp Create Task
Opens a ClickUp task for the crash. Map crash details from FullStory into the task so the engineer has context, and use a test run to check where the task lands.
Step 3Action
Slack Send Channel Message
Sends a Slack message to a channel of your choice. Map in the crash details and data returned by the ClickUp step, such as the task's link, if it is available.

What you need

FlowMatticCore
FullStory AccountAccount
ClickUp AccountAccount
Slack AccountAccount

After importing, map your own data. To keep the template universal, not every step is pre-filled. Open each step in the builder and connect your accounts and fields (channels, lists, sheets, recipients) before you switch the workflow on.

Make it yours

Changes worth making after you import it.

Put a Filter between the FullStory trigger and the ClickUp step that continues only for crashes from a chosen app version or platform, if FullStory sends that field. Other crashes then get neither a task nor a Slack message.
Map the ClickUp task's URL from step 2 into the Slack message so people can jump straight to the task.
Trigger a test crash in a development build after import so FlowMattic captures the FullStory fields you can map.

Questions about this workflow

Will FullStory crashes create duplicate ClickUp tasks?

Yes, as imported. Each crash event runs the workflow and creates a new task. There is no step that looks for an existing task for the same crash.

What goes into the ClickUp task for each FullStory crash?

Whatever you map. The Create Task step ships unmapped, so after import you connect ClickUp and map the crash details into the task name and description. Trigger a test crash first so you can see which details FullStory sends.

Does the Slack alert go out before the ClickUp task exists?

No. The steps run in order, so ClickUp creates the task first and the Slack message follows. That is why the message can carry data from the new task.