TL;DR: Flows is now a first-class way to build and share logic across your solution. You can run it from apps, expose it as an API, serve it to AI agents over MCP, or run it on a schedule. Here’s what shipped recently, what we’re building now, and where we’re headed.
A flow is a reusable block of server-side logic, a function at the solution level. Define an integration or piece of business logic once, then reuse it everywhere: called from apps and other flows, exposed as an HTTP API, served to AI agents, or run unattended on a schedule.
Recently launched
MCP servers. Turn a flow into a Model Context Protocol server so AI agents can call your logic as tools. Each non-private action becomes an MCP tool, advertised automatically from its name, description, and parameters. The built-in MCP Inspector lets you document and test those tools per flow, in any environment.
API endpoints. Expose any flow as an authenticated HTTP endpoint for external systems, whether that’s webhooks, integrations, or a public API. Endpoints support incoming data mapped to schemas and custom JSON responses, and you can download an OpenAPI spec or test live in the API Explorer.
Schedules. Run a flow automatically on a cron expression under a chosen service account. Ideal for nightly syncs, periodic refreshes, and other unattended background work.
Streaming data from flows to apps. Outputs marked Streamable are delivered to the caller incrementally as they’re written, not just at the end of the run, so an app can populate a list live while a long-running flow works. Combined with the new Streaming Web Request node, you can stream data straight from an external API into your app.
Calendar (platform-wide bonus). See all your scheduled flows, services, and deploys together in one place, across every environment. It’s a single view of everything that’s set to run and everything that’s shipping, so you can spot conflicts and know what’s coming at a glance.
What we’re building now
Closing the last parity gaps. Most of the action-node library now runs in flows. The remaining pieces are in the final stretch: user account management and file objects are now live. Multi-reference and multi-enum property support is coming next week. The goal is simple: anything you can do in a service, you can do in a flow.
Devtools for flows. A dedicated developer-tools experience for inspecting flow runs, with step-by-step execution, data views, and live log streaming, so debugging a flow feels as good as debugging an app.
Improved logging and observability. We’re investing in logging and observability for flows that goes well beyond what apps and services offer today, giving you far better visibility into what ran, when, and why.
Where we’re headed
Migrating from services to flows. As parity lands, flows become the default. We’ll make it easy to migrate existing service logic and standardize new solutions on flows.
App action parity. Every action node usable with local data in app actions and available in flows, giving you one consistent logic model whether you’re running in the browser or on the server.
Polished external API integrations. Import a REST spec, pick the endpoints you need, and map responses directly into your data, without dropping down to a service.
More control at runtime. Additional execution controls (like concurrency settings) and broader streaming support across Run Action.
Questions or feedback on Flows? We’d love to hear how you’re using them.