GuidePlatformv1
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.
The Plugin (primary path)
With the plugin, you describe what you want in natural language and Claude builds it. The plugin's skills cover every task an integrator does — creating automations, assemblies, and integration suites; registering OAuth apps; testing; deploying to customers.
Covered in detail in Building with the Plugin.
The Editors (fallback path)
The Assembly Editor and Automation Editor are visual IDEs for the platform. They are valuable for:
- Inspecting what the plugin built
- Surgical edits to existing automations or assemblies
- Edge cases the plugin does not handle well
- Learning by clicking through a finished product
Covered in detail in Using the Editors.
When to use which
| Situation | Use |
|---|---|
| Building something new | Plugin |
| Substantial changes | Plugin |
| Operating at scale | Plugin |
| One-off inspection | Editor |
| Tiny config change not worth a prompt | Editor |
| Something surprises you and you want to see the diagram | Editor |
New integrators should default to the plugin. The UI is always there when you need it.
Related docs
Last updated May 4, 2026