TICKET MANAGEMENT
Dropbox Crash Dump to Linear Repro Assembler
Watches a Dropbox intake folder for crash dumps and logs, bundles each new file set into a normalized archive.
How it runs
The automated pipeline, trigger to output.
- TriggerNew file in Dropbox crash-intake folderDropbox
- ActionRead file and gather sibling artifactsDropbox
- LogicGroup multi-file drop into one bundle
- ActionNormalize names and archive to per-issue folderDropbox
- ActionCreate Linear issue with artifact linksLinear
- OutputUpdate originating Front conversationFront
What it does
Monitors a Dropbox folder where support drops raw crash artifacts (stack traces, HAR files, device logs). When a new file lands, it gathers the related artifacts, normalizes their names and structure, and creates a Linear bug issue with the bundle attached and a back-link to the Front conversation referenced in the filename.
When to use it
Use it when reproduction artifacts arrive as loose files rather than inline ticket attachments, and you want each crash turned into a structured Linear issue without an engineer manually collating files.
How it works
- 1A new file added to the Dropbox `crash-intake` folder triggers the flow.
- 2The flow reads the file plus any siblings sharing the same conversation reference token.
- 3A logic step waits/groups so a multi-file drop becomes one bundle, not many issues.
- 4Filenames are normalized and the set is moved to an archived per-issue subfolder.
- 5A Linear issue is created with the artifact links and parsed crash metadata.
- 6The matching Front conversation is updated with the Linear link to close the loop.
Set it up
What you configure once, before turning it on.
- 1Connect DropboxFiles and folders.
- 2Connect LinearIssues, projects, cycles, triage.
- 3Connect FrontShared inbox, conversations.
- 4Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 5Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 6Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More Ticket Management workflows
Enrich Discord bug reports with Sentry errors before filing in Linear
Takes a Discord bug report, has an LLM pull out likely error signatures, searches Sentry for matching events.
Front-to-Linear Recurring Bug Linker
When a Front ticket is tagged as a bug, it searches Linear for an existing matching issue and either links the ticket to that parent issue or opens a new tracked one.
Front Duplicate Conversation Clusterer
When a new Front conversation arrives, it semantically compares the report against open conversations.
Intercom Known-Issue Auto-Responder
When a new Intercom conversation matches a known active incident, it attaches the conversation to that incident's parent ticket and sends the customer the current status reply.
Weekly reopen-by-agent coaching digest
Aggregates each agent's solved-then-reopened tickets for the week, identifies the most common reopen reason per agent, and emails a private coaching digest to the support manager.
Escalate repeat reopens to a Linear bug
Detects when the same underlying issue reopens across multiple tickets, uses an AI agent to cluster them by root cause.
Run it inside a business
This workflow drops into a full company template. Import the org, and this is one of the playbooks its agents run.
Run this workflow in your colony.
14-day trial. No DevOps. No Sales call. Provisioned in under a minute.