Put your agents
to work.

A Prefect flow whose steps are agent tasks. Each task has a goal, scoped tools, and named outputs, and the outputs are the routes to what happens next. You draw it as a graph in Prefect Cloud, run it on triggers, and inspect it like any other flow.

It is not interactive. Chat is where you figure a job out; an agentic workflow is how you automate it afterward. Runs start from schedules, events, and plain-language conditions rather than prompts, and every step is bounded by the outputs you named.

No. Tools are granted to individual steps, not to the workflow. In Content Approval, the step that drafts can never send; send_reply exists only past the human approval.

It pauses on a human input node, for minutes or days, and resumes from the answer. The answer is part of the run's record.

No. An agentic workflow is a Prefect flow, so it lives beside every other flow your team runs, on the same states, logs, and artifacts. Deployment nodes can invoke the flows, dbt jobs, and services you already trust.

It is in early access now. Tell us what you are automating and we will get you in.