# Botpress Tutorial: Build Your First AI Agent in Studio *How-to — 2026-10-19 — by Mahmoud Zalt* A hands-on walkthrough of Botpress Studio: signing up, reading the canvas, writing instructions, testing in the Emulator, and publishing your bot. **Short answer.** **You build a Botpress agent by creating a bot, writing its instructions, giving it knowledge, testing it in the Emulator, then publishing it.** Sign up, choose Start building or Build my agent, and Botpress walks you through a first bot. Then open Botpress Studio, where a canvas of nodes holds your logic, the Emulator sits in the side panel behind Cmd or Ctrl plus E, and a Publish button in the upper right makes the bot live. **About this guide.** This guide is based on publicly available information and Botpress's own documentation, checked on 17 August 2026. Sistava is not affiliated with Botpress. Interfaces and pricing change often, so confirm the current steps in their documentation before you rely on them. Most people arrive at Botpress with one bot in mind. A support assistant that answers the same eight questions, or a lead qualifier on the pricing page, or something that reads the docs so nobody has to. The product can do all of that. The first hour goes on vocabulary instead: workspaces, Studio, workflows, nodes, cards, the Emulator, publishing. This guide walks that hour. Two things make this easier than it looks. Botpress starts you with a working bot rather than a blank page, and its newest node type does a lot of the thinking on its own. You do not have to draw every branch of every conversation before you see something reply to you. ## What is Botpress Studio? Botpress Studio is the editor where you build, test and manage your bot. Botpress describes it as an integrated development environment for building, testing and managing AI agents and chatbots, combining development tools with a visual drag and drop interface. In practice you are looking at a canvas. Your conversation logic lives in boxes called nodes, connected by lines. A tutorial write-up from DataCamp describes the working layout as a canvas of nodes and connections, a left sidebar holding workflows, system flows, variables and schemas, and a right-hand panel that inspects whichever node you have selected. One thing worth knowing before you read any other tutorial. Botpress has an older generation, v12, whose documentation now lives on a separate site, and the current product is Botpress Cloud. Older tutorials describe v12 screens that no longer match. If a guide mentions panels you cannot find, that is usually why. ## What is a Botpress bot made of? A bot is made of workflows, and a workflow is made of nodes. A node is a single step in the conversation: it runs a sequence of actions, then hands over to the next node. The actions inside a node are called cards. Botpress documents nine node types. You will use two of them constantly and meet the rest as you go. - **Standard Node: **runs its cards one by one, top to bottom, then transitions to the next node. This is your deterministic building block. - **Autonomous Node: **uses an AI model to decide what to say and which of its tools to run, based on instructions you write. - **Start Node: **the entrance to every conversation. It exists only in the Main Workflow, cannot be modified or deleted, and cannot hold cards. - **Entry Node and Exit Node: **the way into and out of any workflow other than the Main Workflow. An Exit Node passes variables back to the parent workflow. - **End Node: **ends the conversation, clearing the session and resetting the bot's state. - **Triggers, Exception Handlers and Comments: **nodes that fire on a specific event, nodes that run when something errors inside a workflow, and annotations that do nothing at runtime. To connect two nodes you select and hold the right edge of the node you are transitioning from, drag outwards, and release on the left edge of the node you are transitioning to. That gesture is the whole wiring model. ## How do you build your first Botpress agent, step by step? Create the bot through the guided flow, open Studio, write instructions, attach knowledge, test in the Emulator, then publish. Botpress's own quickstart splits this into three phases: build, optionally fine-tune, then deploy. 1. **Sign up and let Botpress start the bot for you** — Log in, then choose Start building or Build my agent and follow the on-screen prompts. Botpress says a bot is ready to test and deploy within minutes this way. If you would rather begin from an empty canvas, choose Skip and go straight to Studio. 2. **Look at the preview before you change anything** — The guided flow hands you a bot already trained on the sources you gave it and styled toward your branding. Chat with it first. What it already answers correctly tells you what not to build. 3. **Open Studio and select the node on the canvas** — Selecting a node opens its settings in the inspector panel. DataCamp's walkthrough starts a support bot by writing instructions into the autonomous node the canvas opens with, which is the fastest path to a bot that behaves the way you want. 4. **Write the instructions** — The Instructions field on an Autonomous Node is its main prompt. Botpress's guidance is direct about this: the more specific you are, the better the decisions. Name the job, the tone, what it must never do, and what to do when it does not know. 5. **Give it knowledge** — Go to the Knowledge section of your agent's menu and choose + Add Knowledge Source, or + Add Knowledge Base to create a new one. A website source or a handful of documents is enough for a first pass. 6. **Test in the Emulator** — Press Cmd or Ctrl plus E to toggle the Emulator open in the right-side panel. It shows inline logs as it goes, including bot events, Knowledge Base activity and results, code execution, AI Task operations, workflow transitions and variable capture attempts. 7. **Publish** — Select Publish in the upper right of Studio. This makes the bot live and includes every change since your last publish. Each publish creates a new version, so you can track changes and revert to an earlier one. 8. **Put it somewhere people can reach it** — Botpress's two documented paths are embedding it on your website with Webchat, or connecting it to an external channel or service through an integration. If that felt like a lot of moving parts for one assistant, that reaction is the honest one. Set-up work like this is exactly what we removed at Sistava. Rather than assembling nodes, instructions and knowledge sources into something that behaves, you hire an AI Employee and tell it in plain English what you want handled. It has the tools connected already, it asks when it is unsure, and it sets itself up. Both approaches are legitimate. Botpress gives you a canvas and full control over every branch, which is the right trade when the conversation genuinely needs that control. The question is only whether your first bot needs it. ## How do you test a Botpress bot before publishing? Use the Emulator inside Studio. It is a chat window in the right-side panel, toggled with Cmd or Ctrl plus E, and it doubles as a debugger by printing what the bot did between messages rather than only what it said. From its top-right menu you can start a new conversation as the same user, start again as a different user, or simulate a timeout event. Testing as a fresh user matters more than people expect, because a bot that behaves once it has context often behaves differently on the first message. **Emulator conversations are free of one cost, not both.** Botpress documents this precisely: conversations in the Emulator are not saved, and bot invocations from the Emulator are not counted against your usage quota, but AI operations are. Testing is cheap, not free. Long looping tests with a large model still spend. ## What does publishing a Botpress bot actually do? Publishing deploys the bot and makes it live for real users. It carries over every change made since the last publish, and it creates a new version of the bot at that moment. That versioning is your safety net. If a change makes the bot worse in a way you only notice from real conversations, you have a prior version to return to. Publish in small increments and that net is useful. Publish once a fortnight with forty changes in it and it is not. ## What trips people up on their first Botpress bot? Three things, none of which are in a getting-started guide. The first is the version confusion above: a tutorial describing NLU tabs and Q and A panels is almost certainly describing v12, not the current product. The second is cost shape. DataCamp's write-up makes the point plainly: pricing scales with model calls, so more elaborate logic costs more to run. A bot that thinks in a loop over every message is not the same running cost as one that answers and stops. The third is over-confirming. The same write-up notes that too many are-you-sure prompts train users to click through them without reading, which defeats the reason you added them. Confirm the irreversible things, let the rest flow. There is also a developer path if the canvas is not how you want to work. DataCamp documents a command line route: install Node 18 or newer, install the Botpress CLI package globally, authenticate, initialise a project folder, and deploy from there. Windows users may need to adjust the PowerShell execution policy before the command is recognised. ## FAQ ### Do you need to know how to code to use Botpress? No. Botpress Studio is a visual editor and Botpress describes it as combining development tools with a drag and drop interface. You build by placing nodes, adding cards and writing instructions in plain language. There is a command line path for developers who prefer it, and cards that run code when you need them, but a first working bot does not require either. ### How long does it take to build a first Botpress bot? Botpress says the guided flow can have a bot ready to test and deploy within minutes. A DataCamp tutorial reports building a basic support bot, with instructions and a website knowledge source, in around five minutes and finding it already handled a fair amount of routine support. Anything with branching logic, integrations and edge case handling takes considerably longer, and testing every branch is the part people underestimate. ### Where is the Emulator in Botpress Studio? In the right-side panel. Press Cmd or Ctrl plus E to toggle it open or closed. As well as the chat itself it prints inline logs of bot events, Knowledge Base activity and results, code execution, AI Task operations, workflow transitions and variable capture attempts, so you can see why the bot did something rather than only what it said. ### Does testing in the Emulator use up my quota? Partly. Botpress documents that Emulator conversations are not saved and that bot invocations from the Emulator are not counted against your usage quota, but that AI operations are. So the conversation itself is not metered as a bot invocation, while the model calls it triggers still cost you. ### What is the difference between Botpress Cloud and Botpress v12? Botpress v12 is the earlier open source generation. Its repository directs new users to Botpress Cloud and notes that v12 documentation moved to a separate site after Cloud launched. Botpress Cloud is the current product and the one the main documentation covers. This matters when following tutorials, because guides written for v12 describe an interface that no longer matches. ### What happens when I click Publish? Your bot goes live, including every change made since the last time you published, and a new version of the bot is created. Botpress notes that this versioning lets you track changes and revert to a previous version if you need to, which is why publishing in small increments is worth the habit. ## Sources - [Botpress documentation, ](https://botpress.com/docs/studio/get-started/quick-start/)Quickstart - [Botpress documentation, ](https://botpress.com/docs/studio/introduction/)Introduction to Studio - [Botpress documentation, ](https://botpress.com/docs/studio/concepts/nodes/introduction)Nodes - [Botpress documentation, ](https://botpress.com/docs/studio/concepts/nodes/autonomous-node)Autonomous Node - [Botpress documentation, ](https://botpress.com/docs/studio/concepts/emulator)Emulator - [Botpress documentation, ](https://botpress.com/docs/studio/get-started/manage-your-agent/knowledge/)Add knowledge sources - [Botpress documentation, ](https://botpress.com/docs/tutorial/introduction/)Tutorial introduction - [DataCamp, ](https://www.datacamp.com/tutorial/botpress)Botpress Tutorial: Build and Deploy AI Chatbots - [GitHub, ](https://github.com/botpress/v12)botpress/v12 repository **Tags:** botpress, chatbot-tutorial, ai-agent-tutorial, no-code-chatbot, conversational-ai