LogoLogo
Get support
  • Home
  • Make API
  • Make Bridge
  • White Label
  • MCP Server
  • Make API documentation
  • Getting started
    • Make API structure
    • HTTP methods
    • Making your first API request
    • Rate limiting
    • Resources
  • Authentication
    • Make roles and API scopes
    • Creating API token
    • Managing API token
    • Requesting an OAuth 2.0 client
    • OAuth 2.0 flow in the Make API
  • Pagination, sorting and filtering
    • Pagination and sorting
    • Filtering
  • Troubleshooting and error handling
    • HTTP status error codes
    • Troubleshooting
  • Client libraries
  • API Reference
    • Affiliate
    • Agents
    • Analytics
    • Audit logs
    • Cashier
    • Connections
    • Custom properties
    • Custom properties > Structure items
    • Data stores
    • Data stores > Data
    • Data structures
    • Devices
    • Devices > Incomings
    • Devices > Outgoing
    • Incomplete executions
    • Enums
    • Custom functions
    • General
    • Hooks
    • Hooks > Incomings
    • Hooks > Logs
    • Keys
    • Notifications
    • Organizations
    • Organizations > User organization roles
    • Remote procedures
    • Scenarios
    • Scenarios > Logs
    • Scenarios > Blueprints
    • Scenarios > Consumptions
    • Scenarios > Custom properties data
    • Scenarios folders
    • SDK Apps
    • SDK Apps > Invites
    • SDK Apps > Modules
    • SDK Apps > RPCs
    • SDK Apps > Functions
    • SDK Apps > Connections
    • SDK Apps > Webhooks
    • SSO certificates
    • Teams
    • Teams > User team roles
    • Templates
    • Templates > Public
    • Users
    • Users > Me
    • Users > API Tokens
    • Users > User team roles
    • Users > User team notifications
    • Users > User organization roles
    • Users > Roles
    • Users > Unread notifications
    • Users > User email preferences Mailhub
Powered by GitBook
On this page
Export as PDF
  1. API Reference

Scenarios folders

PreviousScenarios > Custom properties dataNextSDK Apps

Resources

  • Academy
  • Community
  • Help Center

Useful links

  • Support
  • Privacy Notice
  • Status Page
  • make.com

Follow us

  • LinkedIn
  • X (Twitter)
  • Facebook
  • Instagram

© 2025 make.com

Scenarios can be grouped into folders for better organization. The following endpoints allow you to create and manage scenarios folders.

Delete scenario folder

delete

Deletes a scenario folder with a given ID and returns the ID in the response.

Authorizations
Path parameters
folderIdintegerRequired

The unique ID of the scenario folder. It can be retrieved from the List scenarios folders endpoint.

Example: 1
Responses
200
Successful response
application/json
delete
DELETE /api/v2/scenarios-folders/{folderId} HTTP/1.1
Host: eu1.make.com
Authorization: YOUR_API_KEY
Accept: */*
200

Successful response

{
  "scenarioFolder": 123
}
  • GETList scenario folders
  • POSTCreate scenario folder
  • DELETEDelete scenario folder
  • PATCHUpdate scenario folder

List scenario folders

get

Retrieves a collection of all scenarios folders for a team with a given ID. Returned folders are sorted by name in ascending order.

Authorizations
Query parameters
teamIdintegerRequired

Unique ID of the Team.

Example: 1
Responses
200
Successful response
application/json
get
GET /api/v2/scenarios-folders HTTP/1.1
Host: eu1.make.com
Authorization: YOUR_API_KEY
Accept: */*
200

Successful response

{
  "scenariosFolders": [
    {
      "id": 1576,
      "name": "ALPHA",
      "scenariosTotal": 10
    }
  ]
}

Create scenario folder

post

Creates a new scenario folder with data passed in the request body. As the response, it returns all details of the created scenario folder.

Authorizations
Body
namestringRequired

The name of the scenario folder. The name must be at most 100 characters long and does not need to be unique.

teamIdintegerRequired

The unique ID of the team in which the scenario folder will be created.

Responses
200
Created a Folder
application/json
post
POST /api/v2/scenarios-folders HTTP/1.1
Host: eu1.make.com
Authorization: YOUR_API_KEY
Content-Type: application/json
Accept: */*
Content-Length: 28

{
  "name": "ZULU",
  "teamId": 123
}
200

Created a Folder

{
  "scenarioFolder": {
    "id": 1576,
    "name": "ALPHA",
    "scenariosTotal": 10
  }
}

Update scenario folder

patch

Updates a scenario folder with a given ID by passing new values in the request body. Any property that is not provided will be left unchanged. In the response, it returns all details of the updated folder including properties that were not changed.

Authorizations
Path parameters
folderIdintegerRequired

The unique ID of the scenario folder. It can be retrieved from the List scenarios folders endpoint.

Example: 1
Query parameters
Body
namestringOptional

The name for the updated scenario folder. The name must be at most 100 characters long and does not need to be unique.

Responses
200
Folder updated
application/json
patch
PATCH /api/v2/scenarios-folders/{folderId} HTTP/1.1
Host: eu1.make.com
Authorization: YOUR_API_KEY
Content-Type: application/json
Accept: */*
Content-Length: 16

{
  "name": "BRAVO"
}
200

Folder updated

{
  "scenarioFolder": {
    "id": 1576,
    "name": "ALPHA",
    "scenariosTotal": 10
  }
}