CrewAI Studio: How to Build Crews and Flows Without Code

CrewAI Studio is the visual builder inside CrewAI AMP (Agent Management Platform), the paid platform that sits on top of the open-source CrewAI framework. You describe an automation in plain language, a Crew Assistant drafts the agents, tasks, tools and inputs, and you refine the draft on a canvas or in chat. Studio is included on the free Basic plan as well as on Enterprise, so opening it costs nothing on CrewAI's side^[1]. Your model bill is another matter. Basic allows 2 automations and 50 workflow executions a month, which makes Studio a fair place to prototype and a tight place to run production work. The real catch is the code export. It only goes one way.

Where Studio sits between the framework and AMP

Studio belongs to AMP, not to the Python package. CrewAI's docs say the drag-and-drop task builder is part of the platform and absent from the open-source install, so a developer running crewai run on a laptop never sees it. The builder is not new, either. CrewAI announced Studio v2, an assistant paired with a drag-and-drop canvas, in May 2025, included it in the platform at its October 2025 launch, and in July 2026 released the current Crew Studio, which added Flow nodes and source export. Projects built there deploy to the same AMP runtime that coded crews use, not to a separate prototype environment.

CrewAI pitches Studio as a division of labor: business users build on the canvas, while engineers export readable code they can review, version and extend. That pitch holds for the first handoff. It weakens afterward, for reasons the export section spells out. The agent side also has a form-based Visual Agent Builder with real-time testing and a template library, and both plans list agentic workflow templates, so a first project rarely starts from an empty screen.

Step one: connect a model with your own key

Studio builds nothing until an LLM connection exists. CrewAI's setup guide asks for a connection that uses your own provider key, with OpenAI or Azure as the model provider, which means every token the Crew Assistant and your agents consume is billed by that provider rather than by CrewAI^[2]. That is the cost line a free plan label hides. For Azure OpenAI, the guide sets up an LLM Connection with AZURE_DEPLOYMENT_TARGET_URL and AZURE_API_KEY, marks it as the Crew Studio default, and expects the Azure endpoint to be open to all networks.

Tools follow the same rule. When a generated agent uses a search tool that needs a key, such as Serper, that service bills you directly, outside AMP. Teams whose Azure endpoints are restricted to private networks will have to change that setting before Studio can reach the model, so it pays to settle the network question with whoever owns the Azure account before the first build session. Without the connection, the assistant has no model to draft with.

Building a crew: describe it, then shape the canvas

A crew in Studio starts as a sentence. You type or speak a description of the job, or pick one of the built-in starter prompts, and the Crew Assistant generates agents, tasks, tools and inputs for it. Each agent carries the same parts it would have in code: a role, a goal, a backstory and its tools. The draft then appears on a visual canvas where agents and tasks are connected nodes. Chat and drag-and-drop share one state, so you can ask the assistant for a reviewer agent and then drag a task to a new position without either edit undoing the other. A practical order of work looks like this:

1. Describe the outcome you want, including the inputs a run will receive.
2. Read every generated agent's role, goal and backstory, and tighten the vague ones.
3. Check which tools each agent was given and whether any of them needs a paid key.
4. Rewire tasks on the canvas until the order matches how the work really flows.
5. Run a test in the Execution view, then deploy or download.

The Execution view is where a draft earns trust. It shows an event timeline, detailed logs and test runs before you publish, so you can see which agent called which tool and where a task drifted. One reviewer reports lag when running multi-step workflows in Studio. Another used it to test workflows without coding every piece first. Both comments fit a tool that is strongest at drafting and checking.

Building a flow: Single Agent, Crew and Router nodes

Studio also builds Flows, not only crews, but the option reaches organizations gradually: CrewAI began rolling it out gradually in July 2026, and some organizations may not see it yet^[3]. Where it is available, a flow is assembled from three node types. A Single Agent node handles one step with one agent. A Crew node embeds a whole multi-agent team as one step. A Router node branches on a condition. CrewAI's guidance on choosing is plain: a crew suits agents collaborating autonomously toward a goal, while a flow gives a defined sequence with explicit branches for predictable, repeatable runs.

Studio can design the flow from a plain-language description too, creating the steps, configuring the agent inside each one and wiring up integrations. CrewAI's July 2026 post says Studio connects to more than 1,000 applications across CRM, support, messaging, productivity, marketing and developer tools. A finished flow project can be run, inspected in Output and Traces tabs, deployed, shared or downloaded as source code. Our guide to CrewAI Flows shows the same structure in Python, where decorators take the place of nodes.

Agents are reusable. An agent built in a Studio flow can be published to the organization's Agent Repository, pulled into other flows and kept in sync across the organization, and the private agent repository appears on both plans. That turns a well-tuned researcher or reviewer agent into a shared component instead of something every builder recreates, which matters most when several people in one company draft automations in parallel.

Deploying from Studio, and what the free plan holds

Deployment starts from the builder itself: Studio can download the generated code or deploy the crew straight to AMP. Once deployed, every crew or flow becomes an automation with its own API, triggers, traces and access rules. Triggers can be a cron schedule, an app event from services such as Gmail, Outlook, Slack or HubSpot, or a REST API call; Salesforce triggers are set up with CrewAI's support. The pricing table lists standard tools and triggers on both plans and enterprise connectors only on Enterprise, so check which connectors your plan includes. A deployed automation can also be chatted with, exported as a React component or exported as an MCP server, and the dashboard filters automations by source, so Studio builds sit apart from GitHub and ZIP deployments.

Those Basic limits decide how far a Studio prototype can travel. Fifty workflow executions a month comes to about 1.7 a day on a 30-day month, by our arithmetic, and with two automations allowed, two deployed projects fill the plan. CrewAI's pricing page prints no dollar price for Enterprise; it is sold on request, and our CrewAI pricing breakdown walks through the full plan table. On Enterprise, where role-based access control sits, Studio projects are shared from a Share button, and everyone on the default Member team can open every Studio project read-only.

The export only goes one way

Studio's export deserves a decision before you build, not after. Downloading a project as a ZIP is a one-way move: changes made to the code are not reflected in Studio, the code cannot be imported back, and redeploying the customized version creates a separate code-sourced automation^[4]. That new automation has no Studio visual editor, versioning or validation. The visual project and the code project then live side by side, and on Basic the second one takes the other automation slot.

So the real question is who will maintain the automation. If business users will keep editing it, keep it in Studio and treat the canvas as the source of truth. If engineers will extend it with custom tools, hooks or tests, export once, early, and treat the download as a scaffold rather than a round trip. CrewAI says exported Studio code is readable enough to review and put under version control, but its docs state that edited code cannot be imported back into Studio. Teams weighing governance as well, from SSO to PII redaction, can work through our CrewAI buyer's checklist before committing.

Studio or code for your first CrewAI automation?

Start in Studio when the person who understands the job does not write Python and the work fits inside two automations on Basic: the assistant drafts the crew, the canvas makes it legible, and the Execution view shows whether it works before anything ships. Start in code when engineers own the result from day one, because the export cannot come back, and an automation that will grow in Python is better born there. Either way, connect your own model key first. That provider bill is the cost Studio never shows.