> For the complete documentation index, see [llms.txt](https://docs.digibee.com/documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.digibee.com/documentation/development-cycle/build-overview/build-with-a-digital-worker.md).

# Build with a digital worker

Learn how you build an integration with a digital worker in Digital Worker Mode on Digibee, from your first goal to pipelines ready to deploy.

{% hint style="info" %}
Digital Worker Mode is available on request. If it's disabled in the mode selector, read [How to get access](https://docs.digibee.com/documentation/release-notes/digibee-digital-workers/now-available-digital-worker-mode.md#how-to-get-access) to request it for your organization.
{% endhint %}

## How do I build an integration with a digital worker?

You start with a conversation, not with an empty Canvas. You tell the digital worker what the integration needs to do for the business, and together you work out how it should behave. What you agree on goes into the spec. When the spec is ready, the digital worker creates the pipelines, and you test and deploy them.

Building happens in three stages:

1. **Guide:** Share the goal and your context, so the digital worker understands the problem. To learn how, read [Onboard the digital worker to your project](https://docs.digibee.com/documentation/development-cycle/build-overview/build-with-a-digital-worker/onboard-the-digital-worker-to-your-project.md).
2. **Collaborate:** Decide the design with the digital worker until the spec is ready. To learn how, read [Design and decide the solution together](https://docs.digibee.com/documentation/development-cycle/build-overview/build-with-a-digital-worker/design-and-decide-the-solution-together.md).
3. **Delegate and verify:** The digital worker creates the pipelines, and you test them against the spec before you deploy. To learn how, read [Delegate the build and verify it before deploy](https://docs.digibee.com/documentation/development-cycle/build-overview/build-with-a-digital-worker/delegate-the-build-and-verify-it-before-deploy.md).

After you deploy, a digital worker also helps you monitor the integration in production. To see the full process, from your goal to production, read [How do I delegate my integration to a digital worker?](https://docs.digibee.com/documentation/development-cycle/digital-worker-mode/how-do-i-delegate-my-integration-to-a-digital-worker.md).

### Next steps

Now that you know how building with a digital worker works, read [Onboard the digital worker to your project](https://docs.digibee.com/documentation/development-cycle/build-overview/build-with-a-digital-worker/onboard-the-digital-worker-to-your-project.md) to create your first project.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.digibee.com/documentation/development-cycle/build-overview/build-with-a-digital-worker.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
