deploy-flow

Plugin check: Run node "${CLAUDE_PLUGIN_ROOT}/scripts/check-version.js" — if it outputs a message, show it to the user before proceeding.

Deploy Power Automate Cloud Flow

Deploy an existing Power Automate cloud flow JSON definition to a Dataverse environment using the Flow API. Optionally adds the flow to a Dataverse solution for ALM purposes.

Core Principles

• Verify before acting: Always confirm PAC CLI availability, authentication status, and the target environment before attempting deployment.
• Use TaskCreate/TaskUpdate: Track all progress throughout all phases — create the todo list upfront with all phases before starting any work.
• Validate first: Always validate the flow JSON before deploying. Never deploy an invalid definition.
• Never change environment settings without consent: If deployment requires modifying environment configuration, always explain and get explicit user permission.

Initial request: $ARGUMENTS

---

Phase 1: Verify PAC CLI

Goal: Ensure PAC CLI is installed and available

Actions:

1. Create todo list with all 6 phases (see Progress Tracking table).

2. Run pac help to check PAC CLI availability:

   pac help
   

3. If PAC CLI is not installed: Tell the user to install it:

   dotnet tool install --global Microsoft.PowerApps.CLI.Tool
   

4. Also verify Azure CLI is available (needed for Flow API auth):

   az version
   

   If not installed, direct the user to install it.

Output: PAC CLI and Azure CLI verified

---

Phase 2: Verify Authentication

Goal: Ensure the user is authenticated with both PAC CLI and Azure CLI

Actions:

1. Run pac org who to check PAC CLI auth:

   pac org who
   

2. Extract: Environment Name, Org URL, Environment ID, User Email.

3. If not authenticated: Guide through pac auth create --environment "<URL>".

4. Run az account show to verify Azure CLI auth:

   az account show --query "{name:name, user:user.name}" -o table
   

5. If not authenticated: Run az login.

Output: Both PAC CLI and Azure CLI authenticated

---

Phase 3: Confirm Environment and Locate Flow File

Goal: Confirm the target environment and locate the flow JSON file

Actions:

1. Present the current environment and ask for confirmation via AskUserQuestion:

   Question	Options
   You are connected to <ENV_NAME> (<ENV_URL>). Deploy to this environment?	Yes, use this environment; No, let me choose a different one

2. If "No": Run pac org list, let user select, then switch.

3. Locate the flow JSON file:

   • If provided via $ARGUMENTS, use that path

   • Otherwise, search for flow JSON files:

     find . -name "*.json" -path "*/flows/*" -o -name "flow-definition.json" 2>/dev/null
     

   • If multiple found, ask the user which to deploy via AskUserQuestion

   • If none found, ask the user to provide the path

4. Read and display the flow file's displayName for confirmation.

Output: Target environment confirmed and flow file located

---

Phase 4: Validate the Flow

Goal: Validate the flow JSON before deployment

Actions:

1. Run the validation script:

   node "${CLAUDE_PLUGIN_ROOT}/scripts/validate-flow.js" --file "<path-to-flow.json>"
   

2. Parse the JSON output:

   • If valid: true: Present validation summary and proceed

   • If valid: false: Present errors to the user. Offer to fix them or abort:

     Question	Options
     The flow has validation errors. Would you like me to fix them?	Yes, fix the errors; No, abort deployment

   • If "Yes": Fix the errors in the JSON file and re-validate

   • If "No": Stop

Output: Flow JSON validated successfully

---

Phase 5: Deploy the Flow

Goal: Deploy the flow to the target environment via the Flow API

Actions:

1. Run the deployment script:

   node "${CLAUDE_PLUGIN_ROOT}/scripts/deploy-flow.js" --file "<path>" --environment-id "<env-id>"
   

2. Parse the JSON output:

   • If success: true:

     • Display: Flow ID, Display Name, State
     • Proceed to ask about solution packaging

   • If success: false:

     • Present the error to the user
     • Common errors and fixes:
       • InvalidRequestContent with description → Remove the description field from properties
       • Unauthorized / 403 → Re-authenticate: az login
       • ConnectionNotConfigured → The user needs to set up connection references in the Power Automate portal
     • After fixing, retry deployment

3. Solution packaging — Ask via AskUserQuestion:

   Question	Options
   Would you like to add this flow to a Dataverse solution for ALM?	Yes, add to a solution; No, skip

   If "Yes":

   • Ask for the solution unique name (or list existing: pac solution list)

   • Re-run deployment with --solution-name:

     node "${CLAUDE_PLUGIN_ROOT}/scripts/deploy-flow.js" --file "<path>" --environment-id "<env-id>" --solution-name "<name>"
     

   • Or add manually by running the export script:

     node "${CLAUDE_PLUGIN_ROOT}/scripts/export-flow.js" --solution-name "<name>" --output "./solutions"
     

Output: Flow deployed to environment

---

Phase 6: Verify and Summarize

Goal: Verify the deployment and present a summary

Actions:

1. Verify the flow exists in the environment:

   node "${CLAUDE_PLUGIN_ROOT}/scripts/list-flows.js" --filter "<flow-display-name>"
   

2. Present the deployment summary:

   Deployment Summary

   Property	Value
   Flow Name	[displayName]
   Flow ID	[flowId]
   State	Started
   Environment	[envName] ([envUrl])
   Solution	[solutionName or "Not in a solution"]
   Source File	[file path]

3. Remind the user about connection references:

   Important: If this is the first time deploying a flow with this connector to this environment, you may need to configure the connection reference in the Power Automate portal. Go to Power Automate > My flows > [flow name] > Edit and set up any missing connections.

4. Suggest next steps:

   • /create-flow — Create another flow
   • /list-flows — View all flows in the environment
   • Export the solution: pac solution export --name <solution> --path <output.zip>

Output: Deployment verified and summary presented

---

Important Notes

Key Decision Points (Wait for User)

1. After Phase 2: Confirm authentication
2. At Phase 3: Confirm environment and flow file
3. At Phase 4: Fix validation errors or abort
4. At Phase 5: Add to solution or skip

Progress Tracking

Before starting Phase 1, create a task list with all phases using TaskCreate:

Task subject	activeForm	Description
Verify PAC CLI	Verifying PAC CLI	Check PAC CLI and Azure CLI installation
Verify authentication	Verifying authentication	Check auth status for PAC CLI and Azure CLI
Confirm environment and locate flow	Confirming environment	Confirm target environment and find flow JSON file
Validate the flow	Validating flow	Run validation script on the flow JSON
Deploy the flow	Deploying flow	Deploy via Flow API, optionally add to solution
Verify and summarize	Verifying deployment	Confirm deployment and present summary

Mark each task in_progress when starting it and completed when done via TaskUpdate.

---

Begin with Phase 1: Verify PAC CLI