Mobile App Crash Log to GitHub Triage
Upload an iOS or Android crash log, redact sensitive identifiers, fingerprint the failure, and open a developer-ready GitHub issue.
The full canvas, before you import it
Click any node to see its config.
Click a node to select it — same as the Heym editor; the panel shows its settings.
4 nodes · Free & source-available
Mobile App Crash Log to GitHub Triage
Turn raw mobile crash reports into consistent engineering issues without asking developers to manually clean every stack trace. A bundled Python skill reads the uploaded log from Heym Drive, redacts common identifiers, detects iOS or Android markers, and creates a deterministic crash fingerprint before the Agent writes the issue.
What this workflow does
- MobileCrashFile accepts a crash, IPS, JSON, or plain-text log
- TriageMobileCrash calls the bundled parser skill before writing any conclusions
- The skill redacts emails, tokens, and device-like identifiers and hashes the normalized stack signature
- CreateMobileCrashIssue opens a GitHub issue with the platform, app version, severity, fingerprint, and safe reproduction context
- CrashIssueReceipt returns the issue URL and triage fields
Use cases
- Mobile release crash intake for iOS and Android teams
- Deduplicating repeated crash reports by normalized fingerprint
- Converting support attachments into engineering-ready issues
- Keeping device identifiers and tokens out of public issue bodies
Setup
Connect an LLM credential to TriageMobileCrash and a GitHub credential to CreateMobileCrashIssue. Set the target owner and repository, then upload a de-identified sample before processing production logs. The parser is a triage aid; confirm symbols, versions, and severity with your mobile engineering team.
How to import this template
- 1Click Import → Copy JSON on this page.
- 2Open your Heym and navigate to a workflow canvas.
- 3PressCmd+V/Ctrl+V— nodes appear instantly.
- 4Add your API keys in the node config panels and click Run.
Discover more automations
- Dev & IT OpsCodex PR Fix AgentSend a coding task to Codex, open a draft PR when it succeeds, and notify Slack when Codex needs follow-up input.
- Dev & IT OpsAgent-Guided Codex PR DispatcherLet an Agent inspect a GitHub request, prepare a confirmed Codex task, open a ready PR, and notify Slack when Codex needs input.
- Dev & IT OpsCursor Post NotifierMonitor the Cursor blog on a schedule and Slack-notify your team when a new post goes live.
- Dev & IT OpsClaude Blog MonitorMonitor the Anthropic blog on a schedule and Slack-notify your team on new Claude posts.
- Dev & IT OpsGitHub Release RadarCompare the latest GitHub release tag against Redis and notify Slack when a project ships a new version.
- Dev & IT Opsweb.dev Article MonitorCron + crawler + Redis dedupe + Slack: get notified when Google's web.dev blog publishes a new article.
- Dev & IT OpsCloudback MCP Backup Coverage ReviewReview Cloudback backup coverage with a Docker-based MCP server, gate configuration changes with HITL, and notify ops in Slack.
- Dev & IT OpsResilient HTTP + Error HandlerAttach an Error Handler node to an HTTP call and Slack-notify your team the moment a request fails.
- Dev & IT OpsPlaywright Visual AI MonitorTake a full-page screenshot on a schedule, analyse it with an LLM for anomalies, and Slack-alert when something looks off.
- Dev & IT OpsRealtime WebSocket Alert RelayListen to an external WebSocket feed, audit critical events, and forward them to another realtime channel.
- Dev & IT OpsAsync Sub-workflow DispatcherValidate an incoming brief and dispatch a reusable sub-workflow in the background without a response node.
- Dev & IT OpsRabbitMQ Delayed PublisherPublish a release message to RabbitMQ with an optional delivery delay for downstream consumers.