DoozaDooza

Integrations · n8n

Dooza Crew for n8n: give any workflow an AI employee

The Dooza Crew community node hands a task to an agent in your Crew from any n8n workflow and returns the agent’s answer to the next node. Package: n8n-nodes-dooza-crew on npm, MIT licensed, published 28 October 2026, latest 0.1.1 on 29 October 2026.

Try Dooza Crew freeInstall from npm

What the node does

How to set it up

  1. 1. Install the community node package

    On self-hosted n8n open Settings > Community Nodes, install n8n-nodes-dooza-crew, and reload the editor. The node appears as Dooza Crew.

  2. 2. Create the Crew API key

    Sign in at crew.dooza.ai, open the account menu and choose API key. Copy the key that starts with dz_. Dooza Crew is free to try and needs no card.

  3. 3. Add the credential in n8n

    New credential > Dooza Crew API, paste the key, leave Base URL as https://crew.dooza.ai. The key is sent as an Authorization: Bearer header on every request.

  4. 4. Add the Dooza Crew node to a workflow

    Put it after any trigger, choose Run Task, set the agent (master for your main agent) and write the task in plain words. Use expressions to pass data in, for example: Draft a reply to this lead: {{ $json.message }}.

  5. 5. Use the answer in the next node

    The output carries the task id, status and the agent answer. Send it by Gmail, write it to a sheet, post it to Slack, or feed it to another AI step.

The key path in the Crew app is account menu (top right) → API key (crew.dooza.ai/bridge/api-key), and it starts with dz_. API description: OpenAPI JSON.

Example workflow

Schedule Trigger (every morning) → Dooza Crew: Run Task (agent master, task “Find 5 new reviews of our business and summarize them”) → Gmail: send the answer to yourself. Any trigger works the same way: a form, a webhook, a new row in a sheet, a support email.

How it fits with n8n’s own AI nodes

n8n’s AI Agent node runs a model you configure, inside the workflow. The Dooza Crew node calls a team of agents that browse the web, keep files and do a multi-step job, then returns the result to the workflow. Use n8n for the plumbing (triggers, apps, delivery) and Crew for the work that needs judgement and tools. Nothing leaves your Crew without your approval: agents ask you to Approve, Edit or Reject before they send or pay for anything.

Links

Questions

It lets an n8n workflow hand a task to an agent in your Dooza Crew and use the answer in the next node. Two operations: Run Task (send a task to an agent and, by default, wait for the result) and Get Task (fetch the status and result of a task by id). The node can also be attached to the n8n AI Agent node as a tool.

On a self-hosted n8n, install the community node package n8n-nodes-dooza-crew from Settings > Community Nodes using the n8n installation guide (https://docs.n8n.io/integrations/community-nodes/installation/). The node appears in the node panel as Dooza Crew.

Sign in at crew.dooza.ai (free to try, no card needed), open the account menu at the top right and choose API key (crew.dooza.ai/bridge/api-key). The key starts with dz_. In n8n, create a Dooza Crew API credential, paste the key and leave Base URL as https://crew.dooza.ai.

Run Task polls the task by default (Poll Interval 5 seconds) and stops after the Timeout you set (600 seconds by default). On timeout the node returns the latest status with timedOut: true, so your workflow can branch or alert instead of hanging.

No. The agents run inside your Dooza Crew; the node only needs your Crew API key. You do not configure model providers in n8n.

The node is open source (MIT) and free to install. Using it consumes your Crew account: Dooza Crew is free to try with no card needed, and agents ask you to Approve, Edit or Reject before they send or pay for anything.

Community nodes are installed on self-hosted n8n. On n8n Cloud, use the HTTP Request node against the Crew API instead; the OpenAPI description is at crew.dooza.ai/v1/openapi.json.

Want a workflow built, not just connected?

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 in the next five minutes.

Package and node behaviour checked on npm and in the node source on October 29, 2026. If a later version changes an option, the README on npm is the source of truth.