power-automate-flows

Create, manage, and deploy Power Automate cloud flows via the Dataverse Web API.

12|4|Updated Mar 1, 2026
One-click install
npx skills add https://github.com/markus41/Claude-m --skill power-automate-flows
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: power-automate-flows
Source: https://github.com/markus41/Claude-m/tree/main/excel-office-scripts/skills/power-automate-flows
Command: npx skills add https://github.com/markus41/Claude-m --skill power-automate-flows

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Streamlines the end-to-end creation, management, and deployment of Power Automate flows via the Dataverse Web API, reducing manual UI work and configuration time.

Core Features & Use Cases

  • Programmatic flow creation, update, and enablement via REST API with Flow records in Dataverse.
  • Support for Trigger/Action schemas, connection references, error handling, and Office Script integration.
  • CI/CD provisioning and multi-environment promotion patterns for reliable deployments.

Quick Start

Provide a complete payload and call the Dataverse API to create and enable a flow.

Frequently Asked Questions about power-automate-flows

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create Power Automate cloud flows programmatically using the Dataverse API?

You can create Power Automate cloud flows programmatically by sending a complete flow definition payload to the Dataverse Web API, which provisions and enables the flow record without manual UI configuration.

What is the best way to deploy Power Automate flows across multiple environments?

The best way to deploy Power Automate flows across multiple environments is using CI/CD provisioning patterns via the Dataverse Web API, ensuring reliable multi-environment promotion with robust guardrails.

How does connection reference management work when provisioning flows via the Dataverse Web API?

Connection reference management works by mapping connection references within the flow definition payload sent to the Dataverse Web API, ensuring triggers and actions authenticate correctly across environments.

Can I integrate Office Scripts into Power Automate flow definitions deployed through the Dataverse API?

Yes, you can integrate Office Scripts into Power Automate flow definitions deployed through the Dataverse API by including the script execution actions within the flow payload sent to Dataverse.

What are the limitations of managing Power Automate flows via the Dataverse Web API instead of the UI?

Managing flows via the Dataverse Web API requires constructing raw flow definitions, trigger schemas, and action schemas manually, increasing complexity compared to the visual UI, but enabling CI/CD automation.

Do I need to handle trigger and action schemas separately when automating Power Automate flow creation?

Yes, when automating Power Automate flow creation via the Dataverse API, you must define trigger and action schemas correctly within the flow definition payload to ensure the workflow functions as intended.