Skip to main content
ServFlow is an agent builder: you define AI agents and the workflows they run, and a Go engine serves them. The agent is the top-level object. Everything else — workflows, a workspace, the integrations it may use — belongs to one. This page explains the model. To build one, see Deploy your first API with the dashboard.

​
What an agent owns

An agent has a name and an optional description. Everything else it does comes from the workflows attached to it.

​
Webhooks and tasks

Workflows attach to an agent in one of two roles, decided by the workflow’s entry:
  • Webhook — a workflow with an HTTP entry. It is reachable from outside at its listen path, and is how the world sends work to the agent.
  • Task — a workflow with a trigger entry. It is not exposed over HTTP. It runs on a schedule, or because another workflow called it.
A single agent typically has one webhook that receives requests and several tasks doing the internal work.
A task with no cron schedule is simply never scheduled. That makes task the right role for internal helper workflows that exist only to be called by another workflow — they stay owned by the agent rather than floating unattached.

​
Agent resource vs. the agent action

These are different things, and the names collide: You can use the agent action in a workflow without creating an agent resource — that’s just an endpoint that happens to call a model. You create an agent resource when you want a named thing that bundles several workflows, holds a workspace, and is managed as a unit. See AI Agents for the action.

​
How a workflow’s entry decides its role

When you create a workflow, the entry type you choose determines both how it is reached and how it attaches:

​
Identity and references

Every workflow has a stable, human-readable id — a slug like order-sync. This is the identity everything else uses: attaching a workflow to an agent records this id, and one workflow calling another names it this way. A workflow also has a numeric store id, assigned when it is created. That one is only used for direct CRUD (get, update, delete); nothing references a workflow by it.

​
Managing agents from the CLI

Everything the dashboard does is available from servflow-pro resource:
--config-type accepts webhook or task — attach HTTP-entry workflows as webhooks and everything else as tasks. Use remove-config to detach.

​
Next steps

Deploy with the dashboard

Create your first agent and give it a workflow.

AI Agents

The agent action — calling an AI model inside a workflow.

Actions

The building blocks a workflow is made of.

Running ServFlow

What an instance serves, and how to deploy it.