---
ref: tool:make/list-scenarios
name: List scenarios
company: company:make
workflows: []
access: [cli, api]
tags: [capability:automate-workflows, category:automation, has:api, has:cli]
docs: https://developers.make.com/api-documentation/api-reference/scenarios
updated: 2026-09-27
---

# List scenarios

Returns the scenarios in a Make team or organization, filterable by name, folder and whether they are active.

Note: Needs a `teamId` or `organizationId` (`--team-id` on the CLI). Read a scenario's expected inputs with `GET /scenarios/{scenarioId}/interface` before running it.

## Set up

Use the first option your agent supports.

### CLI (official)

Install the command, then confirm it runs.

```sh
npm install -g @makehq/cli
make-cli --version
```

Run `make-cli scenarios list`.

Set `$MAKE_API_KEY` in your environment first.

### API (official)

- Base URL: https://{zone_url}/api/v2
- Endpoint: `GET /scenarios`
- Auth: send the header `Authorization: Token $MAKE_API_KEY`
- Docs: https://developers.make.com/api-documentation

Note: `{zone_url}` is your organization's zone from the Make dashboard's address bar, such as `eu1.make.com`.

Before anything else, confirm access with the cheapest read-only call, like a list or a search. Never send or change anything to test access.

## Rules

- Ask the user before anything that sends messages, costs money, or changes data, and say how many records it touches. One approval covers a batch the user has seen.
- Never print API keys.