Understanding APIANT
The mental model behind APIANT — the four core objects, how data flows through them, and how they are built from lower-level pieces.
Understanding APIANT covers the mental model: the four objects you'll hear about, the loop a running automation follows, and how things actually get built.
You can build a working automation without reading any of this. Claude handles the model implicitly. Skim it now, come back when something Claude tells you needs more context.
In this section
- The Four Core Objects — automations, assemblies, connectors, and integration suites.
- How Data Flows — the loop a running automation follows: trigger fires, actions run, state persists.
- How Things Get Built — Claude-first construction model and when to fall back to the visual editors.
In this section
The Four Core Objects
Automations, assemblies, connectors, and integration suites — the four building blocks every APIANT user encounters.
How Data Flows
How a trigger fires, how actions run, how data is mapped between them, and how state is persisted across executions.
How Things Get Built
The two ways to construct things on APIANT — the Claude Code plugin (primary) and the visual editors (fallback) — and when to use each.