> 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/sections.md).

# Conductor Sections

Creates or deletes a Conductor cloud section, the sidebar groups that organise workspaces. 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 Manage Section

### What it is

Create or delete a Conductor cloud section. Sections group workspaces in the sidebar; move workspaces with Manage Workspace.

### How it works

`create` posts `{name, emoji}` to `POST /v0/sections` and returns the new section; `delete` calls `DELETE /v0/sections/{id}` and returns the section together with the workspace ids that were in it (`removed_workspace_ids`), which are left unfiled rather than deleted. Move workspaces between sections with Manage Workspace's `move_to_section` action.

### Inputs

| Input       | Description                                            | Type                 | Required |
| ----------- | ------------------------------------------------------ | -------------------- | -------- |
| action      | create a personal section, or delete one               | "create" \| "delete" | No       |
| name        | Section name (create)                                  | str                  | No       |
| emoji       | Optional emoji shown next to the section name (create) | str                  | No       |
| section\_id | Section ID (delete)                                    | str                  | No       |

### Outputs

| Output                  | Description                                       | Type            |
| ----------------------- | ------------------------------------------------- | --------------- |
| error                   | Error message if the operation failed             | str             |
| section\_id             | ID of the created or deleted section              | str             |
| section                 | The section: id, name, emoji, workspaceIds        | Dict\[str, Any] |
| removed\_workspace\_ids | Workspaces that were in the section (delete only) | List\[str]      |

### Possible use case

**Per-customer folders**: Create a section per client and move their workspaces into it.

**Retire a project**: Delete its section and archive the returned workspace ids.

***


---

# 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/sections.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.