Custom Connectors logo

Custom Connectors

Community
korchard333
custom-connectors

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.

Overview

Publisherkorchard333
Repositoryclaude-power-platform-community
Skill namecustom-connectors
Stars
50
Forks
6
Bundled files
5
LicenseMIT
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • 5 bundled files

    Scripts, templates, and references the model can read while it works. Files are read-only and never executed.

  • Open source

    Published by korchard333 on GitHub. Read the source before you install it.

Installation

Install the Custom Connectors AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/korchard333/claude-power-platform-community/tree/main/.claude/skills/custom-connectors
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/korchard333/claude-power-platform-community.git /tmp/claude-power-platform-community
mkdir -p .claude/skills
cp -r /tmp/claude-power-platform-community/.claude/skills/custom-connectors .claude/skills/custom-connectors
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Custom Connectors in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Custom Connectors on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Custom Connectors is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

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

ScenarioUseWhy
Standard connector existsStandard connectorZero maintenance, Microsoft-supported
REST API used in one flow onlyHTTP action in Power AutomateSimpler, no connector overhead
REST API used across multiple flows/appsCustom connectorReusable, typed, discoverable
REST API with complex auth (OAuth 2.0)Custom connectorAuth handled once, shared across all uses
High-volume API calls needing throttlingCustom connector + Azure APIMAPIM handles rate limiting, caching, monitoring
On-premises API (no public endpoint)Custom connector + On-premises Data GatewayGateway 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-summary on 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-values for dropdown parameters (don't force users to type GUIDs)
  • Test with both Power Automate and Canvas App (behaviour can differ)
  • Version your connector: host + basePath should include version (e.g., /v2/)
  • Icon must be exactly 160x160px PNG with brand colour background

Anti-Patterns

  • Missing x-ms-summary on 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 triggers
  • code-apps — Code Apps can use connectors via pac code add-data-source -c
  • dataverse-web-api — Alternative when data lives in Dataverse (no connector needed)
  • alm — Solution packaging and deployment of custom connectors

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Custom Connectors AI skill do?

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.

Why use Custom Connectors on TypingMind?

Because you install it once and use it with any model. Custom Connectors is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Custom Connectors in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/korchard333/claude-power-platform-community/tree/main/.claude/skills/custom-connectors. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Custom Connectors?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Custom Connectors?

As many as you like. As long as a model supports skills, you can use Custom Connectors with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Custom Connectors AI skill free?

Yes. It is published on GitHub by korchard333 under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇