Integrations
Dooza Crew integrations: hand work to an AI agent from your software
Dooza Crew connects to other software in two ways today: the Crew Task API (REST, Bearer key, OpenAPI description) and the n8n community node. Both send a task in plain words to an agent in your Crew and give you back its answer. The agent does the work with its own computer and browser, and asks you before it sends or pays for anything.
What is available
Crew Task API
Live
REST over HTTPS with a Bearer key. Use it from your own code or any tool that can send an HTTP request with a header.
n8n community node
Live on npm (n8n verification under review)
n8n-nodes-dooza-crew: Run Task and Get Task inside a workflow, or attach it to the n8n AI Agent node as a tool.
Crew Task API
Base URL https://crew.dooza.ai. Every request carries Authorization: Bearer dz_…; a missing or wrong key returns 401. A task has an id, agent, status (running, completed or failed), result, and created and updated times.
| Method | Path | What it does |
|---|---|---|
| POST | /v1/tasks | Create a task. Body: text (required, up to 20,000 characters) and agent (optional, default master). Returns 202 with the task. |
| GET | /v1/tasks/{id} | Get one task. Poll until status is completed or failed, then read result. |
| GET | /v1/tasks | List recent tasks. Query limit from 1 to 100, default 20. |
Send a task
curl -X POST https://crew.dooza.ai/v1/tasks \
-H "Authorization: Bearer dz_YOUR_KEY" \
-H "Content-Type: application/json" \
-d '{"agent": "master", "text": "Summarize the 5 newest reviews of our business"}'Read the result
curl https://crew.dooza.ai/v1/tasks/task_0123456789abcdef01234567 \
-H "Authorization: Bearer dz_YOUR_KEY"Poll every few seconds until status is completed (read result) or failed (read error). Get your key in the Crew app: account menu → API key. Full schema: crew.dooza.ai/v1/openapi.json.
n8n
On self-hosted n8n, install n8n-nodes-dooza-crew (npm, MIT) from Settings › Community Nodes. It wraps the same API: Run Task waits for the answer by default, Get Task reads a task by id. On n8n Cloud, call the API with the HTTP Request node. Setup steps and an example workflow: Dooza Crew for n8n.
Questions
Yes. The Crew Task API lets your software send a task to one of your Crew agents and read the result. It has three endpoints: POST /v1/tasks, GET /v1/tasks/{id} and GET /v1/tasks. The OpenAPI description is at crew.dooza.ai/v1/openapi.json.
Sign in at crew.dooza.ai (start for $5), open the account menu at the top right and choose API key. The key starts with dz_ and is sent as an Authorization: Bearer header.
No. POST /v1/tasks returns 202 with a task id and status running. Poll GET /v1/tasks/{id} until status is completed (read result) or failed (read error). Agents do multi-step work with a browser and files, so a task can take a while.
Two ready-made surfaces exist today: the Task API and the n8n community node. Anything that can make an HTTP request with a header can call the API, including the HTTP Request node on n8n Cloud. We list a connector here only once it is live.
No. The agents run inside your Dooza Crew. The API and the n8n node only need your Crew API key.
No. Crew agents ask you to Approve, Edit or Reject before they send or pay for anything, whether the task came from the app, the API or n8n.
Rather have the connection built for you?
We build and run AI agents for small businesses, and we keep them working. Tell us the job on a free 30-minute call, or start with Crew yourself and get your API key in a few minutes.
Endpoints checked against the live OpenAPI description and a live API call on October 30, 2026. The OpenAPI file is the source of truth if they ever differ.