Building with the Plugin

You describe the integration in plain English; Claude builds it. "Build a daily sync that pulls new HubSpot contacts into Mailchimp" is enough — Claude matches the request to the right skill and starts.

What you're building

The thing you ship is an integration solution — usually a suite of automations that coordinate to do something useful: sync clients between two systems, route orders into a CRM, drive a multi-step workflow across a half-dozen services. Simpler integrations are sometimes a single automation. Either way, automations are the unit Claude builds.

If APIANT doesn't already have a connector for the service the automation talks to, Claude builds the assembly first. The assembly is the connector — it owns the credentials, the triggers, and the actions for that service. Once it exists, every automation in your account can reuse it.

Most of what Claude builds are automations and the suites that group them. Building an assembly is a prerequisite step, not a goal.

Build automations

The mainline workflow: describe the integration, Claude ships it.

• Setup — install, update, or repair the APIANT plugin via the apiant-cli.
• Build — create automations, suites, and forms.
• Edit — modify live automations safely.
• Test & Deploy — end-to-end validation and dev → prod.
• Automation Patterns — reusable building blocks Claude applies as it builds.
• Closed-Loop Learning — how Claude gets better at building APIANT automations.
• Ops & Support — monitor, diagnose, alert handling.

Build assemblies (when needed)

If the service doesn't have a connector yet, Claude builds the assembly first, then the automation that uses it.

• App Connectors — what connectors are, the three auth flavors, and OAuth registration.
• Assembly Triggers — every way an automation can start.
• Assembly Actions — every CRUD operation against an external service.