Integration API Keys

There are two different ways to connect Claude, providing different functionality. Both are AccessEXL's own MCP servers — pick whichever matches what you want Claude to do.

One workbook

Connects a single workbook directly. Claude can read that workbook's schema, run scenarios, and read outputs — the same as calling the REST API directly, just from a conversation.

1. Team/Enterprise plan: Organization settings → Connectors → Add → Custom (choose Web if asked for a type). Free/Pro/Max plan: Customize → Connectors → Add custom connector.
2. Enter the Connector name and unique URL for your workbook, as per its Settings page, then click Continue.
3. Set Authentication to Sign in now, and set the OAuth client to Use Claude's published identity. These should be the defaults. Click Add and Claude should report that the connector was added successfully. Close the Connector Details box.
4. You should now see your new connector near the bottom of Claude's list of connectors (you may have multiple pages).
5. Depending on your settings, you might now need to close, then go back to settings and click Connect, and enter your workbook's key. You'll be redirected to a page here on AccessEXL. Paste in the workbook's API key and submit (it's checked live, so a mistyped key is caught immediately). You'll then be sent back to Claude.ai, connected.
6. Test it out by going to a new chat and asking Claude a question about your workbook.

A client without OAuth support can instead send the key directly: header Authorization: Bearer <the workbook's API key> (or X-Api-Key to just the key).

Published capabilities (all workbooks)

Connects Claude to every governed capability your organisation has published and shared with you, across all your workbooks at once — Claude discovers and runs the right one on its own, rather than you naming a specific workbook. A workbook needs a published capability first; publish one from its settings on your dashboard.

1. Generate an Agent Access Token from your dashboard's Agent Access Tokens page — a personal credential, separate from any workbook's own API key.
2. In Claude.ai, add another custom connector using this URL instead: https://mcp.accessanalytic.com.au/mcp
3. Set Authentication to OAuth, leave Client ID/Secret blank, and click Connect.
4. You'll be redirected to a page on AccessEXL — paste in the Agent Access Token from step 1 (not a workbook API key) and submit.

Ask the Help assistant for how each process behaves in more detail.

AccessEXL connects to Microsoft Copilot through Copilot Studio's Model Context Protocol (MCP) support — set up by whoever administers Copilot Studio for your organisation's Microsoft 365 tenant, not by an individual end user. As with Claude, there are two separate MCP servers depending on what you want Copilot to do, and unlike Claude, no OAuth setup is needed — just a header and an API key.

One workbook

1. In Copilot Studio, open the agent, then Tools → Add a tool → New tool → Model Context Protocol.
2. Enter a server name and description, and the server URL: https://wkb.accessanalytic.com.au/mcp
3. Set Authentication to API key, Type Header, and header name X-Api-Key.
4. Select Create, then add it to the agent. Whoever is prompted to create the connection enters the workbook's own API key as the value.

Published capabilities (all workbooks)

1. Generate an Agent Access Token from your dashboard's Agent Access Tokens page.
2. Add another MCP tool in Copilot Studio pointed at https://mcp.accessanalytic.com.au/mcp.
3. Set Authentication to API key, Type Header, and header name X-Agent-Token.
4. Create and add it to the agent, entering the Agent Access Token from step 1 as the value.

Your organisation's Power Platform data-loss-prevention policy can restrict which connectors and MCP servers are usable in your tenant — if the tool doesn't appear as an option, check with whoever manages that policy.

Ask the Help assistant for how each process behaves in more detail.

AccessEXL has a native Zapier integration — currently a private integration (available by invitation/private access, not yet listed in Zapier's public App Directory), built around one action, Run a Scenario.

1. In Zapier, search for and add the AccessEXL app to your Zap.
2. Choose the Run a Scenario action, then create a new connection: paste your workbook's API key when prompted. Zapier checks it live against POST /schema/refresh before accepting the connection, so a mistyped key is caught immediately.
3. Once connected, Zapier loads that workbook's inputs and outputs directly from GET /schema — fields use each range's friendly display name where one is configured, ranges with allowed values appear as dropdowns, and percentage fields take a decimal (enter 0.05 for 5%).
4. Map your Zap's data into those fields and continue building as normal.

One Zapier connection represents one workbook. To use a different workbook, add another connection with that workbook's own key. Ask the Help assistant for how the integration behaves in more detail.

Make.com uses the workbook's API key as a plain header credential — no OAuth needed.

Recommended: the AccessEXL app

1. In your Make scenario, add an AccessEXL module (for example Run a Scenario).
2. In Connection, click Add and enter your workbook's API key, then save. One connection is one workbook; add another connection for another workbook.
3. Pick the module you need (read the schema, run a scenario, update inputs, get outputs, and read or write table rows). See the Make.com module reference for every module, mapping examples and troubleshooting.

Or: a generic HTTP module

If the AccessEXL app is not in your Make account, or you want to call the REST API directly, use Make's HTTP module:

1. In your Make scenario, add an HTTP module (the http app's Make a request action).
2. Set Authentication type to API key, and create a key with:
   • Placement: In the request header
   • Parameter name: X-Api-Key
   • Value: your workbook's API key
3. Point the URL at one of:
   • https://api.accessanalytic.com.au/schema (GET): list writable/readable ranges
   • https://api.accessanalytic.com.au/run-scenario (POST, JSON body {"values": {...}}): write inputs, recalculate, read outputs back
   • https://api.accessanalytic.com.au/outputs (GET): read current outputs

Ask the Help assistant for endpoint behaviour.

Premium Power Automate subscription required. AccessEXL currently uses Power Automate's generic HTTP connector, which is a Premium Power Automate feature. If you don't have a Premium subscription, you won't be able to use AccessEXL with Power Automate. You may want to consider Make.com or n8n instead.

Before you start: you need the AccessEXL demo financial model uploaded to your own SharePoint site, and an AccessEXL workbook key created for that file. (The example workbook is on the Quick start page.)

1. Download the AccessEXL Demo Solution from the Downloads page (sign-in required).
2. In Power Automate, go to Solutions → Import solution.
3. Upload the ZIP file.
4. Connect your Office 365 Outlook account when prompted.
5. Enter your AccessEXL Workbook Key.
6. Enter the email address where you want the results sent.
7. Complete the import.
8. Open AccessEXL Demo Quick Start and select Run.
9. Enter the scenario assumptions and run the flow.

AccessEXL sends those values into the Excel model, recalculates it, retrieves the outputs and emails you the results.

Your credentials are not included in the demo. The imported solution uses your own Outlook connection and your own AccessEXL workbook key.

Prefer to build your own flow? Call the API directly with a generic HTTP action (a Premium connector): set Method to GET or POST, add header X-Api-Key set to the workbook's API key, set Body to JSON {"values": {...}} for POST endpoints, and set the URI to one of the endpoints listed under Make.com above.

Ask the Help assistant for the full walkthrough.

1. Add an HTTP Request node.
2. Under Authentication, choose Generic Credential Type → Header Auth, then create a credential with Name X-Api-Key and Value set to your workbook's API key.
3. Set Method and URL to one of the endpoints listed under Make.com above.
4. For POST endpoints, set the node's Body (JSON) to {"values": {...}}.

Ask the Help assistant for more detail.