007CASE STUDY

Browser Automation

FLOWBROWSE

ROLE

SOLO BUILD — FULL PLATFORM

TIMELINE

SHIPPED · ACTIVELY MAINTAINED

SCOPE

Canvas editorBrowser automation engineMultiplayerObservability

STACK

Next.js 16React FlowTrigger.devBrowserbaseLiveblocks
FLOWBROWSE — screenshot

OVERVIEW

Wire nodes together on a canvas — open a page, click something, extract data, run an autonomous agent, send an email — and Flowbrowse turns that graph into a durable background job driving a real, recorded browser session.

The canvas is a React Flow graph with six node types — Open URL, Act, Extract, Observe, Agent, and Send Email — validated against missing triggers, disconnected graphs, and cycles before it ever runs. Multiple people can edit the same workflow at once: Liveblocks drives live cursors, presence, and avatars across the team.

Execution is real, not simulated: Stagehand drives an actual browser session through Browserbase, orchestrated as a durable Trigger.dev task that walks the graph node by node with live status streamed back to a run console — step-by-step logs, formatted JSON output, and, on the Pro tier, full session-replay recordings as HLS streams.

Built for teams, not just solo scripts: Clerk organizations scope every workflow, Clerk Billing gates Pro features like the Agent node and replay, Neon Postgres with Drizzle stores graphs and run history, and Sentry covers errors and tracing across both the Next.js app and the Trigger.dev runtime.

OUTCOMES

6node types: URL · Act · Extract · Agent…
213commits, actively developed
REALTIMEmultiplayer canvas + live run console
No-code automation that's actually observable: every run is a real browser you can watch.
© 2026 RUSHIKESH PALANDEBACK TO TOP ↑
© 2026 RUSHIKESH PALANDE. ALL RIGHTS RESERVED.