Microsoft Integration Guide | Rembrandt Help Center

Connect Rembrandt to Microsoft Copilot Studio, Microsoft 365 Copilot, and Azure AI Studio using OpenAPI-based integrations to access your prospect data directly within Microsoft's AI tools.

What are Microsoft Integrations?

Connect the Rembrandt API to Microsoft's AI platforms to access your prospect data directly in your Microsoft AI conversations and workflows.

Microsoft Copilot Studio

What it is: Microsoft Copilot Studio lets you build custom AI agents (chatbots) that can interact with users and access external data.

When to use it: Use this integration when you want to create a custom chatbot or AI assistant that can answer questions about your prospects. For example, build a chatbot for your sales team that can answer "Show me high-urgency prospects" or "What prospects are in the Netherlands?"

How it works: Add the Rembrandt API as REST API tools to your Copilot Studio agents, enabling them to search and retrieve prospect data during conversations. Alternatively, you can use a Power Platform custom connector (see Power Platform section below).

Microsoft 365 Copilot

What it is: Microsoft 365 Copilot is the AI assistant built into Microsoft 365 apps (Word, Excel, Teams, Outlook, etc.) that helps users with their work.

When to use it: Use this integration when you want all users in your organization to access Rembrandt prospect data directly from Microsoft 365 apps. For example, users can ask Copilot in Teams "What prospects do we have with urgency score 5?" without leaving their workflow.

How it works: Unlike Copilot Studio, Microsoft 365 Copilot cannot directly connect to APIs. Instead, you connect the Rembrandt API via:

Copilot Studio / Power Platform (recommended): Build actions or connectors in Power Platform that call the Rembrandt API, then use these in Copilot Studio agents that are accessible from Microsoft 365 Copilot
Declarative agents / plugins (enterprise): Create declarative agents using Microsoft 365 Agents Toolkit that reference the Rembrandt API

Important: The most common and easiest route is to use Copilot Studio with Power Platform connectors (see Power Platform section below).

Power Platform

What it is: Power Platform includes Power Automate (workflow automation), Power Apps (custom apps), Logic Apps (enterprise integration), and can be used with Copilot Studio.

When to use it: Use this integration when you want to:

Power Automate: Automate workflows like daily prospect digests, CRM syncs, or alerts when new high-urgency prospects appear
Power Apps: Build custom apps that display and work with Rembrandt prospect data
Logic Apps: Create enterprise-level integrations between Rembrandt and other systems
Copilot Studio: Use the connector in your custom agents (alternative to the REST API tools method described in the Microsoft Copilot Studio Integration section below)

How it works: Build a custom connector for the Rembrandt API that can be used across all Power Platform tools, including Copilot Studio. This gives you two options for Copilot Studio: use REST API tools directly (see Microsoft Copilot Studio Integration) or use a Power Platform custom connector.

All integrations use the Rembrandt REST API OpenAPI specification available at https://api.rembrandtagents.com/docs/json.

How the Platforms Work Together

Understanding how these platforms connect to the Rembrandt API:

Integration Methods Overview

1. Copilot Studio (Direct API connection)

Method A: REST API tools (direct connection to Rembrandt API)
Method B: Power Platform custom connector (reusable across Power Platform)
Both methods work in Copilot Studio - choose based on your needs

2. Microsoft 365 Copilot (Indirect connection)

Route 1 (Recommended): Via Copilot Studio agent → uses REST API tools OR Power Platform connector → connects to Rembrandt API
Route 2 (Enterprise): Via declarative agents/plugins → directly references Rembrandt API
Microsoft 365 Copilot cannot directly connect to APIs like Copilot Studio can

3. Power Platform (Connector-based)

Create one custom connector for Rembrandt API
Use it in: Power Automate, Power Apps, Logic Apps, AND Copilot Studio
If you already have a Power Platform connector, you can reuse it in Copilot Studio instead of creating REST API tools

Decision Flow

Want to use Rembrandt API in Copilot Studio?

✅ Use REST API tools (easiest, direct connection)
✅ OR use Power Platform connector (if you also need it in Power Automate/Apps)

Want to use Rembrandt API in Microsoft 365 Copilot?

✅ Create a Copilot Studio agent with REST API tools or Power Platform connector
✅ Make the agent available to your organization
✅ Users access it from Microsoft 365 Copilot

Want to use Rembrandt API in Power Automate/Apps?

✅ Create a Power Platform custom connector
✅ Use the same connector in Copilot Studio (if needed)

Note: The Rembrandt API provides OpenAPI v3.1.1. Microsoft Copilot Studio automatically converts this to v2.0. Power Platform may require manual conversion to v2.0 or enabling preview features for v3 support. Microsoft 365 Copilot supports v3 directly via plugin manifests.

For API documentation, see our API Integration Guide.

Prerequisites

A Rembrandt account with completed onboarding
Microsoft account with access to: Copilot Studio: Power Platform environment access Microsoft 365 Copilot: Microsoft 365 subscription with Copilot enabled Azure AI Studio: Azure subscription and Power Platform environment
Organization access in your Rembrandt account
An API key from Rembrandt (Settings → Service Accounts)

Microsoft Copilot Studio Integration

Add the Rembrandt API to your Copilot Studio agents so they can access your prospect data.

Prerequisites:

Access to Microsoft Copilot Studio
Rembrandt API key (see Step 1 below)

Step 1: Get Your API Key

API keys are created through Service Accounts:

Log in to your Rembrandt account
Navigate to Settings → Service Accounts
Create a Service Account (if you don't have one)
Click Create API Key in your service account
Enter a name for your API key (e.g., "Microsoft Copilot Studio")
⚠️ IMPORTANT: Copy the API key immediately - it starts with rk_ and is only shown once!
Save this key securely—you'll need it in the next step

Step 2: Open Your Agent in Copilot Studio

Go to Microsoft Copilot Studio
Sign in with your Microsoft account
In the left navigation pane, click Agents
Select the agent (custom or Microsoft-branded) you want to enhance
From the agent's Overview page, find the Tools section and click Add tool, OR go directly to the Tools tab and select Add a tool

Step 3: Add REST API Tool

In the dialog that appears, choose New tool
Select REST API as the tool type
You'll see options to import the Rembrandt API OpenAPI specification

Step 4: Import Rembrandt API OpenAPI Specification

Import the Rembrandt API OpenAPI spec: You have two options:
- Option A: Import from URL (Recommended) Enter the Rembrandt API OpenAPI specification URL: https://api.rembrandtagents.com/docs/json Click Import or Continue
- Option B: Upload file
  - Download the OpenAPI JSON from https://api.rembrandtagents.com/docs/json
  - Drag-and-drop the JSON file or browse to upload it
Note: The Rembrandt API OpenAPI specification (v3.1.1) will be automatically converted to v2.0 by Copilot Studio.
After importing, confirm the Rembrandt API endpoints appear correctly:
- GET /v1/prospects - Search and filter prospects
- GET /v1/prospects/:name - Get prospect details by company name
- GET /v1/prospects/by-id/:id - Get prospect details by ID
- GET /v1/domains - List all signal domains
Click Next to proceed

Step 5: Configure Description and Solution

Edit the description: This helps the agent decide when to call this tool. Make it clear and descriptive: Access prospect data and buying signals from Rembrandt. Use this tool to search for prospects, get prospect details, and retrieve signal domain information.
Choose a Solution: Select an existing solution or create a new one to contain this action. Solutions help with organizing and moving actions across environments
Click Next

Step 6: Configure Authentication

Choose your authentication method:

Option A: API Key Authentication (Recommended)

Authentication Type: Select API Key
Parameter Location: Choose Header
Parameter Name: Authorization
Parameter Label: Authorization (or leave default)
Click Next

Option B: OAuth 2.0 (if you prefer OAuth flow)

Authentication Type: Select OAuth 2.0
Provide: Client ID and Client Secret (if using OAuth) Authorization URL and Token URL Scopes (if required) Tenant restrictions (if applicable)
Click Next

Note: For Rembrandt API, use API Key authentication with the Bearer token format.

Step 7: Select Tools (Operations) from the API

After authentication configuration, Copilot Studio will display all endpoints and methods from the Rembrandt API OpenAPI specification:

Select which operations to include: You don't have to add every endpoint. Select only the ones you need:
- ✅ GET /v1/prospects - Search and filter prospects
- ✅ GET /v1/prospects/:name - Get prospect details by company name
- ✅ GET /v1/prospects/by-id/:id - Get prospect details by ID
- ✅ GET /v1/domains - List all signal domains
For each selected endpoint, configure:
- Tool name & description: Pre-populated from spec, but you can improve them
- Input/output parameters: Review and improve descriptions. Blank descriptions must be filled

Example descriptions to add:

For GET /v1/prospects:

Search and filter prospects based on urgency score, company name, domain, country, and buying journey phase. Use this to find prospects matching specific criteria. Sort by urgency score (highest first) unless specified otherwise.

For GET /v1/prospects/:name:

Get detailed information about a specific prospect or all prospects for a company. Use the company name (URL-encoded) as the path parameter. Optionally filter by domain and country to get a specific prospect.

Tip: Only select operations you need. Fewer tools = better precision and performance.

Step 8: Review and Publish the Tool

Review the configuration summary
If changes are needed, use Back to go to previous steps
Once satisfied, click Publish
After publishing, you'll be returned to the Add tool screen where you'll see the tools created from the Rembrandt API

Note: This publishes the REST API tool/action. You still need to publish the agent itself (see Step 11 below) to make it available for use.

Step 9: Connect Tools to the Agent

Now you need to create a connection for each tool:

On the Add tool screen, for each newly created tool:
- Select the tool
- Under Connection, either choose an existing connection or click Create new connection
- Fill in connection details: For API Key: Enter your Rembrandt API key: rk_your_api_key_here The system will automatically format it as Bearer rk_your_api_key_here in the Authorization header
- Click Add and configure
Once the tools are connected, they become available for use by the agent

Step 10: Enable Tools in Your Agent

Go to the Tools tab for your agent
You'll see your REST API tools listed
Use the toggles to enable or disable specific tools
Tools are now ready to be used in conversations

Using REST API Tools in Topics

To invoke these tools in conversation flows:

Go to the Topics page
Create or edit a topic
Add a node, choose Add a tool
Pick your REST API tool from the list
Map inputs/outputs as needed

Tip: Make sure descriptions are clear and descriptive—they help the orchestration decide when a tool should be used.

Step 11: Publish Your Agent

Once your agent is configured with Rembrandt API tools:

Go to your agent's Overview page
Click Publish (top right)
Choose who can access the agent: Only me - For testing purposes Anyone with a link - Share via link with specific users Your organization - Available to all users in your tenant (required for Microsoft 365 Copilot access)
Click Publish to make the agent live

After publishing:

The agent is immediately available for conversations in Copilot Studio
To make it available in Microsoft 365 Copilot, continue to Step 12

Step 12: Add Channels for Microsoft 365 Copilot

To make your agent available in Microsoft 365 Copilot (Teams, Outlook, Word, etc.):

In your agent, go to Channels (left navigation)
Click Add channel
Select Teams + Microsoft 365 Copilot
Configure channel settings: Icon and description - Customize how the agent appears Privacy statement - Add privacy information (optional) Allow users to add to team channels - Enable if you want users to add it to Teams channels
Click Save

Admin Approval (if required):

Some organizations require admin approval before agents appear in Microsoft 365 Copilot
Administrators review the agent in Microsoft Teams Admin Center or Microsoft 365 Admin Center
Once approved, the agent appears in the Agent Store ("Built for your org")

After adding channels:

The agent is available in Microsoft 365 Copilot (Teams, Outlook, Word, Excel, PowerPoint, etc.)
Users can access it by typing @YourAgentName in Microsoft 365 Copilot
Users can also find it in the Agent Store in Teams
When users ask questions, the agent uses the Rembrandt API (via REST API tools or connector) to answer

Microsoft 365 Copilot Integration

Important: Microsoft 365 Copilot cannot directly connect to APIs like Copilot Studio can. You need to use one of these approaches:

Option 1: Via Copilot Studio (Recommended - Easiest)

The easiest way to make Rembrandt API available in Microsoft 365 Copilot is to:

Create a Copilot Studio agent (see Microsoft Copilot Studio Integration section above)
- Add the Rembrandt API using REST API tools OR Power Platform custom connector
- Test the agent to ensure it works correctly
Publish the agent in Copilot Studio:
- Go to your agent's Overview page
- Click Publish (top right)
- Choose Your organization to make it available to all users
- Click Publish
Add channels for Microsoft 365 Copilot:
- Go to Channels in your agent
- Click Add channel → Select Teams + Microsoft 365 Copilot
- Configure settings and click Save
- Note: Admin approval may be required (see Step 12 in Copilot Studio section)
Users access the agent:
- Once published and channels added, users can access it from Teams, Outlook, Word, Excel, etc.
- In Teams, users type @YourAgentName or find it in the Agent Store
- When users ask questions, the agent uses the Rembrandt API to answer
- Responses come directly from your Rembrandt prospect data

Summary: You publish the agent once in Copilot Studio, then add the "Teams + Microsoft 365 Copilot" channel. No separate publishing step in Microsoft 365 Copilot needed.

This is the most common and user-friendly approach. The Copilot Studio agent acts as a bridge between Microsoft 365 Copilot and the Rembrandt API.

Option 2: Via Declarative Agents / Plugins (Enterprise)

For enterprise scenarios, you can create declarative agents using Microsoft 365 Agents Toolkit that reference the Rembrandt API.

Prerequisites:

Office/Teams Copilot access
Rembrandt API key (see Step 1 below)
Microsoft 365 Agents Toolkit
Appropriate permissions and tenant settings to upload custom Copilot agents/plugins

If you choose Option 1 (Recommended): Follow the steps in the Microsoft Copilot Studio Integration section above, then make your agent available to your organization.

If you choose Option 2 (Enterprise): Follow the steps below.

Step 1: Get Your API Key

Get your Rembrandt API key:

Step 2: Install Microsoft 365 Agents Toolkit

The Microsoft 365 Agents Toolkit simplifies plugin creation:

Install the toolkit in Visual Studio or VS Code: npm install -g @microsoft/365-agents-toolkit
Or use it directly: npx @microsoft/365-agents-toolkit

Step 3: Create Plugin Project

Option A: Using Agents Toolkit (Recommended)

Scaffold a new declarative agent: npx @microsoft/365-agents-toolkit create-plugin
Choose "Start with an existing API"
Provide the Rembrandt API OpenAPI spec URL: https://api.rembrandtagents.com/docs/json
Enter plugin name: rembrandt-plugin (or your preferred name)
The toolkit will generate the plugin manifest and project structure using the Rembrandt API specification

Option B: Manual Creation

Create a plugin manifest file (ai-plugin.json or manifest.json) that references the Rembrandt API, using schema version 2.4:

JSON

{
  "schema_version": "v2.4",
  "name_for_human": "Rembrandt API",
  "namespace": "Rembrandt",
  "description_for_human": "Access prospect data and buying signals from Rembrandt",
  "description_for_model": "Use this plugin when the user needs to search for prospects, get prospect details, or retrieve signal domain information from Rembrandt.",
  "logo_url": "https://rembrandtagents.com/logo.png",
  "contact_email": "support@rembrandtagents.com",
  "functions": [
    {
      "name": "getProspects",
      "description": "Search and filter prospects based on company name, domain, and country",
      "parameters": {
        "type": "object",
        "properties": {
          "companyName": {
            "type": "string",
            "description": "Company name to filter by"
          },
          "sortBy": {
            "type": "string",
            "description": "Sort field: lastActivity, companyName, signalCount"
          }
        }
      }
    },
    {
      "name": "getProspectByName",
      "description": "Get detailed information about a specific prospect or all prospects for a company",
      "parameters": {
        "type": "object",
        "properties": {
          "name": {
            "type": "string",
            "description": "Company name (URL-encoded)"
          }
        },
        "required": ["name"]
      }
    },
    {
      "name": "getDomains",
      "description": "List all available signal domains in the system"
    }
  ],
  "runtimes": [
    {
      "type": "OpenApi",
      "auth": {
        "type": "ApiKeyPluginVault",
        "reference_id": "rembrandt-api-key"
      },
      "run_for_functions": ["getProspects", "getProspectByName", "getDomains"],
      "spec": {
        "url": "https://api.rembrandtagents.com/docs/json"
      }
    }
  ],
  "capabilities": {
    "conversation_starters": [
      {
        "title": "Find High-Urgency Prospects",
        "text": "Show me prospects with the highest urgency"
      },
      {
        "title": "Search Prospects",
        "text": "Find prospects in the Netherlands"
      }
    ],
    "response_semantics": {
      "data_path": "$.data"
    }
  }
}

Step 4: Register API Key in Teams Developer Portal

For API Key authentication, you need to register it:

Go to Teams Developer Portal
Navigate to Tools → API key registration
Provide: Base URL: https://api.rembrandtagents.com Name: Rembrandt API Key Tenant scope: Your tenant or organization
Get the API key registration ID (you'll use this in the manifest)
Store your actual API key (rk_...) securely in the plugin vault

Step 5: Configure Authentication in Manifest

Update your manifest's runtimes section:

JSON

"runtimes": [
  {
    "type": "OpenApi",
    "auth": {
      "type": "ApiKeyPluginVault",
      "reference_id": "rembrandt-api-key-registration-id"
    },
    "spec": {
      "url": "https://api.rembrandtagents.com/docs/json"
    }
  }
]

The Rembrandt API OpenAPI specification already includes Bearer token security. Ensure your manifest references it correctly:

YAML

securitySchemes:
  BearerAuth:
    type: http
    scheme: bearer

Step 6: Package Plugin

Create a plugin package (ZIP file) containing:

Plugin manifest (ai-plugin.json or manifest.json) that references the Rembrandt API
Reference to the Rembrandt API OpenAPI specification URL (https://api.rembrandtagents.com/docs/json)
Any Adaptive Card templates (optional)
Logo image (optional)

Step 7: Deploy Plugin

For Local Testing:

Use Agents Toolkit's "Provision" and "Debug/Run" options
Plugin is sideloaded for your account in Teams/Copilot for testing

For Production:

Ensure the Rembrandt API endpoints are reachable (https://api.rembrandtagents.com)
Host your plugin manifest and assets (or use Azure hosting)
Ensure authentication is properly configured with your Rembrandt API key
Register the plugin in Microsoft 365 Copilot settings
Enable the plugin for your organization or specific users

Step 8: Test Plugin

Open Teams in browser
Open Copilot
Select your plugin/agent
Try invoking operations with natural language: "Show me prospects with high urgency" "Find prospects in the Netherlands" "Get all prospects for Microsoft" "Show me prospects with AI-related signals"
Verify responses and UI/templates work correctly
Confirm user consent dialogs appear when needed

Step 9: Enable for Organization

Ensure Copilot extensions/custom app upload is enabled in tenant settings
Ensure the user who deploys has appropriate privileges
Submit or enable the plugin so other users in the org can access it
Monitor usage and performance

Power Platform Custom Connector Integration

Create a custom connector for the Rembrandt API to use it across Power Platform tools: Power Automate, Power Apps, Logic Apps, and Copilot Studio.

Why use a connector instead of REST API tools in Copilot Studio?

You want to use the Rembrandt API in Power Automate flows or Power Apps
You want one connector that works across all Power Platform tools
You prefer managing connections in one place

If you only need Copilot Studio: REST API tools (see Microsoft Copilot Studio Integration section) are simpler and more direct.

Important: The Rembrandt API provides OpenAPI v3.1.1. Power Platform may require conversion to v2.0 or enabling preview features for v3 support (available from February 2026).

Step 1: Get Your API Key

Follow the same steps as above to get your Rembrandt API key.

Step 2: Create Custom Connector in Power Platform

In Power Apps:

Sign in to Power Apps
Select your environment (top right)
In the left navigation, expand Data
Click Custom connectors
Click New custom connector → Import an OpenAPI file

In Power Automate:

Sign in to Power Automate
Select your environment
In the left navigation, expand Data
Click Custom connectors
Click New custom connector → Import an OpenAPI file

Step 3: Import Rembrandt API OpenAPI Specification

Option A: Import from URL (Recommended)
- Select Import from URL
- Enter the Rembrandt API OpenAPI specification URL: https://api.rembrandtagents.com/docs/json
- Click Continue
Option B: Upload File
- Download the OpenAPI JSON from the Rembrandt API: https://api.rembrandtagents.com/docs/json
- Select Upload and choose the downloaded file
- Click Continue

Note: If you receive errors about OpenAPI version, the Rembrandt API's v3.1.1 spec may need conversion to v2.0, or try enabling preview features for v3 support.

Step 4: Configure General Information

Fill in connector details:

Connector name: Rembrandt API (or your preferred name)
Description: Access prospect data and buying signals from Rembrandt
Scheme: HTTPS
Host: api.rembrandtagents.com
Base URL: / (or leave default)
Click Continue

Step 5: Configure Security

Set up authentication:

For API Key Authentication:

Authentication type: Select API Key
Parameter label: Authorization
Parameter name: Authorization
Parameter location: Header
Click Continue

For Generic OAuth 2.0 (if preferred):

Authentication type: Select Generic OAuth 2.0
Configure: Client ID and Client Secret Authorization URL and Token URL Refresh URL (if applicable) Scopes (if required)
Click Continue

Note: Use API Key authentication for the Rembrandt API. Enter your Rembrandt API key when creating the connection.

Step 6: Review and Edit Actions (Definition Tab)

You'll see the Definition tab with imported Rembrandt API operations
Review the Rembrandt API operations:
- GET /v1/prospects - Search and filter prospects
- GET /v1/prospects/{name} - Get prospect details by company name
- GET /v1/prospects/by-id/{id} - Get prospect details by ID
- GET /v1/domains - List all signal domains
Edit operation summaries and descriptions:
- Click on each operation to edit
- Improve the Summary and Description fields
- Use OpenAPI extensions (x-ms-summary, x-ms-visibility) if modifying the OpenAPI file directly
Configure parameters:
- Review required vs optional parameters
- Edit parameter descriptions for clarity
- Set default values if needed
Click Create connector when done

Step 7: Test the Connector

Go to the Test tab
Click New connection
For API Key authentication:
- Enter your Rembrandt API key: rk_your_api_key_here
- Note: The connector will automatically format it as Bearer rk_your_api_key_here in the Authorization header
Click Create
Once connected, test operations: Test GET /v1/domains (no parameters required) - Click Test operation Test GET /v1/prospects with query parameters (e.g., country=US or companyName=Test)
Verify responses are correct
Check for any errors and adjust configuration if needed

Step 8: Use the Connector

Once tested and saved, use the connector across Power Platform:

Power Automate flows:
- Create a new flow
- Add an action, search for "Rembrandt API"
- Select the operation you want to use
Power Apps:
- Add a data source
- Select "Rembrandt API" connector
- Use in your app formulas
Logic Apps:
- Add a new action
- Select your custom connector
- Configure the operation
Copilot Studio (Alternative to REST API tools):
- Go to your agent → Tools
- Click Add tool
- Select Custom connector (instead of REST API)
- Choose your "Rembrandt API" connector
- Configure connection with your API key
- Use in topics just like REST API tools

Note: Using a Power Platform connector in Copilot Studio works the same as REST API tools, but allows you to reuse the same connector across all Power Platform tools.

Azure API Center Export to Copilot Studio

If you're using Azure API Center, you can export the Rembrandt API as a connector to Copilot Studio.

Prerequisites

Azure API Center instance
Rembrandt API registered in API Center (may need conversion to OpenAPI 2.0)
Power Platform environment
Microsoft Copilot Studio license

Step-by-Step Export

Prerequisites: First, you need to register the Rembrandt API in Azure API Center:

Go to Azure Portal and navigate to your Azure API Center
Register the Rembrandt API:
- Add a new API
- Import the Rembrandt API OpenAPI specification from https://api.rembrandtagents.com/docs/json
- Create a version and deployment pointing to https://api.rembrandtagents.com
- Important: Ensure the API definition is in OpenAPI 2.0 format (convert if needed)
Export to Copilot Studio:
- In the left-hand menu, select Copilot Studio (Preview)
- Click Create a connector
- In the dialog: Select the Power Platform environment you want to export to Enter the display name for your connector (e.g., "Rembrandt API") Choose the Rembrandt API, its version, and the deployment associated with that version The Host URL will auto-populate based on the runtime URL (https://api.rembrandtagents.com) Choose which API definition (OpenAPI 2.0) you want to use Optionally, if the API version has configured access settings, select from available security requirement types
- Click Create

Once created:

The connector becomes available inside Copilot Studio
You can test the connector in Power Automate or Power Apps
Then use it inside Copilot Studio to build agent flows

Important: The Rembrandt API provides OpenAPI v3.1.1, which may need conversion to v2.0 for Azure API Center export.

Using Rembrandt in Microsoft Tools

Once configured, you can use Rembrandt data in various ways:

In Copilot Studio Agents

Ask your agent questions like:

"Show me prospects with the highest urgency"
"Find prospects that are actively considering solutions"
"Show me prospects in the Netherlands"
"Find prospects with AI-related signals"
"Show me prospects from job postings"
"Get all prospects for Microsoft"
"Find prospects with high urgency in the last 30 days"

Your agent will use the Rembrandt API to answer these questions directly from your prospect data.

In Microsoft 365 Copilot

If you've set up the integration via Copilot Studio or declarative agents, users can use natural language prompts:

"What prospects do we have with urgency score 5?"
"Show me prospects in the buying phase"
"Find companies looking for supply chain solutions"

Note: If using Copilot Studio, users access the agent through Microsoft 365 Copilot, which then uses the Rembrandt API via the connectors/actions you configured.

In Power Automate / Logic Apps

Create automated workflows:

Daily prospect digest - Get high-urgency prospects daily
CRM sync - Sync prospect data to CRM systems
Alert workflows - Notify when new high-urgency prospects appear
Data enrichment - Enrich CRM records with Rembrandt prospect data

Troubleshooting

Integration Not Working

If Microsoft tools can't access Rembrandt data:

Verify your API key is correct and active (format: rk_*)
Check that the OpenAPI schema URL is accessible: https://api.rembrandtagents.com/docs/json
Ensure your Rembrandt account setup is complete (email verified, organization selected, profile completed)
Try regenerating your API key
For Copilot Studio, ensure the REST API tool is properly connected
For Power Platform, verify the custom connector connection is saved with credentials

OpenAPI Version Issues

Problem: The Rembrandt API provides OpenAPI v3.1.1, but some Microsoft tools may require v2.0.

Solutions:

Microsoft Copilot Studio: Automatically converts the Rembrandt API's v3.1.1 spec to v2.0 (no action needed)
Power Platform: May require manual conversion to v2.0, or enable preview features for v3 support
Microsoft 365 Copilot: Supports the Rembrandt API's v3.1.1 spec directly via plugin manifest (no conversion needed)
Conversion tools: If manual conversion is needed, use online converters or tools like swagger2openapi

Authorization Failed

If you see authorization errors:

Make sure you're using the correct API key format (Bearer rk_...)
Verify your key hasn't expired
Check that your account has access to the organization data you're querying
Ensure the API key was created through Service Accounts
For Power Platform, ensure the connection is properly saved with credentials
For Copilot Studio, verify the connection was created successfully in the tool configuration

Operations Not Available

If operations don't appear:

Verify the OpenAPI spec URL is accessible: https://api.rembrandtagents.com/docs/json
Check that the spec was imported correctly
Ensure you have permissions to use the connector
Try re-importing the OpenAPI specification

API Rate Limits

If you encounter rate limit errors:

Rembrandt API has rate limits: 1,000 requests/hour per API key (regular), 2,000/hour (burst)
Try spacing out your requests
Check rate limit headers in responses: X-RateLimit-Remaining-Key
Contact support if you need higher limits

Schema Out of Date / Endpoints Not Found

Important: Microsoft tools may cache the OpenAPI schema. If the Rembrandt API has been updated with new endpoints, you need to manually refresh the schema.

To refresh your schema:

Copilot Studio:
- Go to your agent → Tools
- Select the REST API tool → Edit
- Re-import the OpenAPI spec from URL: https://api.rembrandtagents.com/docs/json
- Click Update
Power Platform:
- Go to Custom connectors
- Select your Rembrandt connector → Edit
- Re-import the OpenAPI specification
- Save and test
Microsoft 365 Copilot:
- Redeploy the plugin with updated schema
- Ensure the manifest references the latest OpenAPI spec URL

This ensures your integrations use the latest Rembrandt API endpoints and features.

Security & Permissions

The Microsoft integrations use your API key to:

Read your organization's buying signals
Access prospect information
Retrieve signal domain data

Your API key provides read-only access to your organization's data. Keep your key secure and don't share it publicly.

Security Best Practices:

Never commit API keys to version control
Use different keys for different environments
Rotate keys regularly
Revoke keys immediately if compromised
Use Microsoft Entra ID (Azure AD) authentication when possible for enterprise scenarios
Review connector permissions in Power Platform

Consent Dialogs:

Microsoft 365 Copilot shows consent dialogs for the Rembrandt API plugin:

"Allow once" - For read-only operations (all Rembrandt API operations are read-only)

Limitations & Considerations

Rembrandt API OpenAPI Version Support

The Rembrandt API provides OpenAPI v3.1.1:

Copilot Studio: Automatically converts to v2.0 (no action needed)
Power Platform: May require conversion to v2.0 or enabling preview features for v3 support
Microsoft 365 Copilot: Supports v3.1.1 directly via plugin manifest
Azure API Center Export: May require conversion to v2.0

Size Constraints

The Rembrandt API OpenAPI specification is under the size limits
All Rembrandt API endpoints are available for integration

Disconnecting Integrations

Copilot Studio

Go to your agent → Tools
Remove or disable the REST API tool
Optionally revoke your API key in Rembrandt

Microsoft 365 Copilot

Go to Copilot settings → Plugins
Disable or remove the Rembrandt plugin
Optionally revoke your API key in Rembrandt

Power Platform

Go to Custom connectors
Delete or disable the Rembrandt connector
Remove connections using the connector
Optionally revoke your API key in Rembrandt

Need Help?

If you encounter issues connecting or using Microsoft integrations:

Check our Troubleshooting Guide
Review the API Integration Guide for general API information
Microsoft Documentation: Copilot Studio REST API Tools Microsoft 365 Copilot Plugins Power Platform Custom Connectors
Contact support at support@rembrandtagents.com