Build AOG parts release packets with OpenAI, Google Drive and Telegram

by Swapnil Mandloi ✓ · 2 views · created 2026-09-14 · Engineering, AI Summarization

What this workflow does

This AI workflow has 20 nodes and runs when an HTTP POST request hits its webhook URL. Along the way it connects OpenAI Chat Model, Google Drive and Telegram. It also calls mro.example over HTTP.

How it runs

Trigger: When an HTTP POST request hits its webhook URL.

1. Normalize Part and Aircraft Context (Code): runs custom JavaScript code
2. Split Requested Parts (Code): runs custom JavaScript code
3. Fetch OEM Eligibility (HTTP Request): calls an HTTP API
4. Fetch Serialized Life History (HTTP Request): calls an HTTP API
5. Fetch Airworthiness Directive Status (HTTP Request): calls an HTTP API
6. Merge: merges the data from its input branches
7. Calculate Release Blockers (Code): runs custom JavaScript code
8. Explain Traceability Decision (Basic LLM Chain): sends a prompt to an LLM, with model: Power Traceability Reviewer
9. Keep Part Decision (Code): runs custom JavaScript code
10. Route Part Release State (If): checks a condition and branches into true / false

…plus 8 more steps. See the full node list below.

Services it uses

OpenAI Chat ModelGoogle DriveTelegram

HTTP calls to: mro.example

Before you upgrade to n8n 3.0

Nodes used (10)

• Webhookn8n-nodes-base.webhook
• Coden8n-nodes-base.code
• HTTP Requestn8n-nodes-base.httpRequest
• Mergen8n-nodes-base.merge
• OpenAI Chat Model@n8n/n8n-nodes-langchain.lmChatOpenAi
• Basic LLM Chain@n8n/n8n-nodes-langchain.chainLlm
• Ifn8n-nodes-base.if
• Aggregaten8n-nodes-base.aggregate
• Google Driven8n-nodes-base.googleDrive
• Telegramn8n-nodes-base.telegram

From the author

Quick overview This workflow receives an AOG parts request via webhook, validates OEM eligibility, life history, and airworthiness directives via external APIs, and uses OpenAI to generate decision rationales. It then reserves eligible parts or quarantines…

View the original on n8n.io → Check your own copy