Workflows & automation
OrgFlow: workflows from the administrative sediment
OrgFlow asks whether organizational communications can be recovered into a process model, and from there into a workflow that an automation platform can actually run.
Read about OrgFlow
An organization rarely explains itself in diagrams. It explains itself in smaller and less dignified ways: an email asking whether something has been approved, a message saying the invoice has gone astray, a call in which three people discover that the “usual process” was usual only to one of them. Reminders, exceptions, confirmations, apologies, attachments, and that most revealing of institutional artifacts: the follow-up. OrgFlow starts there — a prototype (PDF) that asks whether those traces can be recovered into a process model, and from there into a workflow that an automation platform can actually run. My contribution lived mostly in the last stretch: the conversion agent that translated formal process elements into n8n workflow JSON, the structural-validation layer, the code-interpreter environment that let the agent assemble workflows through helper functions rather than hand-writing brittle objects, and the trace checks that compared what the workflow actually did against what the process model said it should do. Less about asking a language model to be clever, and more about giving it tools, guardrails, and a narrow corridor in which cleverness could do less damage. Its failures are part of the point: a workflow that looks plausible on paper becomes, in execution, a very patient machine waiting for a node that will never arrive.








