> ## Documentation Index > Fetch the complete documentation index at: https://docs.duvo.ai/llms.txt > Use this file to discover all available pages before exploring further. # List Automations > List the team's automations, each with its live agent and queue counts. An automation is the workspace container an agent or queue belongs to on a team that has moved to Automations — its id is what `POST /queues` and `POST /agents` need as `automation_id`. ## OpenAPI ````yaml https://api.duvo.ai/v2/documentation/mintlify.json get /v2/teams/{teamId}/automations openapi: 3.0.3 info: title: Duvo Public API description: >- Public API for programmatic access to Duvo. Authenticate with API keys created in the Duvo dashboard. ## Rate limits Requests are counted per API key. Every response advertises the quota with the IETF RateLimit fields, so a client can self-throttle without waiting for a rejection: - `RateLimit-Policy: "default";q=;w=` — the policy in force: `q` requests per `w` seconds. - `RateLimit: "default";r=;t=` — the live state: `r` requests left, quota resetting in `t` seconds. - Read the quota from the headers rather than hard-coding it; it differs per environment. - The same numbers are also sent as `ratelimit-limit`, `ratelimit-remaining` and `ratelimit-reset`. Once the quota is exhausted the API answers `429 Too Many Requests` with `Retry-After` set to the seconds to wait; honor it instead of retrying immediately. version: 1.0.0 servers: - url: https://api.duvo.ai description: Production server security: [] tags: - name: Runs description: Start, monitor, and manage agent runs (Runs in the Duvo UI) - name: Sandboxes description: Create sandboxes and upload files for agent runs - name: Queues description: Manage queues and their agent bindings - name: Cases description: Create, list, and manage cases and their labels within queues - name: Case Approvals description: Submit decisions on pending case approval requests issued by an agent run - name: Case Attachments description: Upload, list, download, and remove the files attached to a case - name: Automations description: >- List and manage automations — the workspace container that groups the agents and queues making up one end-to-end process - name: Agents description: Create and manage agents for automation workloads - name: Revisions description: Create and manage agent revisions — the underlying Setup for an Agent - name: Agent Folders description: Organize agents into folders - name: Agent Memory description: Read an agent's memory files (the Memory feature in the Duvo UI) - name: Suggestions description: >- List, apply, and dismiss an Agent's improvement suggestions (the suggestions inbox in the Duvo UI) - name: Notifications description: >- List, read, dismiss, and clear the authenticated user's team notifications (the Notification Center in the Duvo UI) - name: Schedules description: List schedules configured for an agent - name: Duvo Pulse description: >- Create, list, iterate on, and delete Duvo Pulse dashboards — live, agent-generated visualizations of your Duvo data - name: Case Triggers description: >- Configure case triggers that automatically dispatch agent runs (Runs in the Duvo UI) for cases added to a queue - name: Triggers description: >- Configure event triggers that start a Run automatically when an external event fires (e.g. an email arrives, a Linear issue is created, or a file changes in Google Drive) - name: Skills description: Manage team and system skills (reusable knowledge packs). - name: Files description: Manage team files. - name: Plugins description: Discover plugins that can be referenced from a revision. - name: Organizations description: Inspect organizations you belong to and the teams within them - name: Team description: Inspect the team and members associated with the API key - name: Invites description: >- Invite people to a team — one at a time or in bulk, scoped to a Clarity process or the whole team — and manage the team's shareable invite link - name: Integrations description: Browse the team's catalog of available integration types - name: Connections description: Manage your connected integrations - name: Credentials description: >- Manage logins (domain + username + password + TOTP) used by agents to sign in to websites and desktop applications, and attach them to assignment revisions - name: Secrets description: >- Manage env-var secrets injected into runs, and attach them to assignment revisions. Only metadata is exposed; values are never returned - name: Revision Integrations description: >- Attach integrations to assignment revisions, pin specific connections, and link queues - name: ClarityV2 description: >- Manage Clarity v2 process snapshots, automation proposals, and the extra-capture-request follow-up loop paths: /v2/teams/{teamId}/automations: get: tags: - Automations summary: List Automations description: >- List the team's automations, each with its live agent and queue counts. An automation is the workspace container an agent or queue belongs to on a team that has moved to Automations — its id is what `POST /queues` and `POST /agents` need as `automation_id`. operationId: listAutomations parameters: - schema: default: 250 type: integer minimum: 1 maximum: 250 in: query name: limit required: false description: Number of automations per page (1-250, default 250) - schema: type: integer minimum: 0 maximum: 9007199254740991 in: query name: offset required: false description: Number of automations to skip - name: teamId in: path required: true schema: type: string responses: '200': description: Default Response content: application/json: schema: type: object properties: automations: type: array items: type: object properties: id: type: string format: uuid name: type: string agent_count: type: integer minimum: -9007199254740991 maximum: 9007199254740991 queue_count: type: integer minimum: -9007199254740991 maximum: 9007199254740991 created_at: type: string updated_at: type: string folder_id: default: null description: >- The agent folder this automation sits in, or null when it sits at the root. Automations reuse the team's existing agent_folder tree rather than a parallel one, so a converted team keeps the grouping it already had. Defaulted rather than required for the same reason is_setting_up is: the client parses this response, and a backend that predates the column must not throw and take the automation's name down with it. nullable: true type: string pinned_at: default: null description: >- When the calling user pinned this automation to the top of their Automations list, or null when they have not. A pin is per user, like an Agent pin: teammates each keep their own. Defaulted rather than required for the same reason folder_id is. nullable: true type: string is_setting_up: default: false description: >- True while this Module automation's setup is under way. setup_started_at is stamped when the team starts setting up (and again by reopen-setup) and cleared when setup finishes, so this reads as currently in setup, not as a record of a past one. Read together with is_demo, which lives on the detail response: both true is a demo with a build under way; is_demo alone is a demo nobody has begun. On the summary rather than the detail so that a client holding only a list, create or patch response knows the state too, and so every write onto the shared automation collection carries it. Defaulted rather than required: the client parses this response, so a backend that predates the column must not throw and take the automation's name down with it, and nothing on the wire has always meant an automation nobody has set up. type: boolean setup_step: default: null description: >- The key of the latest confirmed setup step, null until Start Setup is pressed. The server only ever advances it forward, so reopening a setup can resume where the team got to. Cleared with the rest of the setup state when setup finishes. nullable: true type: string setup_build_chat_id: default: null description: >- The Ask Duvo chat building the automation from the approved proposal, or null while setup has not reached the build. Not a hard reference: the chat can be deleted while this still names it, which the client reads as no build yet. nullable: true type: string format: uuid setup_progress: default: null description: >- The setup facts behind the tile's Setup badge — captures uploaded, the team's own process map generated, a proposal written — or null while the automation is not being set up (and whenever it has no module process for the facts to hang off). nullable: true type: object properties: has_captures: type: boolean has_process_map: type: boolean has_proposal: type: boolean required: - has_captures - has_process_map - has_proposal additionalProperties: false viewer_can_edit: description: >- Whether the caller may change this automation. An automation takes its agents' ownership rule: a Builder may edit one whose every agent they created, and Lead Builder or above may edit any. Sent by the list and detail endpoints; absent from create and update responses, where the client falls back to the caller's role. type: boolean required: - id - name - agent_count - queue_count - created_at - updated_at - folder_id - pinned_at - is_setting_up - setup_step - setup_build_chat_id - setup_progress additionalProperties: false total: type: integer minimum: -9007199254740991 maximum: 9007199254740991 limit: type: integer minimum: -9007199254740991 maximum: 9007199254740991 offset: type: integer minimum: -9007199254740991 maximum: 9007199254740991 required: - automations - total - limit - offset additionalProperties: false '401': description: Default Response content: application/json: schema: type: object properties: error: type: string required: - error additionalProperties: false '403': description: Default Response content: application/json: schema: type: object properties: error: type: string required: - error additionalProperties: false '500': description: Default Response content: application/json: schema: type: object properties: error: type: string required: - error additionalProperties: false security: - bearerAuth: [] components: securitySchemes: bearerAuth: type: http scheme: bearer description: API key authentication. Get your API key from the Duvo dashboard. ```` This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.