$ ~/registry/skill/microsoft-plugins-power-pages-skills-integrate-webapi

SKILL

integrate-webapi

Name: integrate-webapi
Author: microsoft

Integrate Power Pages Web API into frontend with permissions and deployment.

Stars

★ 440

Source

GitHub

Updated

2026-07-11

// securityLow risk

Prompt only, no code
Open source
Community-trusted· 440

Running security audit…

Credentials
Network egress
Code execution
Data access
Supply chain

// install

Copy the install command and let the AI configure it · recommended for beginners

Please install the "integrate-webapi" skill from askskill:
1. Download https://raw.githubusercontent.com/microsoft/power-platform-skills/main/plugins/power-pages/skills/integrate-webapi/SKILL.md
2. Save it as ~/.claude/skills/integrate-webapi/SKILL.md
3. Reload skills and tell me it's ready

// download

Download SKILL.mdInstall manifest ↗

// examples

Connect frontend to Dataverse data retrieval

Prompt

Help me integrate the Web API into a Power Pages frontend to read data visible to the current user from the Dataverse Contact table. Please provide a frontend call example, required table permission setup, and deployment considerations.

Expected

Provides sample frontend code for reading data, matching table permission guidance, and a deployment checklist for production.

Create records from form submission

Prompt

I want a Power Pages form submission to create a new record in the Dataverse Case table through the Web API. Help me design the frontend call, permission configuration, and release process so visitor submissions work correctly.

Expected

Outputs a frontend approach for record creation, permission recommendations for visitor access, and implementation steps from testing to release.

Implement full CRUD integration

Prompt

Plan a complete Web API CRUD integration for my Power Pages site targeting the Custom Requests table. Include frontend code structure for read, create, update, and delete operations, table permission strategy, and recommendations for deploying to production.

Expected

Delivers a CRUD integration plan with code structure, permission matrix, and production deployment guidance for direct implementation.

// docs

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

Integrate Web API

Integrate Power Pages Web API into a code site's frontend. This skill orchestrates the full lifecycle: analyzing where integrations are needed, implementing API client code for each table, configuring permissions and site settings, and deploying the site.

Core Principles

First table sequential, then parallel: The first table must be processed alone because it creates the shared powerPagesApi.ts client. Once that exists, remaining tables can be processed in parallel since each creates independent files (types, service, hooks).
Parallelize independent agents: The table-permissions-architect and webapi-settings-architect agents are independent — invoke them in parallel rather than sequentially.
Permissions require deployment: The .powerpages-site folder must exist before table permissions and site settings can be configured. Integration code can be written without it, but permissions cannot.
Use TaskCreate/TaskUpdate: Track all progress throughout all phases — create the todo list upfront with all phases before starting any work.

Prerequisites:

An existing Power Pages code site created via /create-site

A Dataverse data model (tables/columns) already set up via /setup-datamodel or created manually

The site must be deployed at least once (.powerpages-site folder must exist) for permissions setup

Initial request: $ARGUMENTS

Workflow

Verify Site Exists — Locate the Power Pages project and verify prerequisites
Explore Integration Points — Analyze site code and data model to identify tables needing Web API integration
Review Integration Plan — Present findings to the user and confirm which tables to integrate
Implement Integrations — Use the webapi-integration agent for each table
Verify Integrations — Validate all expected files exist and the project builds successfully
Setup Permissions & Settings — Choose permissions source (upload diagram or let the architects analyze), then configure table permissions and Web API site settings with case-sensitive validated column names
Review & Deploy — Ask the user to deploy the site and invoke /deploy-site if confirmed

Phase 1: Verify Site Exists

Goal: Locate the Power Pages project root and confirm that prerequisites are met

Actions:

1.1 Locate Project

Look for powerpages.config.json in the current directory or immediate subdirectories to find the project root. Use your file-search tool (e.g., Glob with patterns powerpages.config.json and */powerpages.config.json) rather than a shell-specific command.

If not found: Tell the user to create a site first with /create-site.

1.2 Read Existing Config

Read powerpages.config.json to get the site name.

1.3 Detect Framework

Read package.json to determine the framework (React, Vue, Angular, or Astro). See ${CLAUDE_PLUGIN_ROOT}/references/framework-conventions.md for the full framework detection mapping.

1.4 Check for Data Model

Look for .datamodel-manifest.json to discover available tables:

**/.datamodel-manifest.json

If found, read it — this is the primary source for table discovery.

1.5 Check Deployment Status

Look for the .powerpages-site folder:

**/.powerpages-site

If not found: Warn the user that the permissions phase (Phase 5) will require deployment first. The integration code (Phases 2–4) can still proceed.

Output: Confirmed project root, framework, data model availability, and deployment status

Phase 2: Explore Integration Points

Goal: Analyze the site code and data model to identify all tables needing Web API integration

Actions:

…

View full docs ↗

Generate sample Dataverse records for testing and demoing a Power Pages site.

microsoftGet→

$ loading_