Build monday.com automations with Claude Code in the terminal
The same Claude as the desktop app, if you'd rather work in Terminal or PowerShell. It builds, checks, saves and tests the whole automation.
You need
- Claude Code installed (Anthropic's setup guide)
- Node.js 18 or later and the Azure CLI (step 1 installs them)
- Plugin Genie installed, the monday connector connected in Power Automate (Getting Started), and permission to create flows
Steps
- Install Node.js and the Azure CLI
In Terminal (this uses Homebrew), then open a new Terminal window:
brew install node azure-cliIn PowerShell, then close and reopen PowerShell so the new commands are found:
winget install OpenJS.NodeJS.LTS winget install Microsoft.AzureCLI - Sign in to Azure
In TerminalPowerShell, run these and check the account shown is the one that owns your Power Automate environment:
az login az account show - Start Claude Code in an empty folder
In TerminalPowerShell:
mkdir flows cd flows claude - Install Microsoft's Power Automate plugin
Paste these one at a time, then restart Claude Code so the plugin loads.
/plugin marketplace add microsoft/power-platform-skills /plugin install power-automate@power-platform-skills - Check setup and choose your environment
Paste these one at a time. Replace [your environment] with the name of the Power Automate environment where your monday connection lives.
/power-automate:setup /power-automate:route-environments Resolve the environment named [your environment], show its ID, and make it current after I confirm. - Build your first automation
/power-automate:create-flow Using the Plugin Genie monday connector, when an item on my monday.com board "Projects" changes its Status column to "Done", post a message in the Teams channel "Delivery" in the team "Operations" with the item name and the Owner column.
- Check it worked
Open the automation in Power Automate and read each step. Change a test item in monday.com, confirm the result arrives, and check the run history shows every step succeeded.
Prompts to copy
Swap in your own board, column and channel names, then paste into Claude Code.
/power-automate:create-flow Using the Plugin Genie monday connector, when an item's Status changes to "Stuck" on my "Projects" board, post the item name and owner to the "Team" channel in Teams.
/power-automate:create-flow When a new response arrives for the form "Client intake", use the Plugin Genie monday connector to create an item on my "Intake" board and fill the Email and Request columns.
/power-automate:create-flow Using the Plugin Genie monday connector, when an item is created on my "Clients" board, create a matching item in the SharePoint list "Clients" at [site URL].
/power-automate:create-flow Every Monday at 8am, use the Plugin Genie monday connector to get items on my "Projects" board whose Due date has passed and whose Status isn't "Done", and email me the list.
/power-automate:create-flow Using the Plugin Genie monday connector, when a new update is posted on an item on my "Support" board, add a row to the Excel table "Activity" in [file] with the item name, author and update text.
/power-automate:create-flow Using the Plugin Genie monday connector, when a sub-item is created on my "Launch" board, create a matching task in the Planner plan "Launch tasks" and assign it to the sub-item's owner.
Tips for better results
- Start with "Using the Plugin Genie monday connector" so it picks Plugin Genie's monday.com steps.
- Put board, column and channel names in quotes, spelled as they are in monday.com.
- Say when it should run first, then what should happen.
- If the automation updates the same board that starts it, add "don't re-trigger on the automation's own changes" to avoid loops.
Questions about Claude Code
"claude" isn't recognized as a command.
Finish installing Claude Code with Anthropic's setup guide, then open a new TerminalPowerShell window.
It can't find the monday connector.
Ask: "List all connectors in this environment, including custom ones." If monday isn't there, check that the monday connection exists in Power Automate, in the environment you chose with /power-automate:route-environments.
It signed in to the wrong Microsoft account.
In TerminalPowerShell, run az logout, then az login with the account that owns your Power Automate environment. Check it with az account show.
The automation ran but something failed.
Ask it to fix it with /power-automate:debug-flow, or open the run history in Power Automate to see which step failed. Still stuck? Contact us.
Can it build a whole automation from one description?
Yes. Once you're comfortable, use /power-automate:build-flow with a full description to build it in one go.
