> For the complete documentation index, see [llms.txt](https://agpt.co/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://agpt.co/docs/integrations/block-integrations/account.md).

# Conductor Account

One-call overview of a Conductor account: identity, projects (repositories), sections and routines. Requires your own Conductor API key, created at [app.conductor.build/users/api-keys](https://app.conductor.build/users/api-keys) and added through AutoGPT’s credentials UI. Select that credential for each Conductor block; no server-wide default key is used.

## Conductor Get Account

### What it is

Get an overview of your Conductor account in one call: who you are, the projects (repositories) you can open workspaces in, your sections and your routines. Use this first to find project IDs.

### How it works

The block calls `GET /me` for the caller's identity, then pages through `GET /v0/projects`, `GET /v0/sections` and `GET /v0/routines` (each `{data, offset, hasMore}` listing) until `limit` items or the end. Routine listings never include webhook URLs; use Manage Routine to create a routine or rotate its secret and receive the URL. Any HTTP or API error (`userMessage` from Conductor) is raised as a block error.

### Inputs

| Input | Description                                               | Type | Required |
| ----- | --------------------------------------------------------- | ---- | -------- |
| limit | Maximum number of projects, sections and routines to list | int  | No       |

### Outputs

| Output   | Description                                                                                                         | Type                   |
| -------- | ------------------------------------------------------------------------------------------------------------------- | ---------------------- |
| error    | Error message if the operation failed                                                                               | str                    |
| user     | The authenticated identity: userId, name, email, organizationId                                                     | Dict\[str, Any]        |
| projects | Repositories you can create workspaces in: id, name, gitRemote                                                      | List\[Dict\[str, Any]] |
| sections | Your cloud sections: id, name, emoji, workspaceIds                                                                  | List\[Dict\[str, Any]] |
| routines | Your routines: id, name, prompt, repoUrl, agent, model, enabled, runCount, triggers (webhook URLs are not included) | List\[Dict\[str, Any]] |

### Possible use case

**Orient an agent**: Run this first so AutoPilot or a graph can look up the `projects[].id` it needs before creating a workspace.

**Inventory**: List sections and routines to decide where new workspaces should be filed and which automations already exist.

***


---

# 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://agpt.co/docs/integrations/block-integrations/account.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.