> 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/flow-studio/start-from-a-template.md). # Start from a template Pick a ready-made flow in the Templates gallery and let Flow Studio walk you through what it needs: your accounts, your sheets, a voice agent and when it runs. A template is a flow Dapta has already built for a common job, such as calling the leads in a Google Sheet or saving every call's result to a sheet or to HubSpot. Pick one, and a step-by-step setup asks only for what's missing, so the flow runs with your own accounts, sheets and agents. *** ## Find a template **Step 1:** In **Flow Studio**, click **New Flow**. The **Templates** gallery opens. **Step 2:** Browse or search: * **Most used** opens with the most popular templates, followed by a few from each group. The menu on the left lists the groups, named after what you want to automate, such as **Outbound calls**, **After the call**, **WhatsApp & chat** and **Data & CRM sync**, with how many templates each one has. * Or type what you want in **What do you want to automate?**, in your own words. Search reads the template's name, what it connects to and its description, ignores accents, and knows common words in English and Spanish: *meeting* or *calendario* finds the calendar templates. Every card says what the template does and what it works with, such as Google Sheets, a voice agent or a phone number. **Step 3:** Click a template to open it. **How it works** lists its steps, **You'll need** lists what to have ready, and the right side shows a preview of the flow. Click **Use this template**. {% hint style="info" %} Nothing fits? **Start from scratch**, in the gallery, builds a flow without a template. {% endhint %} *** ## Set it up step by step **Use this template** creates the flow and opens its setup. The left side shows **Setting up** with the flow's name, the steps, and **Your progress** below them. The steps depend on the template. The most common ones: | Step | What you choose | | --------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | **Your accounts** | The accounts the flow uses, such as your Google account or HubSpot. Each one shows **Ready** or **Not connected**, and you can connect it right there. | | **Choose your sheets** | The Google Sheet and the tab for each step that reads or saves rows, and which of your columns matches each one the flow needs. **Match automatically** pairs them for you. If your sheet is missing a column, **Add to Google Sheets** adds it. | | **Choose your voice agent** | The number the call is made from (**Call from**) and the voice agent that talks. | | **What the agent knows** | Which data goes to each of your agent's variables during the call. | | **Choose when it runs** | **Only when I press Run flow**, or **Automatically on a schedule**: the days, how often, the hours and the time zone. | | **Choose the agent** | For flows that start when a call ends: the voice agent that sends its finished calls to this flow. | Click **Continue** to move on, or click a step on the left to jump to it. A step marked **In the editor** needs something only you have, like an access token: you finish it in the flow editor, and it doesn't stop you from finishing the setup. *** ## Review and finish The last step, **Review**, shows what is ready and what is still missing. * When everything is set, it reads **Your flow is ready**. Click **Finish**, and Dapta shows you where to test and run the flow. * When something is missing, it says how many steps are left. **Finish** works once every required step is done. **Finish later** closes the setup and keeps what you've chosen so far. While steps are left, the flow editor shows **Finish setup** in the bottom-left corner of the canvas, with how many are left. Until you click **Finish**, running the flow opens the setup first. {% hint style="info" %} A template can carry sample values from the account it was built in. That is why a flow made from a template doesn't run until you've been through its setup. {% endhint %} *** {% content-ref url="/pages/Pz7BppzrVK4WkgMcbq4s" %} [Creating a New Flow in Flow Studio](/flow-studio/creating-a-new-flow-in-flow-studio.md) {% endcontent-ref %} {% content-ref url="/pages/PhTCpKrcrmDC04f2f00p" %} [Setting Up Triggers in Flow Studio](/flow-studio/setting-up-triggers-in-flow-studio.md) {% endcontent-ref %} --- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.dapta.ai/flow-studio/start-from-a-template.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.