Google Drive and Jira Software integration

📘 Description: This workflow automates the incident response lifecycle — from creation to communication and archival. It instantly creates Jira tickets for new incidents, alerts the on-call Slack team, generates timeline reports, logs the status in Google Sheets, and archives documentation to Google Drive — all automatically. It helps engineering and DevOps teams respond faster, maintain audit trails, and ensure no incident details are lost, even after Slack or Jira history expires. ⚙️ What This Workflow Does (Step-by-Step) 🟢 Manual Trigger – Start the incident creation and alerting process manually on demand. 🏷️ Define Incident Metadata – Sets up standardized incident data (Service, Severity, Description) used across Jira, Slack, and Sheets for consistent processing. 🎫 Create Jira Incident Ticket – Automatically creates a Jira task with service, severity, and description fields. Returns a unique Jira key and link for tracking. ✅ Validate Jira Ticket Creation Success – Confirms the Jira ticket was successfully created before continuing. True Path: Proceeds to Slack alerts and documentation flow. False Path: Logs the failure details to Google Sheets for debugging. 🚨 Log Jira Creation Failures to Error Sheet – Records any Jira API errors, permission issues, or timeouts to an error log sheet for reliability monitoring. 🔗 Combine Incident & Jira Data – Merges incident context with Jira ticket data to ensure all details are unified for downstream notifications. 💬 Format Incident Alert for Slack – Generates a rich Slack message containing Jira key, service, severity, and description with clickable Jira links. 📢 Alert On-Call Team in Slack – Posts the formatted message directly to the #oncall Slack channel to instantly notify engineers. 📋 Generate Incident Timeline Report – Parses Slack message content to create a detailed incident timeline including timestamps, service, severity, and placeholders for postmortem tracking. 📄 Convert Timeline to Text File – Converts the generated timeline into a structured .txt file for archival and compliance. ☁️ Archive Incident Timeline to Drive – Uploads the finalized incident report to Google Drive (“Incident Reports” folder) with timestamped filenames for traceability. 📊 Log Incident to Status Tracking Sheet – Appends Jira key, service, severity, and timestamp to the “status update” Google Sheet to build a live incident dashboard and enable SLA tracking. 🧩 Prerequisites Jira account with API access Google Sheets for “status update” and “error log” tracking Slack workspace connected via API credentials Google Drive access for archival 💡 Key Benefits ✅ Instant Slack alerts for new incidents ✅ Centralized Jira ticketing and tracking ✅ Automated timeline documentation for audits ✅ Seamless Google Drive archival and status logging ✅ Reduced MTTR through faster communication 👥 Perfect For DevOps and SRE teams managing production incidents Engineering managers overseeing uptime and reliability Organizations needing automated post-incident documentation Teams focused on SLA adherence and compliance reporting

Who is this for? This template is ideal for HR teams, startup founders, operations leads, remote-first companies, and freelancers managing onboarding manually or across multiple tools. Whether you’re hiring your first intern or streamlining onboarding for dozens of new team members, this workflow automates the entire trigger → task creation → onboarding delivery process using no-code tools connected via n8n. What problem does this solve? Employee onboarding is often fragmented and error-prone — involving Jira tasks, Slack DMs, file sharing, and email templates spread across different apps. This workflow connects it all, letting you create tasks, notify people, share folders, and message hires instantly — right when they’re marked as “Hired” in a Google Sheet or added to Slack. No more bouncing between 5 tabs. This is onboarding as a system. What this workflow does ✅ Watches a Google Sheet (or Slack trigger) for new hires 📋 Creates a Jira onboarding Epic with role-based subtasks 📂 Generates a Google Drive folder and shares it with the new hire 📬 Sends a personalized, HTML-formatted welcome email via Gmail 💬 Posts a Slack message in the #onboarding channel + DM to the hire 📊 Logs onboarding activity back to the Sheet (status, links, etc.) 🔁 Modular subtasks based on role/team (e.g. Dev vs Marketing vs Student) 🧠 Expressions, fallback logic, and Slack→Jira user ID mapping built-in Setup Create API credentials for: Slack Google Sheets Google Drive Jira Cloud Gmail (API or SMTP) Import the .json workflow into your n8n instance (Cloud or self-hosted) Replace placeholder values (e.g. Project ID, Issue Type ID, folder path) Customize onboarding messages, email HTML, and task logic Test with included mock data (sample hire, Slack user, Jira user) Activate your flow and start onboarding with one click 🗒 Color-coded workflow notes This workflow uses Innovatio’s sticky note system to guide you visually: 🟩 Green Notes → Main automation steps 🟦 Blue Notes → What to customize (IDs, prompts, expressions) 🟨 Yellow Notes → Optional logic and future upgrades 🟫 Gray Notes → Welcome + final “next steps” CTA Every group includes pre-filled nodes, dynamic expressions, and mock outputs so you can test quickly and scale confidently. How to customize this workflow? 📂 Swap Google Sheets for Airtable (better for teams or approvals) 📅 Add 30/60/90-day check-ins via Google Calendar 🤖 Plug in OpenAI to generate onboarding subtasks by role 📬 Auto-assign mentors or SlackBot reminders after 7 days 📊 Push Sheet logs into Notion or your HR dashboard Need custom logic? Email me at [email protected] Final notes This template was created by Velebit from Innovatio with modularity, scalability, and team experience in mind. All links included are official. No affiliate tracking, no sponsored content. 📜 A separate commercial license applies to the purchase via Gumroad, which includes extended rights, usage for client work, and scaling strategies.

⚖️ HR Sovereign: AI-Powered Onboarding Hub A high-fidelity employee onboarding engine: Intake → Role-Based Enrichment → AI Personalization → IT Provisioning. ⚙️ Core Sovereign Logic Enrichment:** Auto-classifies Tech, Sales, and Leadership roles to drive specific logic tracks. Intelligence:* Uses AI Agent (GPT-4)* to generate personalized welcome messaging based on job DNA. Atomization:* Merge PDF* node assembles role-specific policies and benefits into a single high-res package. Provisioning:* Dynamically generates Jira hardware/access tickets and Notion* tracking dashboards. Delivery:* Sends branded HTML emails via Gmail and announces hires on Slack*. 📋 Setup & Prerequisites Intake: Connect your HRIS (BambooHR/Workday) to the Webhook URL. Assets: Organize Drive folders into "Technical", "Leadership", and "Standard" templates. Tracking: Connect your Notion Onboarding Database and Jira IT Project. Metrics: Time_to_Provision, Engagement_Score, Document_Integrity_Hash.

🎧 IT Voice Support Automation Bot – Telegram Voice Message to JIRA ticket with OpenAI Whisper > Automatically process IT support requests submitted via Telegram voice messages by transcribing, extracting structured data, creating a JIRA ticket, and notifying relevant parties. 🧑‍💼 Who’s it for Internal teams that handle IT support but want to streamline voice-based requests. Employees who prefer using mobile/voice to report incidents or ask for support. Organizations aiming to integrate conversational AI into existing support workflows. ⚙️ How it works / What it does A user sends a voice message to a Telegram bot. The system checks whether it’s an audio message. If valid, the audio is: Downloaded Transcribed via OpenAI Whisper Backed up to Google Drive The transcription and file metadata are merged. The merged content is processed through an AI Agent (GPT) to extract structured request info. A JIRA ticket is created using the extracted data. The IT team is notified via Slack (or other channels). The requester receives a Telegram confirmation message with the JIRA ticket link. If the input is not audio, a polite rejection message is sent. 📌 Key Features Supports voice-based ticket creation Accurate transcription using Whisper Context-aware request parsing using GPT-4.1 mini Fully automated ticket creation in JIRA Notifies both IT and the original requester Cloud backup of original voice messages (Google Drive) 🛠️ Setup Instructions Prerequisites | Component | Required | |----------|----------| | Telegram Bot & API Key | ✅ | | OpenAI Whisper / Transcription Model | ✅ | | Google Drive Credentials (OAuth2) | ✅ | | Google Sheets or other storage (optional) | ⬜ | | JIRA Cloud API Access | ✅ | | Slack Bot or Webhook | ✅ | Workflow Steps Telegram Voice Message Trigger: Starts the flow when a user sends a voice message. Is Audio Message?: If false → reply "only voice is supported" Download Audio: Download .oga file from Telegram. Transcribe Audio: Use OpenAI Whisper to get text transcript. Backup to Google Drive: Upload original voice file with metadata. Merge Results: Combine transcript and metadata. Pre-process Output: Clean formatting before AI extraction. Transcript Processing Agent: GPT-based agent extracts: Requester name, department Request title & description Priority & request type Submit JIRA Request Ticket: Create ticket from AI-extracted data. Setup Slack / Email / Manual Steps: Optional internal routing or approvals. Inform Reporter via Telegram: Sends confirmation message with JIRA ticket link. 🔧 How to Customize Replace JIRA with Zendesk, GitHub Issues, or other ticketing tools. Change Slack to Microsoft Teams or Email. Add Notion/Airtable logging. Enhance agent to extract department from user ID or metadata. 📦 Requirements | Integration | Notes | |-------------|-------| | Telegram Bot | Used for input/output | | Google Drive | Audio backup | | OpenAI GPT + Whisper | Transcript & Extraction | | JIRA | Ticketing platform | | Slack | Team notification | Built with ❤️ using n8n