custom-connectors
Skill46 starsChanged 8 months agoMITView on GitHub
Custom Connectors for Power Platform. Use when: building custom connectors, OpenAPI definitions, OAuth authentication, API Key auth, triggers (polling/webhook), connector policies, Azure APIM integration, DLP considerations.
In this repository40 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- accessibility-uxSkill
- ai-builderSkill
- almSkill
- architectureSkill
- azure-openaiSkill
- business-process-flowsSkill
- canvas-appsSkill
- code-appsSkill
- code-reviewerSkill
- copilot-studioSkill
- dashboardsSkill
- data-migrationSkill
- dataverse-mcpSkill
- dataverseSkill
- dataverse-web-apiSkill
- devops-engineerSkill
- env-strategySkill
- governanceSkill
- integration-patternsSkill
- licensingSkill
- m365-integrationSkill
- model-driven-appsSkill
- observabilitySkill
- pcfSkill
- perf-optimiseSkill
- platform-builderSkill
- pluginsSkill
- power-automateSkill
- power-biSkill
- power-pagesSkill
- power-platform-teamSkill
- project-managerSkill
- securitySkill
- solutions-architectSkill
- spec-driven-devSkill
- test-engineSkill
- testingSkill
- uat-coordinatorSkill
- web-resourcesSkill
The file
We split this skill into the rules it gives an agent
7 rules. About 0 are common, 4 are distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
Distinctive · estimate
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 54
Always use x-ms-summary on every parameter and property (maker-friendly display names)
- Very specific: line 55
Always set x-ms-visibility: "internal" for technical parameters users shouldn't see
- Distinctive: line 56
Always define response schemas (Power Automate needs them for dynamic content)
- Very specific: line 57
Use x-ms-dynamic-values for dropdown parameters (don't force users to type GUIDs)
- Distinctive: line 58
Test with both Power Automate and Canvas App (behaviour can differ)
- Distinctive: line 70
Not classifying connector in DLP policy (blocks use with Dataverse/SharePoint)
- Distinctive: line 72
Not including connector in solution (breaks ALM)
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Skill: Custom Connectors
When to Use
Trigger when building, configuring, or debugging custom connectors — reusable API wrappers that expose REST APIs as Power Platform connectors for use in Power Automate, Power Apps, and Copilot Studio.
When to Use Custom Connectors vs Alternatives
| Scenario | Use | Why |
| Standard connector exists | Standard connector | Zero maintenance, Microsoft-supported |
| REST API used in one flow only | HTTP action in Power Automate | Simpler, no connector overhead |
| REST API used across multiple flows/apps | Custom connector | Reusable, typed, discoverable |
| REST API with complex auth (OAuth 2.0) | Custom connector | Auth handled once, shared across all uses |
| High-volume API calls needing throttling | Custom connector + Azure APIM | APIM handles rate limiting, caching, monitoring |
| On-premises API (no public endpoint) | Custom connector + On-premises Data Gateway | Gateway bridges private network |
Project Structure
custom-connectors/
contoso-erp/
apiDefinition.swagger.json # OpenAPI 2.0 definition
apiProperties.json # Connector metadata + policies
icon.png # 160x160 connector icon
settings.json # Test settings
README.md⚠️ REQUIRED: Load Sub-Files Before Implementation
SKILL.md is a summary only — it is NOT sufficient for implementation.
The detailed content (complete payloads, XML templates, working examples, edge-case handling) lives in sub-files in the same directory as this SKILL.md. Before writing any code, you MUST use read_file on the sub-files relevant to your task:
- OpenAPI Definition — Swagger structure, action definitions, schema definitions, x-ms extensions, dynamic values/schema
- Authentication — API Key, OAuth 2.0 (Authorization Code), Azure AD / Entra ID, apiProperties.json configuration
- Triggers — Polling triggers (batch), webhook triggers, deregistration endpoint, trigger hints
- Policies & APIM — Connector policies (set header, route request), Azure APIM integration, DLP classification, CLI workflow, solution-aware connectors
Best Practices
- Always use
x-ms-summaryon every parameter and property (maker-friendly display names) - Always set
x-ms-visibility: "internal"for technical parameters users shouldn't see - Always define response schemas (Power Automate needs them for dynamic content)
- Use
x-ms-dynamic-valuesfor dropdown parameters (don't force users to type GUIDs) - Test with both Power Automate and Canvas App (behaviour can differ)
- Version your connector:
host+basePathshould include version (e.g.,/v2/) - Icon must be exactly 160x160px PNG with brand colour background
Anti-Patterns
- Missing
x-ms-summaryon parameters (users see raw field names) - Missing response schemas (dynamic content unavailable in flow designer)
- Using
x-ms-visibility: "internal"on required user inputs (hides needed fields) - Hardcoded hostnames in OpenAPI definition (use connection parameter for environment switching)
- Not classifying connector in DLP policy (blocks use with Dataverse/SharePoint)
- Polling triggers without proper 202 handling (triggers fire with empty data)
- Not including connector in solution (breaks ALM)
- Using Basic auth for production connectors (use OAuth 2.0 or API key)
- Missing error response definitions (poor error handling in flows)
Related Skills
power-automate— Flows consume custom connectors as actions and triggerscode-apps— Code Apps can use connectors viapac code add-data-source -cdataverse-web-api— Alternative when data lives in Dataverse (no connector needed)alm— Solution packaging and deployment of custom connectors
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

