Build

Build covers everything you do when something doesn't exist yet — a new automation, a connector for an app the catalog doesn't have, an action or trigger missing from an existing connector, a form to capture human input, or a multi-automation suite for a customer.

Describe what you want and Claude picks the right skill, or combination of skills, to match.

• Build an automation — "Connect HubSpot to Mailchimp." The most common entry point. Builds a single automation from a description.
• Build a connector — "We need to integrate with Acme CRM." Used when no catalog connector exists for the system you want.
• Build an action — "Add a 'create deal' action to HubSpot." Used when the connector exists but the operation you need doesn't.
• Build a trigger — "Add a webhook trigger to Zoom for completed recordings." Used when the connector exists but the trigger pattern you need doesn't.
• Build an integration suite — "Build a complete sync between HubSpot and Salesforce: contacts, companies, deals, plus a daily reconciliation." Used when the deliverable is a suite of automations that work together.
• Build a form — "Add a form so the customer can choose which warehouse to ship from." Used when the workflow needs human input.

Build an automation

You describe a single workflow in plain language. Claude figures out which trigger to use, which actions, what data to pass between them, and produces a draft you can review in the automation editor.

If your prompt is specific enough, Claude builds without questions. If it's vague, it asks one or two clarifying questions to narrow it down — "do you want to sync only new contacts, or also updates?".

Build a connector

If the catalog doesn't have a connector for the vendor you need, Claude builds one. You name the vendor; Claude searches for the API documentation, reads it, generates the connector, runs test calls against the real API to verify each operation works, and adds it to your catalog. The new connector is available the next time you ask Claude to build an automation that uses it.

Build an action

Catalog connectors don't always expose every operation their API supports. When the automation you describe needs an action that's missing — "create a deal in HubSpot," "upload a file to Box" — Claude offers to add it to the existing connector. Claude reads the API docs for that operation, generates the action with the right input and output fields, tests it against the live API, and saves it to the connector. No full rebuild.

Build a trigger

Same shape, different direction. Most connectors ship with the standard polling triggers their vendor supports, but webhooks, self-registering webhooks, and protocol-thread triggers often aren't yet wired up. When you describe an automation that needs a trigger pattern the connector doesn't have, Claude picks the right kind, generates the trigger logic, and verifies it fires on real events before adding it to the connector.

Build an integration suite

Used when the deliverable is several automations working together — a productized integration suite a customer would buy as a single thing. Claude scopes the work, decides what gets built in what order based on dependencies, and builds each individual automation in the suite.

Build a form

Some workflows can't run end-to-end without human input. You describe what input is needed and where in the automation it sits, and Claude generates a form that pauses execution, collects the input, and resumes.