Creating Custom Connectors in Microsoft Copilot Studio (Power Virtual Agents)

Custom connectors in Microsoft Copilot Studio (formerly Power Virtual Agents) allow you to integrate external services, APIs, or data sources into your chatbot. This provides flexibility to extend the chatbot’s capabilities beyond built-in options.

---

Step-by-Step Guide to Creating a Custom Connector in Copilot Studio

Step 1: Understanding Custom Connectors

Before creating a custom connector, understand that:

• It acts as a bridge between your chatbot and an external API.
• It can connect to RESTful APIs using authentication methods such as API keys, OAuth 2.0, or Basic Authentication.
• Once created, it can be reused across multiple applications within Power Platform.

---

Step 2: Preparing the API

You need an API to integrate with Copilot Studio.
Ensure the API:

• Is publicly accessible or within an authenticated network.
• Uses a standard REST structure (GET, POST, PUT, DELETE).
• Has a valid OpenAPI (Swagger) specification or Postman collection for easy import.
• Supports authentication if required.

---

Step 3: Accessing Power Platform to Create a Custom Connector

To create a custom connector in Copilot Studio, follow these steps:

1. Go to Power Platform
   • Open Power Apps or go to Power Automate.
   • Sign in with your Microsoft account.
2. Navigate to Custom Connectors
   • In the left navigation panel, click on Dataverse → Custom Connectors.
   • Click + New Custom Connector.
   • Choose an option:
     • Create from blank (if you want to manually configure everything).
     • Import from OpenAPI (Swagger).
     • Import from Postman collection.

---

Step 4: Defining Custom Connector Details

1. Enter Basic Information
   • Name your connector (e.g., “Weather API Connector”).
   • Add an icon (optional) and description.
2. Set Up Authentication
   • Choose an authentication type based on your API:
     • No authentication – If API is public.
     • API Key – If API requires a key in the header or query.
     • OAuth 2.0 – If API requires user authentication.
     • Basic Authentication – If API requires a username and password.

---

Step 5: Defining API Endpoints

1. Enter Base URL
   • Input the API’s base URL (e.g., https://api.weather.com).
2. Add Actions (Operations)
   • Click + New Action.
   • Provide:
     • Summary – A brief description.
     • Operation ID – A unique identifier.
     • Request URL – The endpoint URL (e.g., /forecast).
     • Method Type – Select from GET, POST, PUT, DELETE.
     • Headers & Query Parameters – Add required parameters.

---

Step 6: Configuring Responses

1. Click “Response” Section
2. Add a Sample Response
   • Run the API in Postman and copy a successful response JSON.
   • Paste it in the Response Definition.
   • Define response parameters (e.g., temperature, humidity).

---

Step 7: Testing the Custom Connector

1. Click “Test” Tab.
2. Authenticate (if required).
3. Enter Parameters and click Test Operation.
4. If successful, you will see a valid JSON response.

---

Step 8: Using the Custom Connector in Copilot Studio

1. Open Microsoft Copilot Studio.
2. Go to Topics and create/edit a topic.
3. Click Add an Action.
4. Select Call an Action → Choose Custom Connector.
5. Map input/output parameters.
6. Save and Test.

---

Final Notes

• Custom connectors can be shared across Power Apps and Power Automate.
• Use environment variables for secure API key storage.
• Enable logging to monitor API requests.