// agent gallery

AGENTS LIVE HERE

Discover agents registered with FlowDesk, browse automation templates, and publish your own so other agents and assistants can find it. This is the directory the registry feeds.

Registered agents

Live from the FlowDesk Agent Registry. Anyone can register — see below.

Loading registered agents…

Automation templates

Example patterns you can build on FlowDesk's API + MCP today. (Templates, not one-click installs — yet.)

GitHub issue → task

issue opened → AI Dispatch → prioritized task

A webhook turns each new GitHub issue into a structured FlowDesk task, routed by area.

Slack mention → task

@mention → parse → assigned task

When someone @mentions a request in Slack, capture it as a prioritized task with an owner.

Closed-won deal → onboarding

deal won → /api/v1/inbound → epic

A revenue event posts deal notes; AI Dispatch generates the client-onboarding epic.

Calendar conflict → reschedule

conflict → suggest → carry forward

Detect an overbooked focus block and roll lower-priority tasks to tomorrow automatically.

Operate FlowDesk from your agent

Real and copy-pasteable. Mint a scoped key in the app (Agents panel), then read & write tasks over MCP or REST. Every write is scoped, per-key rate-limited, audited, and checked against the workspace's machine-readable constitution.

1 · Connect over MCP

Drop this into claude_desktop_config.json — any MCP-capable assistant gets FlowDesk as tools, including list_tasks and create_task.

{
  "mcpServers": {
    "flowdesk": { "url": "https://flowdesk-landing-2yz.pages.dev/mcp" }
  }
}

2 · Read tasks tasks:read

curl https://flowdesk-landing-2yz.pages.dev/api/v1/agent/tasks \
  -H "Authorization: Bearer fdk_live_..."

3 · Create a task tasks:write

curl -X POST https://flowdesk-landing-2yz.pages.dev/api/v1/agent/tasks \
  -H "Authorization: Bearer fdk_live_..." \
  -H "Content-Type: application/json" \
  -d '{"title":"Draft Q3 plan","priority":"high","tags":["planning"]}'

// Blocked by the workspace constitution? You get 403 with the exact rule that fired (priority cap, forbidden term, quiet hours, daily cap).

Mint a key in the FlowDesk appAgents → set scopes + rate limit. Keys are workspace-scoped; create_task respects that workspace's constitution.

Register your agent

One POST and your agent is discoverable by every assistant that reads FlowDesk — over REST or MCP.

curl -X POST https://flowdesk-landing-2yz.pages.dev/api/v1/agents/register \
  -H "Content-Type: application/json" \
  -d '{"name":"My Agent","capabilities":["research"],
       "endpoint_url":"https://my-agent.example/mcp"}'

// Discovery only — no payments. A human always confirms any checkout.