Skip to main content

Workflow Architecture

How Workflow docs are organized for FleetStudio automation (n8n and related scripts).

System Overview​

Each production automation has one markdown doc under docs/ai-workflow/workflows/. The index lists every active workflow. Runtime still lives in n8n (or a script host); this site is the knowledge base, not the executor.

Architecture Diagram​

graph TB
    subgraph Docs["fleet-docs - Workflow"]
      Overview["overview.md"]
      Index["workflows/index.md"]
      Pages["individual workflow *.md"]
    end

    subgraph Runtime["Automation runtime"]
      N8n["n8n workflows"]
      Scripts["Python / scripts"]
    end

    subgraph Externals["Integrations"]
      Slack["Slack"]
      Sheets["Google Sheets"]
      Sam["SAM.gov / TED"]
      Brevo["Brevo / Lemlist"]
      Timesheet["Timesheet"]
    end

    Overview --> Index
    Index --> Pages
    Pages -.->|"documents"| N8n
    Pages -.->|"documents"| Scripts
    N8n --> Slack
    N8n --> Sheets
    N8n --> Sam
    N8n --> Brevo
    N8n --> Timesheet
    Scripts --> Brevo

How to read this diagram​

Arrows mean flow / dependency / "talks to", not button clicks. Dashed lines mean docs describe a runtime; they do not execute it.

Design Decisions​

Decision: One markdown file per workflow​

Context: Teams need a single place for purpose, trigger, and steps.
Decision: Each workflow gets its own .md under workflows/.
Consequences: Easy sidebar entries; index stays the catalog.

Decision: Docs site is not the runner​

Context: n8n / scripts already execute automations.
Decision: Document here; run elsewhere.
Consequences: No fake npm package or API platform in these docs.

Decision: Project label is Workflow​

Context: Sidebar previously said "AI Workflow".
Decision: Use Workflow as the project name.
Consequences: Clearer label; folder path stays docs/ai-workflow/ for stable URLs.