Airtable and GitHub integration

Mobile App Build Time Hotspot Tracker - Gradle/CocoaPods Analyzer Alerting This workflow automates the monitoring and analysis of CI/CD build performance for mobile projects using Gradle and CocoaPods. It triggers upon build completion, compares metrics against historical performance stored in Airtable, and leverages AI to identify regressions. The system provides automated feedback via GitHub PR comments and email alerts for critical performance drops. ⚡ Quick Implementation Steps Configure CI Pipeline: Set your CI job to send a POST request with build metrics to the workflow's Webhook URL. Set Configuration: Adjust the regressionThreshold (default: 20%) and excludeModules in the Set Configuration node. Connect Airtable: Link your credentials to the Fetch Historical Builds and Store Build Data nodes. Connect GitHub & Gmail: Authenticate your GitHub and Gmail OAuth2 credentials for reporting. Verify AI Model: Ensure the OpenAI Chat Model is connected to power the performance analysis. What It Does The workflow acts as an intelligent performance gatekeeper for development pipelines: Metric Collection: Captures detailed task durations, build IDs, and PR context directly from CI/CD webhooks. Historical Comparison: Automatically retrieves the last 10 builds for a specific repository to calculate average baselines. AI-Powered Diagnostics: Uses a specialized AI agent to analyze slowdowns, identify root causes, and provide optimization recommendations. Automated Reporting: Categorizes findings by severity (Critical, Warning, Info) and updates stakeholders through PR comments and high-priority emails. Who’s It For Mobile Engineering Teams looking to prevent "death by a thousand cuts" in build time slowdowns. DevOps/Platform Engineers who need automated auditing of build infrastructure health. Release Managers requiring an audit trail of performance regressions across different pull requests. Technical Workflow Breakdown Entry Points (Triggers) Webhook: Listens for POST requests at /webhook/build-hotspot-tracker containing build metrics and repository metadata. Processing & Logic Set Configuration: Defines static variables like regression sensitivity and modules to ignore (e.g., test modules). Historical Analysis: Aggregate nodes calculate min, max, and average build times from historical records. AI Build Analyzer: An AI Agent utilizing GPT-4.1-mini to synthesize current build data with historical trends and PR context. Route by Severity: A switch node that directs the workflow based on whether the AI classifies the regression as Critical, Warning, or Info. Output & Integrations GitHub (Comment on PR): Posts a formatted markdown report including a severity badge, regressions list, and root causes. Airtable (Store Build Data): Logs the build ID, total duration, and AI recommendations for long-term tracking. Gmail (Notify Email): Sends immediate alerts to the team for critical regressions, including a direct link to the affected PR. Customization Adjust Sensitivity Modify the regressionThreshold in the Set Configuration node to change how aggressive the system is in flagging slowdowns (e.g., set to 10 for stricter monitoring). Module Filtering Update the excludeModules parameter to ignore specific tasks like linting or unit tests that may have volatile durations but do not represent core build performance. Analysis Detail The AI Build Analyzer prompt can be customized to focus on specific platform needs, such as focusing heavily on CocoaPods link times or Gradle configuration phases. Troubleshooting Guide | Issue | Possible Cause | Solution | | :-------------------------- | :----------------------------------------- | :----------------------------------------------------------------------------------------- | | No PR Comments | GitHub permissions or incorrect PR number. | Verify your GitHub token has write access and the CI payload includes a valid prNumber. | | Historical Data Missing | Airtable Filter failure. | Ensure the repository and prNumber fields in Airtable match the incoming Webhook data. | | AI Analysis Errors | OpenAI credits or model timeout. | Check your OpenAI API quota and verify the gpt-4.1-mini model is available in your region. | | Emails Not Sending | Gmail OAuth2 expired. | Re-authenticate the Gmail node in your n8n credentials settings. | Need Help? If you need assistance customizing this workflow, adding new features or integrating more systems (like JIRA, Slack or Google Sheets), feel free to reach out. Our n8n automation experts at WeblineIndia are here to support you in scaling your automation journey.

Automatically detect, classify, and document GitHub API errors using AI. This workflow connects GitHub, OpenAI (GPT-4o), Airtable, Notion, and Slack to build a real-time, searchable API error knowledge base — helping engineering and support teams respond faster, stay aligned, and maintain clean documentation. ⚙️📘💬 🚀 What This Template Does 1️⃣ Triggers on new or updated GitHub issues (API-related). 🪝 2️⃣ Extracts key fields (title, body, repo, and link). 📄 3️⃣ Classifies issues using OpenAI GPT-4o, identifying error type, category, root cause, and severity. 🤖 4️⃣ Validates & parses AI output into structured JSON format. ✅ 5️⃣ Creates or updates organized FAQ-style entries in Airtable for quick lookup. 🗂️ 6️⃣ Logs detailed entries into Notion, maintaining an ongoing issue knowledge base. 📘 7️⃣ Notifies the right Slack team channel (DevOps, Backend, API, Support) with concise summaries. 💬 8️⃣ Tracks & prevents duplicates, keeping your error catalog clean and auditable. 🔄 💡 Key Benefits ✅ Converts unstructured GitHub issues into AI-analyzed documentation ✅ Centralizes API error intelligence across teams ✅ Reduces time-to-resolution for recurring issues ✅ Maintains synchronized records in Airtable & Notion ✅ Keeps DevOps and Support instantly informed through Slack alerts ✅ Fully automated, scalable, and low-cost using GPT-4o ⚙️ Features Real-time GitHub trigger for API or backend issues GPT-4o-based AI classification (error type, cause, severity, confidence) Smart duplicate prevention logic Bi-directional sync to Airtable + Notion Slack alerts with contextual AI insights Modular design — easy to extend with Jira, Teams, or email integrations 🧰 Requirements GitHub OAuth2 credentials OpenAI API key (GPT-4o recommended) Airtable Base & Table IDs (with fields like Error Code, Category, Severity, Root Cause) Notion integration with database access Slack Bot token with chat:write scope 👥 Target Audience Engineering & DevOps teams managing APIs Customer support & SRE teams maintaining FAQs Product managers tracking recurring API issues SaaS orgs automating documentation & error visibility 🪜 Step-by-Step Setup Instructions 1️⃣ Connect your GitHub account and enable the “issues” webhook event. 2️⃣ Add OpenAI credentials (GPT-4o model for classification). 3️⃣ Create an Airtable base with fields: Error Code, Category, Root Cause, Severity, Confidence. 4️⃣ Configure your Notion database with matching schema and access. 5️⃣ Set up Slack credentials and choose your alert channels. 6️⃣ Test with a sample GitHub issue to validate AI classification. 7️⃣ Enable the workflow — enjoy continuous AI-powered issue documentation!