Integrations

Create tasks from where your team already works, and dispatch them to whatever agent runs them. Slack, Discord, and any endpoint that accepts an HTTP POST.

Slack

Run /buildd in any channel to create a planning-mode task without leaving Slack. You get an immediate confirmation, and buildd notifies the channel when the plan is ready.

1

Create a Slack app

Add a slash command pointing at your buildd instance.

2

Connect it

Store your Team ID, Channel ID, and Bot Token on the workspace.

3

Run /buildd

Type your goal and buildd creates a planning-mode task.

Slack
/builddresearch AI agent frameworks and write a comparison report
Task created: "research AI agent frameworks and write a comparison report"
— I'll notify you when the plan is ready.
Full setup guide →

Discord

Run /buildd as a slash command in your server. The reply is a rich embed carrying the task title, status, mode, and a link straight to the task.

1

Create a Discord app

Register a bot with slash commands and set the interactions URL.

2

Connect it

Store your Guild ID, Channel ID, and Bot Token on the workspace.

3

Run /buildd

Get a rich embed back with the task title, status, and mode.

Discord

buildd

Task Created: implement dark mode for the dashboard

A planning-mode task has been created and is ready for a worker to pick up.

PendingMode: Planning
Full setup guide →

Webhook dispatch

Point a workspace at any HTTP endpoint and buildd posts each new task to it. Delivery is best-effort, so your agent can also claim tasks through the API. Use it to drive an agent buildd has no first-party integration for: OpenClaw, an n8n workflow, or your own.

1

Enable webhooks on your agent

Expose an endpoint that accepts an authenticated HTTP POST.

2

Register the endpoint

Point your workspace at that URL with a bearer token.

3

Create tasks

From the dashboard, the API, or MCP. buildd posts each new task to your endpoint.

4

Report back

Your agent PATCHes progress and opens PRs through the buildd API.

Register the endpoint

POST /api/workspaces/{workspaceId}/webhook
{ "url": "https://your-agent.example.com/hooks/agent", "token": "your-secret-token", "enabled": true, "runnerPreference": "any" }

runnerPreference is optional and filters which tasks get dispatched. There is a companion /webhook/test endpoint for checking connectivity before you enable it.

What your endpoint receives

POST https://your-agent.example.com/hooks/agent
Authorization: Bearer your-secret-token Content-Type: application/json { "message": "Work on buildd task: <title>\n\n<description>\n\n---\nTask ID: <id>\nReport progress: POST https://buildd.dev/api/workers/{workerId}", "sessionKey": "buildd-<taskId>", "name": "buildd" }

Data flow

Data flow
Dashboard / API / MCP │ ▼ POST /api/tasks ──► Pusher (runner workers) │ ├──► POST your webhook URL │ │ │ ▼ │ Your agent starts a session │ │ │ ▼ └──── PATCH /api/workers/:id (progress) POST /api/github/pr (PR creation)

Any agent, not just OpenClaw

Webhook dispatch works with any agent that accepts an HTTP POST. The payload is plain JSON, so integrating your own agents, n8n workflows, or any automation platform is a matter of accepting one request. See the docs →