Add Connector

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

📋 Shared instructions: shared-instructions.md | Connector reference: connector-reference.md — read both first.

Add Connector (Generic)

Fallback skill for any connector not covered by a dedicated /add-* skill. For common connectors, prefer the dedicated skills:

• /add-dataverse — Dataverse tables
• /add-sharepoint — SharePoint Online

(More dedicated skills will land in v1: /add-teams, /add-excel, /add-onedrive, /add-azuredevops, /add-office365.)

The native host runtime (@microsoft/power-apps-native-host) handles connector routing, connection resolution, and OAuth consent through PowerAppsProvider in app/_layout.tsx — no separate executor wiring is needed.

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

Telemetry checkpoint: validate_connector_project

Check for memory-bank.md per shared-instructions.md.

Also confirm we're inside a Power Apps mobile app:

test -f power.config.json && test -f app.config.js

If either is missing, instruct the user to run /create-mobile-app first and stop.

Step 2 — Identify Connector

Telemetry checkpoint: resolve_connector_request

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.

Before proceeding, check if the connector has a dedicated skill. If it does, delegate immediately and STOP:

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

Cloud flows are supported by the Power Apps CLI, but they are not connector data sources. If the user wants to invoke an existing Power Automate cloud flow from the app, use the flow-specific commands instead of pa app add data-source:

$PA app list-flows --search '<flow-name-or-keyword>' --json
$PA app add flow --flow-id <flow-guid> --non-interactive

To remove a flow later (only when the user asks; pa needs --force for a non-interactive removal):

$PA app remove flow --flow-id <flow-guid> --force --non-interactive

After pa app add flow, continue at Step 4 and inspect the generated service/model files the same way as connector data sources.

Step 3 — Add Connector

Telemetry checkpoint: generate_connector_data_source

First, get the connection ID or connection reference (see connector-reference.md):

Run the /list-connections skill with the connector API ID (for example shared_office365users). Capture the exact connectionId from pa connection create, or the connectionRef from pa connection list-references if the caller is solution-aware. If creation cannot complete in the CLI, 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 environmentId or a prior step): https://make.powerapps.com/environments/<environment-id>/connections → + New connection → search for the connector → Create.

Classify the connector before running pa app add data-source:

For action-style connectors, print before starting:

"→ Running pa app add data-source for <connector>. ~10–30 seconds (writes generated services + connector schemas)."

Then run:

$PA app add data-source --connector <apiId> --connection-id <connectionId>

For table-based connectors, discover datasets and tables first:

$PA connection list-datasets --connector <apiId> --connection-id <connectionId> --json
$PA connection list-tables --connector <apiId> --connection-id <connectionId> --dataset '<dataset>' --json

Present the datasets/tables to the user if they did not specify them. Add one data source per selected table:

$PA app add data-source --connector <apiId> --connection-id <connectionId> --dataset '<dataset>' --table '<table>'

For SQL stored procedures, discover procedures only when the user asks to invoke a stored procedure rather than a table:

$PA connection list-procedures --connection-id <connectionId> --dataset '<database>' --json
$PA app add data-source --connector shared_sql --connection-id <connectionId> --dataset '<database>' --procedure '<procedure>'

For Dataverse actions/functions rather than tables, discovery is available but this plugin only adds Dataverse table CRUD:

$PA app find-dataverse-api --search '<operation-name>' --json

Surface the matching operation metadata and STOP with a clear note that this plugin can add Dataverse table CRUD through /add-dataverse, but does not add Dataverse actions/functions.

If the user actually needs Dataverse table CRUD, stop and delegate to /add-dataverse; do not add Dataverse tables from this generic connector skill.

Parameter reference:

• --connector — connector API ID (often shared_<connector>, e.g., shared_office365users). Use the exact value provided by the caller or connector docs.
• --connection-id / -c — required for non-Dataverse connectors unless using --connection-ref. Get from pa connection create, the maker portal, or caller context.
• --connection-ref — optional connection reference name when adding into a solution-aware app.
• --dataset / -d — required for table-based datasources (for example SharePoint site URL, Excel file/location, SQL database).
• --table — table/list/resource name for table-based datasources.
• --procedure — SQL stored procedure name when adding a stored procedure instead of a table.
• --non-interactive — use only on commands whose required options are fully supplied and whose implementation supports non-interactive omission of optional prompts. Do not add --environment-id to app-root verbs once power.config.json exists.
• --solution-id / -s — optional solution identifier when the data source should be added to a specific solution.