Command line interface (CLI)
The monday CLI enables you to interact with the apps framework using a set of predefined commands to execute various operations. This document explains how to install the CLI and walks through the supported commands, but you can also access the CLI here.
Installation
To start using the CLI, you must first install it using the following command:
$ npm install -g @mondaycom/apps-cli
After installing the CLI, use the mapps init command to add your API token: 
$ mapps init -t <SECRET_TOKEN>
Commands
- mapps api:generate
- mapps app:create
- mapps app:deploy
- mapps app:list
- mapps app:promote
- mapps app-features:build
- mapps app-features:create
- mapps app-features:list
- mapps app-version:builds
- mapps app-version:list
- mapps autocomplete [SHELL] [-r]
- mapps code:env
- mapps code:logs
- mapps code:push
- mapps code:secret
- mapps code:status
- mapps help [COMMANDS]
- mapps init
- mapps scheduler:create
- mapps scheduler:delete
- mapps scheduler:list
- mapps scheduler:run
- mapps scheduler:update
- mapps storage:export
- mapps storage:remove-data
- mapps storage:search
- mapps tunnel:create
Global flags
The following global flags are optional and can be used on any command.
| Global flag | Description | 
|---|---|
| --print-command | Prints the command that was executed. | 
| --verbose | Prints advanced logs. | 
mapps api:generate
mapps api:generateThe mapps api:generate command prepares your environment for custom query development by creating all necessary files and scripts. Make sure to run it from your root directory! 
Example
$ mapps api:generate
mapps app:create
mapps app:createThe mapps app:create command creates an app. 
Flags
| Long flag | Short flag | Description | 
|---|---|---|
| --targetDir | -d | The directory to create the app in. | 
| --name | -n | The new app's name. | 
Example
$ mapps app:create -n NEW_APP_NAME
mapps app:deploy
mapps app:deployThe mapps app:deploy command deploys an app using manifest file. 
Flags
| Long flag | Short flag | Description | 
|---|---|---|
| --appId | -a | The app's unique identifier. | 
| --directoryPath | -d | The project's directory path. If excluded, the working directory will be used. | 
| --force | -f | Force push to the latest version (draft or live). | 
| --appVersionId | -v | The version's unique identifier. | 
| --region | -z | The region to use: us,au, oreu. | 
Example
$ mapps app:deploy 
mapps app:list
mapps app:listThe mapps app:list command lists all apps for a specific user. 
Example
$ mapps app:list
mapps app:promote
mapps app:promoteThe mapps app:promote command promotes an app's draft version to live. 
Flags
| Long flag | Short flag | Description | 
|---|---|---|
| --appId | -a | The app's unique identifier. | 
| --appVersionId | -i | The app version's unique identifier | 
Example
$ mapps app:promote -i <APP_VERSION_ID> -a <APP_ID>
mapps app-features:build
mapps app-features:buildThe mapps app-features:build command creates a new app feature build. Please note that it currently only supports custom URL or monday code build types. 
Flags
| Long flag | Short flag | Description | 
|---|---|---|
| --appId | -a | The app's unique identifier. | 
| --appFeatureId | -d | The app feature's unique identifier. | 
| --appVersionId | -i | The app version's unique identifier. | 
| --buildType | -t | The build type: custom_urlormonday_code. | 
| --customUrl | -u | The custom URL for your app's build (if applicable). | 
Example
$ mapps app-features:build 
// or
$ mapps app-features:build -a 123456789 -i 987654321 -d 17654321 -t custom_url -u https://www.test.com
// or 
$ mapps app-features:build -a 123456789 -i 987654321 -d 17654321 -t monday_code -u /triggers
mapps app-features:create
mapps app-features:createThe mapps app-features:create command creates a new app feature. 
Flags
| Long flag | Short flag | Description | Accepted values | 
|---|---|---|---|
| --appId | -a | The app's unique identifier. | |
| --appVersionId | -i | The app version's unique identifier. | |
| --featureName | -n | The feature's name. | |
| --featureType | -t | The feature's type. | 
mapps app-features:list
mapps app-features:listThe mapps app-features:list command lists all features for a specific app version. 
Flags
| Long flag | Short flag | Description | 
|---|---|---|
| -appId | -a | The app's unique identifier. | 
| --appVersionId | -i | The app version's unique identifier. | 
Example
$ mapps app-features:list 
// or 
$ mapps app-features:list -a 123456789 -i 987654321
mapps app-version:builds
mapps app-version:buildsThe mapps app-version:builds command lists all builds for a specific app version. 
Flags
| Long flag | Short flag | Description | 
|---|---|---|
| --appVersionId | -i | The version's unique identifier. | 
$ mapps app-version:builds -t 987654321
mapps app-version:list
mapps app-version:listThe mapps app-version:list command lists all versions for a particular app. 
Flags
| Long flag | Short flag | Description | 
|---|---|---|
| --appId | -i | The app's unique identifier. | 
Example
$ mapps app-version:list -i 1234567890
mapps autocomplete [SHELL]
mapps autocomplete [SHELL]The mapps autocomplete [SHELL] command displays the autocomplete installation instructions. 
Arguments
| Argument | Description | 
|---|---|
| SHELL | The shell type: zsh,bash, orpowershell. | 
Flags
| Long flag | Short flag | Description | 
|---|---|---|
| --refresh-cache | -r | Refreshes the cache (ignores displaying instructions). | 
Example
$ mapps autocomplete bash
mapps code:env
mapps code:envThe mapps code:env command manages environment variables for your app hosted on monday code. 
Flags
| Long flag | Short flag | Description | 
|---|---|---|
| --appId | -i | The app's ID. | 
| --key | -k | The variable key (required for setanddelete). | 
| --mode | -m | The management mode: list-keys,set, ordelete. | 
| --value | -v | The variable value (required for set). | 
| --region | -z | The region to use: us,au, oreu. | 
Example
$ mapps code:env -m set -k <KEY> -v <VALUE>
mapps code:logs
mapps code:logsThe mapps code:logs command streams logs. 
Flags
| Long flag | Short flag | Description | 
|---|---|---|
| --logsEndDate | -e | The log's end date (e.g. MM/DD/YYYY HH:mm). Only supported for historyevents. | 
| --logsStartDate | -f | The log's start date (e.g. MM/DD/YYYY HH:mm). Only supported for historyevents. | 
| --appVersionId | -i | The app's version ID. | 
| --logSearchFromText | -r | The regex text to search the logs for. Only supported for liveevents. | 
| --eventSource | -s | The log's source: live(live events) orhistory(past events). | 
| --logsType | -t | The log's type: http(http events) orconsole(stdout). | 
| --region | -z | The region to use: us,au, oreu. | 
Example
$ mapps code:logs -i <APP_VERSION_ID> -t <LOGS_TYPE>
mapps code:push
mapps code:pushThe mapps code:push command pushes your project to be hosted on monday.com's infrastructure. 
Flags
| Long flag | Short flag | Description | Notes | 
|---|---|---|---|
| --appId | -a | The app's ID. | |
| --client-side | -c | Pushes client-side code to monday.com (4.6.0 and above). | Uploads code to our CDN for faster load times and reduced latency (recommended). The directory must include a root-level index.html. | 
| --directoryPath | -d | The project's directory path. If excluded, the working directory will be used. | When using a bundler, make sure the directory path is the build directory (e.g.,"./dist"). | 
| --force | -f | Force push to the latest version (draft or live). | |
| --appVersionId | -i | The app's version ID. | |
| --region | -z | The region to use: us,au,eu. | 
Example
$ mapps code:push -d <PROJECT BUILD DIRECTORY PATH> -i <APP_VERSION_ID_TO_PUSH>
mapps code:secret
mapps code:secretThe mapps code:secret command manages secret variables for your app hosted on monday-code. It is only available for monday code apps. 
Flags
| Long flag | Short flag | Description | 
|---|---|---|
| -appId | -i | The app's ID. | 
| --key | -k | The variable key (required for setanddelete). | 
| --mode | -m | The management mode: list-keys,set, ordelete. | 
| --value | -v | The variable value (required for set). | 
| --region | -z | The region to use: us,au,eu. | 
Example
$ mapps code:secret -m set -k <KEY> -v <VALUE>
mapps code:status
mapps code:statusThe mapps code:status command provides the status of a specific project hosted on monday-code. It is only available for monday code apps. 
Flags
| Long flag | Short flag | Description | 
|---|---|---|
| --appVersionId | -i | The app's version ID. | 
| --region | -z | The region to use: us,au,eu. | 
Example
$ mapps code:status -i <APP_VERSION_ID>
mapps help [COMMANDS]
mapps help [COMMANDS]The mapps help [COMMANDS] command displays help for mapps. 
Arguments
| Argument | Description | 
|---|---|
| COMMANDS | The command to show help for. | 
Flags
| Long flag | Short flag | Description | 
|---|---|---|
| --nested-commands | -n | Includes all nested commands in the output. | 
Example
$ mapps help [COMMANDS] [-n]
mapps init
mapps initThe mapps init command initializes the mapps config file (i.e., ".mappsrc"). You can use this command to add your API token to access the CLI. 
Flags
| Long flag | Short flag | Description | 
|---|---|---|
| --local | -l | Creates the configuration file locally in the current project working directory. Use this if you are using different access tokens for each of your projects. | 
| --token | -t | The API access token. | 
Example
$ mapps init -t <SECRET_TOKEN>
mapps scheduler:create
mapps scheduler:createThe mapps scheduler:create command creates a new scheduled cron job. It is only available for monday code apps.
Flags
| Long flag | Short flag | Description | Notes | 
|---|---|---|---|
| --appId | -a | The app's unique identifier. | |
| --minBackoffDuration | -b | The minimum backoff duration between retries. | The value should be in seconds. Optional. If omitted, the default will be 10 minutes. | 
| --description | -d | The scheduled job's description. | |
| --name | -n | The scheduled job's name. This is the unique identifier of the job for this app. | There is no whitespace allowed. This should be unique to the job, but the names of deleted jobs can be reused. | 
| --maxRetries | -r | The maximum number of retries for failed jobs. | Optional. | 
| --schedule | -s | The scheduled job's cron expression. | Relative to UTC. Use a cron expression generator to ensure proper format (e.g., Cronhub ). | 
| --timeout | -t | The job execution timeout. | The value should be in seconds. Optional. | 
| --targetUrl | -u | The job's target URL path. | This must start with "/". It will be relative to /mndy-cronjob. | 
| --region | -z | The region to use: us,au, oreu. | 
Example
$ mapps scheduler:create -a APP_ID -s "0 * * * *" -u "/my-endpoint" -n "My-scheduled-job" -d "This job will execute hourly." -r 3
mapps scheduler:delete
mapps scheduler:deleteThe mapps scheduler:delete command deletes a scheduled cron job. It is only available for monday code apps.
Flags
| Long flag | Short flag | Description | 
|---|---|---|
| --appId | -a | The app's unique identifier. | 
| --name | -n | Scheduled job name | 
| --region | -z | The region to use: us,au, oreu. | 
Example
$ mapps scheduler:delete -a APP_ID -n "my-job"
mapps scheduler:list
mapps scheduler:listThe mapps scheduler:list command lists all scheduled cron jobs. It is only available for monday code apps. 
Flags
| Long flag | Short flag | Description | 
|---|---|---|
| --appId | -a | The app's unique identifier. | 
Example
$ mapps scheduler:list -a APP_ID
mapps scheduler:run
mapps scheduler:runThe mapps scheduler:run command runs a scheduled cron job. This can be used to invoke a scheduled job on demand instead of waiting for the next iteration of the schedule. It is only available for monday code apps. 
Flags
| Long flag | Short flag | Description | 
|---|---|---|
| --appId | -a | The app's unique identifier. | 
| --name | -n | Scheduled job name | 
| --region | -z | The region to use: us,au, oreu. | 
Example
$ mapps scheduler:run -a APP_ID -n "my-job"
mapps scheduler:update
mapps scheduler:updateThe mapps scheduler:update command updates a scheduled cron job. It is only available for monday code apps.
Flags
| Long flag | Short flag | Description | Notes | 
|---|---|---|---|
| --appId | -a | The app's unique identifier. | |
| --minBackoffDuration | -b | The minimum backoff duration between retries. | The value should be in seconds. Optional. If omitted, the default will be 10 minutes. | 
| --description | -d | The scheduled job's description. | |
| --name | -n | The scheduled job's name. This is the unique identifier of the job for this app. | There is no whitespace allowed. This should be unique to the job, but the names of deleted jobs can be reused. | 
| --maxRetries | -r | The maximum number of retries for failed jobs. | Optional. | 
| --schedule | -s | The scheduled job's cron expression. | Relative to UTC. Use a cron expression generator to ensure proper format (e.g., Cronhub). | 
| --timeout | -t | The job execution timeout. | The value should be in seconds. Optional. | 
| --targetUrl | -u | The job's target URL path. | This must start with "/". It will be relative to /mndy-cronjob. | 
| --region | -z | The region to use: us,au, oreu. | 
Example
$ mapps scheduler:update -a APP_ID -n "my-job" -d "This job will execute automatically." -r 3 -b 10 -t 60
mapps storage:export
mapps storage:exportThe mapps storage:export command exports all keys and values stored on monday for a specific customer account.
| Short flag | Long flag | Description | 
|---|---|---|
| -a | --appId | The app to retrieve the key for. | 
| -c | --clientAccountId | The client account number. | 
| -d | --fileDirectory | The file path. Optional. If not used, it will take your current folder. | 
| -f | --fileFormat | The file format: CSV or JSON. Optional, the default is JSON. | 
Example
$ mapps storage:export 
// or
$ mapps storage:export -a 12345678790 -c 9876543210 
mapps storage:remove-data
mapps storage:remove-dataThe mapps storage:remove-data command removes all storage data for a specific customer account. 
| Long flag | Short flag | Description | 
|---|---|---|
| --appId | -a | The app's ID. | 
| --clientAccountId | -c | The client account number. | 
| --force | -f | Skip the confirmation step | 
Example
$ mapps storage:remove-data -a 1234567890 -c 9876543210
mapps storage:search
mapps storage:searchThe mapps storage:search command searches keys and values stored on monday for a specific customer account.
| Long flag | Short flag | Description | 
|---|---|---|
| --appId | -a | The app to retrieve the key for. | 
| --clientAccountId | -c | The client account number. | 
| --term | -t | The term to search for. | 
Example
$ mapps storage:search 
// or 
$ mapps storage:search -a 1234567890 -c 9876543210 -t keyword
mapps tunnel:create
mapps tunnel:createThe mapps tunnel:create command creates a networking tunnel to publicly expose code running on the local machine. 
Flags
| Long flag | Short flag | Description | 
|---|---|---|
| --appId | -a | The unique identifier of the app to get a unique tunnel domain for. | 
| --port | -p | The port to forward tunnel traffic to. The default is 8080. | 
Example
$ mapps tunnel:create -p 3000 -a 123456789
Updated 8 days ago
