Introduction

Flowra is one place to build agents and workflows, connect apps, and ground them in your data. You run them from chat, messengers, schedules, widgets, MCP, or your own API — for a single team or many end customers under one project. Do day-to-day work in the dashboard (often starting in chat). Use the API when the same capabilities must live inside your app.

Choose your path

Use the product

Learn the mental model, then build your first agent in chat — no code required.

Build with the API

Get an API key, call tools and workflows from your backend, and open the API reference.

Start with concepts: How Flowra works. For Cursor/Claude or SaaS tenancy, see Next steps below.

How the pieces connect

Account → Project (shared setup + API key)
       → External user (connections, agents, knowledge, tables, threads)
         → Entry points: Chat | Channels | Schedule | Events | Widget | API | MCP

Nested detail: Projects and API keys. Also: External users switcher and Entry points and channels.

What you can build

Support and ops agents with tools, knowledge, and channel replies
Scheduled reports and event-driven workflows
Customer-facing chat embeds (widgets)
Multi-tenant SaaS where each customer connects their own accounts
Custom tools (JS/Python), MCP in Cursor/Claude, sandbox and live browser when you need them

Next steps

How Flowra works — Concepts and glossary
First agent in chat — Product quick start
Toolkits and tools · Skills
API quickstart — First authenticated request
MCP in the dashboard — Cursor / Claude and project MCP
Multi-tenancy — x-username and per-user isolation
API reference — Endpoints and schemas

Getting started

In the dashboard

Try this

Choose your path

Use the product

Build with the API

How the pieces connect

What you can build

Next steps

​Choose your path

Use the product

Build with the API

​How the pieces connect

​What you can build

​Next steps

Choose your path

How the pieces connect

What you can build

Next steps