Correlate Mobile Crash Reports with GitHub Commits via Claude & Slack

Correlate mobile crashes with the exact GitHub commit—automatically

This n8n workflow takes incoming mobile crash reports, finds the most relevant stack frames, matches them to recent GitHub commits, and uses Claude to recommend the most likely responsible change—then creates a triage task and posts the result to Slack.

What this workflow does

• Receives a crash report via an HTTP webhook (or runs manually with a sample payload for testing).
• Normalizes the payload, extracts stack frames, and selects top “app-owned” candidate frames using configured path prefixes.
• Investigates GitHub evidence for each candidate file: queries the GitHub API for recent commits touching that path and fetches file content metadata.
• Asks Anthropic Claude to analyze the crash context plus GitHub evidence, returning a JSON response with:
  • most likely responsible commit/author
  • a confidence score
  • fix guidance when available
• Creates a task in your issue/task tracker API, auto-assigning when confidence meets a threshold (otherwise leaving it for manual triage).
• Posts a Slack message to your configured channel with the suspected file/author, confidence, and the suspected commit link (when available).

Use cases

• Speed up triage after a new mobile release by mapping crash stack traces directly to recent GitHub changes.
• Reduce manual investigation time for engineering teams using tools like Crashlytics, Sentry, or Bugsnag by automating the correlation step.
• Improve accountability by creating ticket tasks linked to the most likely offending commit and author.

Technical details

• Webhook + normalization using webhook, if, set, and code.
• GitHub integration to retrieve recent commits by path and associated file metadata.
• Claude integration via Anthropic HTTP Header Auth using your x-api-key.
• Task/issue creation via your task tool HTTP Header Auth API.
• Slack posting using the slack node with OAuth to publish results to your channel.