AIToday
Large Language ModelsHugging Face BlogPublished: Aug 25, 2026, 13:01 JST2 min read

Gradio Adds Drag-and-Drop AI Workflow Builder

Gradio Adds Drag-and-Drop AI Workflow Builder

Key takeaway

  • Gradio now includes gr.Workflow, a visual builder for AI pipelines.

  • Users can connect typed nodes and run each step separately.

  • Every workflow also becomes a REST API and deploys to Hugging Face Spaces with one command.

3 Key Points

  1. What happened

    Hugging Face has introduced gr.Workflow, built into Gradio, which lets users describe AI pipelines as graphs of typed nodes. The workflow serves as a drag-and-drop canvas where every node is runnable and each intermediate result is visible.

  2. Why it matters

    This makes complex AI pipelines — like generating an image, removing its background, or creating a voiceover — accessible as a visual interface rather than requiring Python scripting and print-debugging. Each workflow also becomes a REST API and can be deployed to Hugging Face Spaces with one command.

  3. What to watch

    Every workflow output becomes a REST endpoint named after its label, callable from Python or curl. Users can also run their own GPU models inside a Space by decorating a function with @spaces.GPU, and Hugging Face says even something as involved as AUTOMATIC1111 can be built this way.

Ask the AI about this article →

Context & Analysis

The announcement positions gr.Workflow as a way to make AI pipelines themselves the interface, rather than hiding them behind code. The examples on the blog show a spectrum: from a simple single-node image editor to a multi-branch media studio that chains several models and Spaces. This variety suggests the design goal is to cover both lightweight demos and more production-like arrangements where each output also becomes a callable endpoint.

The fan-out pattern is highlighted repeatedly, where one input feeds multiple operators running in parallel — as in the Generative Art Lab and the dataset profiler. The ZeroGPU example adds another layer, allowing an fn node to run a model inside the Space on demand, with a GPU grabbed and released for each call. This means users are not limited to external Inference Providers or pre-built Spaces.

For a business reader, the practical significance lies in the low barrier to entry: clicking Duplicate on any demo to rewire it, or starting from a few lines of Python. Each workflow ships with REST endpoints automatically, which could let teams integrate AI steps into existing applications without building custom glue code. The promise that something as complex as AUTOMATIC1111 can be built this way hints at the intended scale, with a follow-up post planned to walk through that build step by step.

FAQ

What can I build with gr.Workflow?
You can build any AI pipeline, such as editing images with text prompts, generating images with FLUX and removing backgrounds, creating voiceovers, and analyzing Hugging Face datasets. Even something as involved as AUTOMATIC1111 can be built this way.
Can I call a workflow from code?
Yes. Every output becomes a REST endpoint named after its label, and you can call it from Python using the Gradio client or directly via curl. Endpoints that call a model or a Space run under a Hugging Face token.
How do I get started building my own workflow?
Open any demo on the blog, click Duplicate, and start rewiring. From Python, the code can be as short as gr.Workflow(bind=[your_function]).launch(). The full walkthrough is in the official gr.Workflow guide in the Gradio docs.
Hugging Face BlogRead Original Article

Get the latest Large Language Models news every morning

AI-summarized, only the topics you pick — one digest a day via Email, Slack, or Discord.

Free · takes 30 seconds · unsubscribe anytime

Ask AI

Ask AI anything about this article. Q&As are published on this page for other readers too.

Related Articles

Next articleNvidia eyes Perplexity investment at $30B valuation