> For the complete documentation index, see [llms.txt](https://docs.distro.so/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.distro.so/developers/list-workflows.md).

# List API-triggered workflows

List published workflows that use the **API call** trigger before choosing a workflow to start.

```http
GET /api/v1/triggers?account_id=WORKSPACE_ID
Authorization: Bearer YOUR_DISTRO_API_TOKEN
```

Required scope: `visual_workflows:read` or `visual_workflows:start`.

## Response

```json
{
  "workflows": [
    {
      "id": 123,
      "name": "Route an API lead",
      "enabled": true,
      "version": 2,
      "inputs": {},
      "start_url": "/api/v1/triggers/123?account_id=456"
    }
  ]
}
```

The numbers and empty schema here are examples. Your workflow's `inputs` contains its published input schema. Match your request to that schema rather than assuming every workflow accepts the same lead fields.

A listed workflow can be Off. Check `enabled`, and confirm live enrollment/execution is available to the workspace.

## Configure the source

In the workflow editor, choose API call, define the input schema, simulate representative cases and publish. The listing exposes the published version, not uncommitted draft edits.

If the workflow is absent, check the workspace, publication, trigger type, token permissions and feature access. A form-triggered workflow is not automatically an API-call workflow.

Use the returned start path with the same application base URL. Continue with [Start a workflow](/developers/start-workflow.md).


---

# 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 dynamically by asking a question.

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

```
GET https://docs.distro.so/developers/list-workflows.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 `build a script that syncs our docs to a CMS` 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.