Add Connector
Wire an arbitrary Microsoft Power Platform connector into a Power Apps code app when no dedicated add-* skill exists.
Overview
Add Connector is an agent skill for the Build phase that adds any Power Platform connector to a Power Apps code app using the generic add-data-source workflow.
Install
npx skills add https://github.com/microsoft/power-platform-skills --skill add-connectorWhat is this skill?
- Six-step workflow: memory bank check, identify connector, add, inspect and configure, build, update memory bank
- Points to dedicated skills for Dataverse, Azure DevOps, Teams, Excel, OneDrive, SharePoint, and Office 365 when applicab
- Uses shared Power Platform instructions and Microsoft connector reference documentation
- Supports user-specified connectors via arguments or an AskUserQuestion discovery step
- Generic fallback when `/add-*` specialized skills do not cover the connector
- 6-step connector workflow
Adoption & trust: 75 installs on skills.sh; 349 GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
Your Power Apps code app needs a connector that has no dedicated `/add-*` skill, and you are unsure how to add and configure it without breaking the project context.
Who is it for?
Builders in an active Power Apps code app who know the connector name and have or can create an environment connection.
Skip if: Greenfield apps with no code app scaffold, or cases where a specific skill such as add-dataverse or add-teams already covers the connector.
When should I use this skill?
User invokes add-connector or asks to integrate a Power Platform connector not covered by a specific add-* skill in the code app.
What do I get? / Deliverables
The connector is added, configured against a real connection ID, built successfully, and recorded in memory-bank.md for later agent steps.
- Configured connector in the code app
- Updated memory-bank.md
- Successful project build after integration
Recommended Skills
Journey fit
Build integrations is the primary journey moment: you are extending a code app with external data sources and connectors. Integrations subphase matches power-apps CLI add-data-source flows, connection IDs, and connector configuration—not UI polish or launch.
How it compares
Reach for this generic skill only after checking dedicated Microsoft add-* skills in the same plugin pack.
Common Questions / FAQ
Who is add-connector for?
Developers and solo builders using Power Apps code apps who need to integrate a Microsoft or third-party connector not covered by a named add-* skill.
When should I use add-connector?
During Build integrations when wiring data sources into a code app, after memory-bank.md exists and you have identified the connector from Microsoft docs or user input.
Is add-connector safe to install?
Check this page’s Security Audits panel; the skill allows Bash and edits and can run platform CLIs—use only in trusted repos and review connection scopes in your tenant.
SKILL.md
READMESKILL.md - Add Connector
**📋 Shared Instructions: [shared-instructions.md](${CLAUDE_PLUGIN_ROOT}/shared/shared-instructions.md)** - Cross-cutting concerns. # Add Connector (Generic) Fallback skill for any connector not covered by a specific `/add-*` skill. For common connectors, prefer the dedicated skills: - `/add-dataverse` -- Dataverse tables - `/add-azuredevops` -- Azure DevOps - `/add-teams` -- Microsoft Teams - `/add-excel` -- Excel Online (Business) - `/add-onedrive` -- OneDrive for Business - `/add-sharepoint` -- SharePoint Online - `/add-office365` -- Office 365 Outlook (calendar, email, contacts) ## Workflow 1. Check Memory Bank → 2. Identify Connector → 3. Add Connector → 4. Inspect & Configure → 5. Build → 6. Update Memory Bank --- ### Step 1: Check Memory Bank Check for `memory-bank.md` per [shared-instructions.md](${CLAUDE_PLUGIN_ROOT}/shared/shared-instructions.md). ### Step 2: Identify Connector **If `$ARGUMENTS` is provided or the caller already specified the connector**, use it directly and skip the question below. Otherwise, ask the user which connector they want to add. Browse available connectors: [Connector Reference](https://learn.microsoft.com/en-us/connectors/connector-reference/) **Before proceeding, check if the connector has a dedicated skill. If it does, delegate immediately and STOP:** | Connector API name | Delegate to | | ----------------------- | ------------------ | | `sharepointonline` | `/add-sharepoint` | | `teams` | `/add-teams` | | `excelonlinebusiness` | `/add-excel` | | `onedriveforbusiness` | `/add-onedrive` | | `azuredevops` | `/add-azuredevops` | | `office365` | `/add-office365` | | `commondataservice` | `/add-dataverse` | Invoke the appropriate skill with the same `$ARGUMENTS` and **do not continue this skill's workflow**. Common connector API names: - `sharepointonline`, `teams`, `excelonlinebusiness`, `onedriveforbusiness` - `azuredevops`, `azureblob`, `azurequeues` - `office365`, `office365users`, `office365groups` - `sql`, `commondataservice` ### Step 3: Add Connector **First, find the connection ID** (see [connector-reference.md](${CLAUDE_PLUGIN_ROOT}/shared/connector-reference.md)): Run the `/list-connections` skill. Find the connector in the output. If none exists, direct the user to create one using the environment-specific Connections URL — construct it from the active environment ID in context (from `power.config.json` or a prior step): `https://make.powerapps.com/environments/<environment-id>/connections` → **+ New connection** → search for the connector → Create. ```bash # Non-tabular connectors (Teams, Azure DevOps, etc.) npx power-apps add-data-source -a <connector-api-name> -c <connection-id> # Tabular connectors (SharePoint, Excel, SQL, etc.) -- also need dataset and table npx power-apps add-data-source -a <connector-api-name> -c <connection-id> -d '<dataset>' -t '<table>' ``` **Parameter reference:** - `-a` (apiId) -- connector name (e.g., `sharepointonline`, `teams`) - `-c` (connectionId) -- **required** for all non-Dataverse connectors. Get from `/list-connections`. - `-d` (dataset) -- required for tabular datasources (e.g., SharePoint site URL, SQL database). Not needed for Dataverse. - `-t` (table) -- table/list name for tabular datasources (e.g., SharePoint list, Dataverse table logical name) ### Step 4: Inspect & Configure After adding, inspect the generated files. **Generated service files can be very large** -- use `Grep` to find specific methods instead of reading the entire file: ``` Grep pattern="async \w+" path="src/generated/services/<Connector>Servic