> For the complete documentation index, see [llms.txt](https://docs.dapta.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.dapta.ai/dapta-mcp/skills/flow-studio.md).

# Flow Studio

These skills let you design new automations and understand the ones you already run.

{% hint style="info" %}
Building or changing a flow uses a **preview, then commit** flow. Every create, update, or run goes through a preview you confirm.
{% endhint %}

### flow-studio-flow-builder

**What it does:** Designs and builds Flow Studio automations for you. It asks about your goal, trigger, and integrations, then assembles a working flow (for example, pull leads from Google Sheets, loop through them, place voice calls, then update your CRM) and deploys it after you approve.

**Use it when:** You want to create a new automation, build a flow from a use case or a spec you paste in, or modify an existing flow (add a step, change a filter, remove a node).

**Try saying:**

* "Build me a flow that calls leads from a Google Sheet and updates the row with the result."
* "Create an automation that emails a summary after each WhatsApp conversation."
* "Add a follow-up email step to my existing appointment-reminder flow."

**You get back:** A summary of the flow it designed, a status table of which integration credentials are connected versus missing, a preview of what will be created or changed, and after you approve, the deployed flow with its URL and a checklist of any fields you still need to configure in Flow Studio.

**Writes data?** Yes, via preview then commit. Every create, update, or run goes through a preview you confirm.

**Behind the scenes:** `search_flow_templates`, `search_node_templates` (proven building blocks), `get_workspace_integrations` (wire up credentials), `validate_flow_structure` (auto-fix wiring), and `preview_create_flow` and `commit_create_flow` (or the update equivalents) to deploy.

***

### flow-studio-analytics

**What it does:** Inspects and reports on your existing Flow Studio automations. Lists your flows and folders, explains what a flow does, shows execution health, version history, configured integrations, and webhook details. Read-only, for understanding rather than building.

**Use it when:** You want to list or count your flows, see how often a flow runs and its error rate, find out who last edited a flow, check connected integrations, or get a flow's input schema or webhook URL.

**Try saying:**

* "List all the automations in my workspace."
* "How healthy are my flows over the last 30 days, any high error rates?"
* "Who edited the call-automation flow most recently, and what integrations do I have connected?"

**You get back:** Flow lists grouped by folder, per-flow execution stats (runs, successes, failures, average duration), version changelogs with author and timestamp, an integrations list, and flow input schemas or webhook URLs on request.

**Writes data?** No, read-only. For building or editing flows, Claude routes you to `flow-studio-flow-builder`.

**Behind the scenes:** `get_workspace_flows`, `get_flow_details`, `get_flow_execution_stats`, `get_flow_versions`, `get_workspace_integrations`, `get_flow_input_schema`, `get_flow_webhook_url`.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.dapta.ai/dapta-mcp/skills/flow-studio.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.