Flowblocks
Dashboard
Dashboard
Getting Started
QuickstartHow it works
Building Workflows
The canvasGenerating with AIPreview and runsSharing and collaboration
Steps
OverviewAgentBranches and loopsGuardrails and approvalState and data
Connectors
OverviewGoogleMicrosoftDropboxOther providersMCP servers
Develop
Embedding the builderNode SDKREST API
Reference
Self-hostingEnvironment variablesLimitsFAQ

All systems operational

Getting Started

Quickstart

Build a workflow, connect a tool, and run it in the preview chat. Takes about five minutes.

This page builds a workflow that takes a chat message, calls a model, and replies. You then run it and read the record of each step.

Prerequisites

  • A Flowblocks account at app.flowblocks.dev, or a local install.
  • A key for at least one model provider: OpenAI, Anthropic, or xAI.

Start a workflow

On the home page, describe what you want in a sentence, for example "Answer support questions, and ask before issuing a refund". Flowblocks drafts a graph for you. If you would rather draw it yourself, open a blank canvas instead.

Every workflow begins with a Start step, which receives the chat message, and finishes at an End step, which returns the last output.

Add an Agent step

Pick Agent from the palette on the left. It appears on the canvas; drag it where you want it, then draw a connection from Start to the agent and from the agent to End.

Select the agent to open its settings on the right. Choose a provider and a model, and write the instructions the model should follow.

Connect a tool

In the agent's settings, pick a connector such as Gmail or Google Drive and approve access in the provider's window. Then choose which of its tools the agent may call.

Tip

Select only the tools this step needs. The model can call any tool you leave enabled.

Run it

Press Run to open the preview chat and send a message. The reply streams back as the graph runs.

Each run is saved. Open the Runs tab to see every step's input, output and timing.

Add an approval

Add a Human approval step before any action that needs sign-off. The run pauses there until someone approves or rejects it, then follows the matching path.

Next steps

How it works

How a run moves through a workflow.

Steps

All twelve step types.

Connectors

54 built-in connectors, and any MCP server.

Embedding the builder

Render the builder in your own app.

On this page

PrerequisitesStart a workflowAdd an Agent stepConnect a toolRun itAdd an approvalNext steps