Integration API Keys
Every AccessEXL workbook has its own API key (find or create one from that workbook's settings icon on your dashboard). This page covers exactly where that key goes for each supported platform. For everything else — API behaviour, limits, billing, security, and how to configure a workbook — ask the .
Claude
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.
- In Claude, open Settings → Customize → Connectors and choose Browse connectors. Team/Enterprise plan: an owner first adds it for the organisation from Organization settings → Connectors → Browse connectors.
- Search for AccessEXL, choose the connector named AccessEXL (not AccessEXL Agent, which is for published capabilities) and click Connect.
- 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, connected.
- Test it out by going to a new chat and asking Claude a question about your workbook, for example "Tell me the schema of my connected AccessEXL workbook".
Connecting more than one workbook?
The AccessEXL connector from Claude's directory connects one workbook. Add each further workbook as a custom connector with its own name and URL:
- Team/Enterprise plan: Organization settings → Connectors → Add → Custom (choose Web if asked for a type). Free/Pro/Max plan: Settings → Customize → Connectors → Add custom connector.
- Enter the Connector name and unique URL for your workbook, as per its Settings page, then click Continue.
- Set Authentication to Sign in now, and set the OAuth client to Use Claude's published identity. These should be the defaults. Click Add, then close the Connector Details box.
- Find the new connector in Claude's list of connectors (you may need to close and go back to Settings → Customize → Connectors), click Connect and paste that workbook's API key on the AccessEXL page.
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. It respects SharePoint permissions: your organisation can choose that people only find and run a capability if they can open its workbook in SharePoint themselves (checked with their own Microsoft sign-in). A workbook needs a published capability first; publish one from its settings on your dashboard.
- In Claude, open Settings → Customize → Connectors and choose Browse connectors. Team/Enterprise plan: an owner first adds it for the organisation from Organization settings → Connectors → Browse connectors.
- Search for AccessEXL, choose AccessEXL Agent and click Connect.
- On the AccessEXL page that opens, click Continue with AccessEXL, sign in if asked, and choose Allow. Nothing to copy or paste: AccessEXL creates your personal access token for you and sends you back to Claude, connected. (Already have a token? Use Use an existing access token instead on that page.)
- Test it in a new chat, for example "What AccessEXL capabilities can you use?"
Can't find it in Claude's directory?
Add it as a custom connector instead:
- Team/Enterprise plan: Organization settings → Connectors → Add → Custom (choose Web if asked for a type). Free/Pro/Max plan: Settings → Customize → Connectors → Add custom connector.
- Give your connector the name AccessEXL capabilities, then enter the URL:
https://mcp.accessanalytic.com.au/mcpand click Continue. - Set Authentication to Sign in now, and set the OAuth client to Use Claude's published identity. These should be the defaults. Click Add, then Connect if Claude asks, and carry on from step 3 above.
Ask the for how each process behaves in more detail.
Microsoft Copilot
As with Claude, there are two ways to connect Microsoft Copilot, depending on what you want it to do.
Published capabilities (all workbooks): the AccessEXL Agent
The AccessEXL Agent for Microsoft 365 Copilot reaches every capability your organisation has published and shared with you, across all your workbooks. Each person signs in with their own AccessEXL account and only sees the capabilities shared with them, with the same SharePoint access rules as in Claude.
- Open Microsoft 365 Copilot in Teams (the first sign-in works most reliably there; after that the agent also works in Copilot on the web, Outlook, Word, Excel and PowerPoint).
- Choose Agents → Get agents, search for AccessEXL, choose AccessEXL Agent and click Add.
- Open the agent and ask, for example, "What AccessEXL capabilities do I have access to?" Choose Sign in when Copilot asks.
- On the AccessEXL page that opens, click Continue with AccessEXL, sign in if asked, and choose Allow. Nothing to copy or paste. Microsoft's sign-in link lasts 5 minutes, so ask again if it has expired.
- Copilot asks you to confirm before it runs a capability. Running one never changes your workbook.
You need a Microsoft 365 Copilot licence and an AccessEXL account in an organisation that has shared capabilities with you. In Word, Excel and PowerPoint, open the agent from the menu in the Copilot pane.
Can't find AccessEXL Agent in Copilot?
Your Microsoft 365 admin may need to make it available first: in the Microsoft 365 admin centre, open Agents → All agents, find AccessEXL Agent and deploy it to the people who need it. Some organisations only allow agents an admin has approved.
Building your own agent in Copilot Studio instead?
- Create an Agent Access Token on the Agent Access Tokens page.
- In Copilot Studio, open the agent, then Tools → Add a tool → New tool → Model Context Protocol, with the server URL
https://mcp.accessanalytic.com.au/mcp - Set Authentication to API key, Type Header, and header name
X-Agent-Token. - Create and add it to the agent, entering the Agent Access Token from step 1 as the value.
An Agent Access Token is personal. If several people will use the agent, set the tool to use each person's own credentials so everyone enters their own token and sees only the capabilities shared with them. Otherwise everyone who uses the agent gets the builder's access.
One workbook (Copilot Studio)
Give a Copilot Studio agent one workbook as a tool, signed in with that workbook's own API key. This suits a Copilot agent built for one model, or someone outside your organisation who was sent a key.
- In Copilot Studio, open (or create) an agent, then Tools → Add a tool → New tool → Model Context Protocol.
- Enter a server name and description, and the server URL:
https://wkb.accessanalytic.com.au/mcp - Set Authentication to API key, Type Header, and header name
X-Api-Key. - Select Create, then add it to the agent. When asked to create the connection, enter the workbook's API key as the value.
- Try it in the test pane, for example "What inputs does this model take?", then choose Publish and add the Teams and Microsoft 365 Copilot channel to use it in Copilot and Teams.
Using the agent in Microsoft 365 Copilot needs a Microsoft 365 Copilot licence. Your organisation's Power Platform data policy can restrict which MCP servers are usable; if the tool isn't offered, check with whoever manages that policy.
Ask the for how each process behaves in more detail.
Zapier
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.
- In Zapier, search for and add the AccessEXL app to your Zap.
- 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/refreshbefore accepting the connection, so a mistyped key is caught immediately. - 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 (enter0.05for 5%). - 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 for how the integration behaves in more detail.
Make.com
Make.com uses the workbook's API key as a plain header credential — no OAuth needed.
Recommended: the AccessEXL app
- In your Make scenario, add an AccessEXL module (for example Run a Scenario).
- In Connection, click Add and enter your workbook's API key, then save. One connection is one workbook; add another connection for another workbook.
- 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:
- In your Make scenario, add an HTTP module (the http app's Make a request action).
- 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
- Point the URL at one of:
https://api.accessanalytic.com.au/schema(GET): list writable/readable rangeshttps://api.accessanalytic.com.au/run-scenario(POST, JSON body{"values": {...}}): write inputs, recalculate, read outputs backhttps://api.accessanalytic.com.au/outputs(GET): read current outputs
Ask the for endpoint behaviour.
Power Automate
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.)
- Download the AccessEXL Demo Solution from the Downloads page (sign-in required).
- In Power Automate, go to Solutions → Import solution.
- Upload the ZIP file.
- Connect your Office 365 Outlook account when prompted.
- Enter your AccessEXL Workbook Key.
- Enter the email address where you want the results sent.
- Complete the import.
- Open AccessEXL Demo Quick Start and select Run.
- 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 for the full walkthrough.
n8n
AccessEXL node (one workbook)
The AccessEXL node, n8n-nodes-accessexl, runs scenarios, updates inputs, reads outputs and reads or writes table rows, with input and column fields taken from your workbook's own configuration. It can also be used as a tool by an n8n AI Agent. It is a verified n8n node, available now on n8n Cloud.
- In a workflow, open the nodes panel (+), search for AccessEXL and add it to your workflow. On self-hosted n8n you can also go to Settings → Community nodes → Install and enter
n8n-nodes-accessexl. - Add an AccessEXL node, create an AccessEXL API credential and paste your workbook's API key. One credential is one workbook.
- Choose an action, for example Run a scenario or Add a table row.
Published capabilities (all workbooks)
An n8n AI Agent can discover and run every capability your organisation has published and shared with you, through n8n's built-in MCP Client Tool. Agent capabilities are available on Business accounts.
- Generate an Agent Access Token from your dashboard's Agent Access Tokens page.
- On an AI Agent node, add a Tool and choose MCP Client Tool.
- Set Endpoint to
https://mcp.accessanalytic.com.au/mcp, Server Transport to HTTP Streamable and Authentication to Bearer Auth, with the Agent Access Token as the token. - Leave Tools to Include as All. The agent searches the capabilities, reads the one it needs and runs it.
HTTP Request node
- Add an HTTP Request node.
- Under Authentication, choose Generic Credential Type → Header Auth, then create a credential with Name
X-Api-Keyand Value set to your workbook's API key. - Set Method and URL to one of the endpoints listed under Make.com above.
- For POST endpoints, set the node's Body (JSON) to
{"values": {...}}.
Ask the for more detail.
Not sure which platform fits what you're building? Ask the for an overview, or contact us.