Core Workflow Primitives Across Platforms
Explore how to design and build automation workflows using core primitives such as triggers actions routers data mapping and run histories. This lesson helps you apply a platform-agnostic approach to support inbox triage workflows across n8n Zapier and Make while avoiding common pitfalls of similar but different components. Learn to map concepts and evidence to each platform for reliable workflow operation and easier debugging.
We'll cover the following...
A support inbox triage automation can produce the same outcome in any platform, yet the build often stalls because each tool uses different nouns for the same moving parts. The fastest way past that friction is to describe the workflow without naming any platform and then translate it into a small set of shared primitives. Along the way, we'll also uncover a few "near-neighbor" traps components that look interchangeable across platforms but behave very differently once a run actually executes. Scope is a platform-agnostic map for the support inbox triage workflow.
Here is the workflow sketch in plain language.
Ingest message
Call LLM triage
Branch by priority and topic
Notify or escalate
Log a run record
Fallback to human review on errors or when
needs_human=true
Two of those steps can also hand the case to a person instead of continuing: the LLM call when it errors, and the branch when triage sets needs_human=true. That fallback to human review is an exit from the flow, not a sixth step at the end, which is how the diagram below shows it. ... ...