Files

T

NuklearRabbitandClaude Sonnet 5 e0c107a94a n8n: store cleaned workflow definitions as repo source of truth

Move the two live-validated workflows into n8n/workflows/ (credential-
based auth referenced by name only, no secret values), add a manifest
covering all 4 canonical workflows and a read-only drift-check script
against n8n's Public API. Retire the pre-integration root-level starter
files that still carried the literal-token pattern, and repoint the
Unraid deploy scripts, Makefile targets and runbook at the new files.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>

2026-08-04 13:34:51 +02:00

3.1 KiB

Raw Blame History

n8n workflow manifest

Source of truth for the four canonical Fleet Ops n8n workflows. Definitions in this directory are cleaned exports of the live workflows on https://n8n.itworx.tech — credential values are never embedded; nodes reference named n8n credentials instead. Run n8n/workflows/check_drift.py to compare a live workflow against its repo definition.

1. Fleet Ops — Vehicle Return Orchestration

Field	Value
File	`fleet-ops-vehicle-return.json`
Purpose	Orchestrate the post-return follow-up (cleaning vs. attention-required) once Fleet Ops emits a `vehicle.returned.v1` outbox event, and report the result back to Fleet Ops.
Trigger	Production webhook, `POST /webhook/mobilityops-return`, Header Auth (`Fleet Ops Webhook Trigger Token`)
Event contract	`contracts/events.schema.json`, `event_type: vehicle.returned.v1` (envelope: `event_id`, `event_type`, `occurred_at`, `correlation_id`, `aggregate`, `data`)
Required credentials	`Fleet Ops Webhook Trigger Token` (Header Auth, on the trigger); `Fleet Ops Service Token` (Header Auth, on the outbound HTTP call)
Live workflow ID	`mobilityops-return-processing`
Active status (as of 2026-08-04)	Active / Published
Checksum (sha256)	`e13a3087269fc97019a7adf6c6a6a4ee4bd354c2dd7167d4966d4753a48e970e`

2. Fleet Ops — Scheduled Data Quality Scan

Field	Value
File	`fleet-ops-data-quality-scan.json`
Purpose	Periodically (and on-demand) run the Fleet Ops data-quality scan and summarize created-issue counts per rule.
Trigger	Schedule Trigger (hourly, Europe/Brussels instance timezone) + Manual Trigger for on-demand test runs
Event contract	N/A — HTTP-triggered scan call, no inbound event envelope. Request: `POST /api/v1/integrations/n8n/scheduled-scan`, Header Auth.
Required credentials	`Fleet Ops Service Token` (Header Auth, on the scan HTTP call)
Live workflow ID	`mobilityops-scheduled-quality-scan`
Active status (as of 2026-08-04)	Active / Published
Checksum (sha256)	`cc30b28b07dad9f9908a6ea0c564ec4c2f362a3ed71b7e97a7b6894408bb7e2e`

3. Fleet Ops — RAGcore Procedure Sync

Not yet built. Blocked on a RAGcore application credential (scope sources:sync) for the fleet-ops application, to be provided by the project owner. Will sync n8n/workflows/fleet-ops-ragcore-procedure-sync.json against the real RAGcore contract (POST /v1/uploads, GET /v1/knowledge-spaces, etc. — see contracts/ragcore-contract-assumptions.md and the live inspection notes in docs/live-ai-integration/n8n-current-state.md).

Field	Value
File	`fleet-ops-ragcore-procedure-sync.json` (not yet created)
Live workflow ID	—
Active status	Not built

4. Fleet Ops — Workflow Error Handler

Not yet built. Central error workflow to be attached to workflows 1-3 via n8n's per-workflow "Error Workflow" setting. Reports bounded, secret-free failure details to a new Fleet Ops automation-failure endpoint.

Field	Value
File	`fleet-ops-error-handler.json` (not yet created)
Live workflow ID	—
Active status	Not built

3.1 KiB Raw Blame History