TICKET MANAGEMENT
Archive Intercom bug screenshots to Drive and link them in a Linear issue
When a customer reports a visual bug in Intercom, an agent collects the attached images, stores them in a dated Google Drive folder.
How it runs
The automated pipeline, trigger to output.
- TriggerIntercom conversation tagged 'visual-bug'Intercom
- ActionDownload all image attachments from the conversationIntercom
- ActionCreate dated Drive folder and upload screenshotsGoogle Drive
- ActionCreate Linear issue with repro summary and Drive linkLinear
- OutputPost Linear link back as an Intercom internal noteIntercom
What it does
Intercom attachment links expire and break, so visual bug reports lose their evidence by the time an engineer looks. This workflow pulls every image from a flagged Intercom conversation, saves them to a permanent Google Drive folder named for the conversation, and files a Linear issue that references the Drive bundle plus a transcript of the reported behavior.
When to use it
Use it for UI and rendering regressions reported via Intercom chat, where the screenshot is the bug and you can't risk losing it to link expiry.
How it works
- 1An Intercom conversation tagged `visual-bug` triggers the run.
- 2The agent reads the conversation and downloads all image attachments.
- 3A Google Drive folder is created, named with the conversation ID and date, and the images are uploaded.
- 4The agent writes a short repro summary and reported environment from the chat.
- 5A Linear issue is created with the summary and a link to the Drive folder.
- 6The Linear issue link is posted back into the Intercom conversation as an internal note.
Set it up
What you configure once, before turning it on.
- 1Connect IntercomConversations, contacts, articles.
- 2Connect Google DriveDocs, sheets, slides, files.
- 3Connect LinearIssues, projects, cycles, triage.
- 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.