Connecting Workable to Microsoft Copilot Studio

Check the full setup guide here.

Connect Workable to a Microsoft Copilot Studio agent to find recruiting and HR information and take actions in your Workable account through conversation. The Workable Model Context Protocol (MCP) server gives your agent access to tools for jobs, candidates, employees, requisitions, offers, time off and more.

This guide covers the recommended setup using the certified Workable MCP connector and an alternative manual setup.

Before you start

To set up the connection, you need:

An active Workable account and a user with access to the information and actions the agent will use.
A Microsoft Copilot Studio license and permission to create agents and connections in your Power Platform environment.
For the certified connector, a license that covers Premium connectors and an environment whose connector policies allow Workable MCP.
For manual setup, permission to add custom or third-party MCP servers.
A browser that allows the Workable sign-in pop-up window.

The MCP server is available on all Workable subscription tiers. HR tools, such as employees, time off, time tracking and performance reviews, require the corresponding Workable products to be enabled on your account.

The certified connector is currently in Preview. It is available in commercial regions, excluding GCC, GCC High, US Department of Defense (DoD) and China operated by 21Vianet.

The agent's access depends on the signed-in user's Workable permissions. It cannot access information or perform actions that the user cannot access or perform in Workable.

Setting up the connection

Using the certified connector (recommended)

Open Microsoft Copilot Studio, select your environment and create an agent or open an existing one.
On the Build tab, select the + next to Tools.
In Add a tool, search for Workable and select the MCP filter.
Select Workable MCP, then + Add.
Create a connection if prompted. You can name it Workable.
In the Workable authorization window, sign in, review the requested permissions and approve the connection.

No server URL, API key, client ID or client secret is required for this setup.

Choose Workable MCP rather than Workable (Independent Publisher). The latter is a separate community connector that uses an API key.

Once the tool appears under Tools, open it to review its settings:

Connection: Check that Workable has a green check mark. Use Manage connections if you need to switch or repair the connection
Authentication: Select End user account so each person using the agent signs in with their own Workable account
Tool permissions: Keep Allow all enabled to allow all available Workable tools, or turn it off and enable individual tools. For an agent that should only retrieve information, select the relevant read-only tools

Select Done. If you previously added Workable manually, remove the duplicate tool so the agent has one Workable connection.

Adding the MCP server manually

Use this alternative if the certified connector is unavailable and your organization permits custom MCP servers.

Open your agent, select the + next to Tools and open the Model Context Protocol (MCP) tab.
Select + Add to open the Add MCP server form.
Enter Workable MCP as the server name.
Enter a description, such as: “Connect to Workable to find jobs, candidates and employees and manage recruiting and HR tasks.”
Enter https://mcp.workable.com/mcp as the server URL.
Select OAuth 2.0 for authentication, then Dynamic (with discovery) for the configuration type. The configuration type appears after you choose OAuth authentication.
Select Add.
Under Select a connection, open the connection dropdown and create a new connection. Name it Workable and select Create.
Sign in to Workable in the authorization window, review the requested permissions and approve the connection.
When Workable shows a green check mark, select Add to attach the server to your agent. Remove any duplicate Workable tools.

You do not need to enter a client ID or client secret when using dynamic discovery.

Publishing and testing your agent

Whichever setup option you use, add the following text to your agent's Instructions:

When using Workable tools, call get_accounts first and use the subdomain of your account as the `account` argument on every subsequent call.

This lets the agent identify the Workable accounts you can access and use the appropriate account for subsequent requests.

Select Publish, then confirm Save and publish.
Open the agent's chat pane or Preview tab.
Ask: “Which are the open jobs in my account?”
Expand the agent's trace and check that it calls get_accounts followed by get_jobs, then returns information from your Workable account.

Once connected, you can also try questions such as:

“Which candidates applied for the Senior Backend Engineer role this week, and where are they in the pipeline?”
“Show me the requisitions waiting on my approval.”
“Who is out of office in the Berlin office next month?”

The available tools and results depend on your permissions, the products enabled on your Workable account and the tool permissions configured for the agent.

Troubleshooting the connection

Workable MCP does not appear in the catalogue: Ask your Power Platform administrator to check your environment's region, Premium connector licensing and connector policies. If custom MCP servers are permitted, you can use the manual setup above.

The Workable sign-in window does not open: Allow pop-ups for copilotstudio.microsoft.com and try creating the connection again.

A redirect URI mismatch appears during manual setup: Contact Workable Support with the redirect URI shown in the error so it can be reviewed for allow-listing. Alternatively, use the certified connector if it is available.

The agent uses duplicate Workable tools: Check whether both the certified connector and a manually registered Workable server are attached. Remove the duplicate tool.

A Workable tool returns an error

401 Unauthorized: Sign in again to refresh the connection
403 Forbidden: Check the signed-in user's Workable permissions and that the required product is enabled
404 Not found: Check the account subdomain and that the requested record is visible in that account
409 Conflict: Check the record's current state before trying the action again
422 Unprocessable: Check the supplied values, using stages and other options from your Workable account
429 Rate limited: Wait briefly and try again