Create a ClickUp task when a FullStory mobile app crash is detected

When FullStory detects a crash in your mobile app, this workflow creates a ClickUp task with the crash details you map, so each crash is on your team’s board as a piece of work to look at.

FullStory

ClickUp

Download this workflow Browse more workflows

2 steps Setup ~5 min Used on 808 sites Productivity Free to import

The Create a ClickUp task when a FullStory mobile app crash is detected workflow on the FlowMattic canvas, with 2 steps across FullStory, ClickUp — The workflow as it appears in the builder after import. Each step opens for editing.

What this workflow does

Crashes recorded in FullStory are only useful once someone acts on them. If your developers plan their work in ClickUp, a crash that never becomes a task tends to wait until a user complains. This workflow turns each detected crash into a task.

The FullStory trigger Mobile App Crash fires when FullStory detects a mobile crash event and passes that event's data to FlowMattic. The ClickUp step runs Create Task. You choose where the task goes and map the crash data into it, for example a task name built from the app and the error, and a description holding the rest.

Each crash event creates its own task. If one bug crashes the app for many users, you may get many tasks for the same problem, so consider a Filter or a dedicated place in ClickUp for crash tasks. Run a test after import to see which crash fields FullStory sends, and check Task History for the ClickUp response.

Mobile team triage board

Crashes from your iOS or Android app become tasks in the space your mobile developers already review each morning, ready to be assigned.

Watching a new release

After shipping an app update, crash tasks appear in ClickUp as they happen, so the team can tell quickly whether the release introduced a problem.

Agency maintaining a client app

The agency keeps crash work for each client app in ClickUp, and every FullStory crash event shows up there with the details the developer needs.

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
Fires when FullStory detects a crash event in your mobile app. The data FullStory sends about that crash is available to map into the ClickUp task.
Step 2Action
ClickUp Create Task
Creates a new ClickUp task. Choose where it is created and map the FullStory crash data into the task name and description so the developer can start from it.

What you need

FlowMatticCore
FullStory AccountAccount
ClickUp 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.

If FullStory's crash data includes the app version or build, add a Filter after the trigger that continues only for your live release, so test builds don't fill the board.
Add a Slack or email step after Create Task if someone should be told about each crash as well as having it on the ClickUp board.
Put the app version and device into the task name when FullStory sends them, which makes duplicate crashes easier to spot and merge.

Questions about this workflow

Does every FullStory mobile crash create a ClickUp task?

Yes. Each crash event FullStory reports runs the workflow once and creates one task. To narrow that down, put a Filter between the two steps.

Will repeated crashes from the same bug be merged in ClickUp?

No. The workflow creates a new task for each crash event and does not look for an existing one. Your team merges or closes duplicates in ClickUp.

Does my app have to send data to FullStory for the crash trigger to work?

Yes. The trigger reacts to crash events FullStory detects in a mobile app, so the app must already be reporting to FullStory. Connect both your FullStory and ClickUp accounts when you import.

Can I assign the ClickUp task to someone automatically?

Check the Create Task step after import to see which task settings it offers. Run one test crash event and confirm the task looks the way your team expects.