Zum Inhalt springen
NEUMarktplatz und dein Team: Verkaufe, was du baust, und bekomm Pläne und Änderungen, die getestet sind, bevor du sie siehst. Neuigkeiten ansehen

Bibliothek / Aufgaben & Projektmanagement

Aufgaben & Projektmanagement

Motorsport-Technikprüfergebnisse mit OpenAI, Google Sheets und Slack weiterleiten

Wird durch einen Webhook für jede Fahrzeugeinreichung ausgelöst, prüft das Ablaufdatum jedes Sicherheitspunkts anhand seines Prüfzyklus und leitet das Fahrzeug an bestanden, bedingt, durchgefallen oder DQ weiter.

Was sie bewirkt

## 📘 WORKFLOW DETAILS Motorsports Tech Inspection Pass/Fail Router Scores every safety-equipment item's expiry against its rating-specific cycle, then routes the whole car into one of four inspection outcomes automatically. Who it's for: SCCA/NASA-style club racing tech inspectors and chief stewards who need consistent, fast pass/conditional/fail/DQ decisions at trackside. Execution walkthrough 1. Trackside tech-inspection app POSTs one car's submission (driver/car info + safety-equipment array) to the webhook. 2. Equipment array is split out; each item is deterministically scored for days-to-expiry against its class's expiry cycle (helmet 5yr, harness 2yr, etc.), in parallel with a class-metadata tag. 3. Branches merge and aggregate into one consolidated equipment-compliance score for the car. 4. Text Classifier reads the aggregated score plus inspector notes and routes to Pass / Conditional-Pass-Rework / Fail / Disqualify. 5. Each of the 4 classifier outputs is stamped onto a inspectionCategory field by its own Set node (Text Classifier itself never writes a field). 6. A 4-way Switch reads that field and drives 4 genuinely different terminal actions, with a nested If on the Pass path checking the grid-position eligibility cutoff time. 7. Every terminal action posts to the race-control timing API, archives to Google Sheets, and (for DQ) escalates to the chief steward on Slack before a final crew-channel notification. Node-by-node summary | Node | Role | |---|---| | Receive Car Inspection Submission | Webhook trigger | | Split Equipment Line Items | Fan-out per equipment item | | Compute Item Expiry & Pass Fail | Code: real expiry logic | | Merge / Aggregate | Fan-in + compliance score | | Classify Overall Inspection Result | AI: Text Classifier (4-way) | | Tag *Category (x4) | Per-branch field stamps | | Route By Inspection Category | 4-way Switch | | Check Grid Eligibility Cutoff Time | Nested If (secondary check) | | HTTP Request (x4) | Primary sink: race-control API | | Log Inspection Result Archive | Google Sheets archival log | | Slack (x2) | Crew notify + chief-steward escalation | Expected input: webhook POST (driver/car info + equipment array with dates/ratings). Expected output: one race-control API post + one archive row per car; DQ additionally pings the chief steward. Sticky colour legend: trigger=1, transform=2, ai=3, branch=4, storage=5, notif

Die Schritte

  1. Receive Car Inspection Submission
  2. Split Equipment Line Items
  3. Compute Item Expiry & Pass Fail
  4. Tag Equipment Class Metadata
  5. Merge Equipment Score Branches
  6. Aggregate Equipment Compliance Score
  7. Classify Overall Inspection Result
  8. Inspection Classification Model
  9. Tag Pass Category
  10. Tag Conditional Category
  11. Tag Fail Category
  12. Tag Disqualify Category
  13. Route By Inspection Category
  14. Check Grid Eligibility Cutoff Time

Insgesamt 21 Schritte.

Ähnliche Automatisierungen