Your ecommerce data,
inside Microsoft Copilot.
Connect PayHelm to Microsoft 365 Copilot via a Copilot Studio agent. Ask about revenue, margin, ad performance, and inventory in Word, Excel, Outlook, or Copilot Chat — grounded in your live data.
Why connect PayHelm to Copilot
Copilot already lives in the tools your team uses all day. PayHelm makes it fluent in your business.
Ask business questions in plain English
Type @PayHelm in any Copilot chat — Word, Excel, Outlook, or Microsoft 365 Copilot Chat — and get revenue, margin, and ad performance without switching tools.
Ad performance & recommendations
Query Google Ads and Meta campaign performance and get AI-driven scale/pause recommendations, grounded in your live spend and ROAS data.
Grounded, not generic
Every answer is grounded in your actual PayHelm data via MCP — not a generic LLM guess. Numbers match what's in your PayHelm dashboard.
Drop straight into Office documents
Ask Copilot in Word to draft a board summary or in Excel to build a P&L — PayHelm's live numbers flow directly into the document you're already writing.
Inventory & anomaly awareness
Ask which SKUs are at risk of stocking out, or which campaigns just dropped in ROAS — PayHelm surfaces the answer with the underlying numbers.
Runs inside your Microsoft tenant
Deployed as a Copilot Studio agent inside your own Microsoft 365 environment — your IT team controls who gets access and what data it can see.
Connect PayHelm to Microsoft Copilot
The straightforward route is to connect PayHelm's MCP server to a Copilot Studio agent, then publish that agent to Copilot. You don't need an existing Teams app for this.
Check the endpoint first: Microsoft Copilot Studio requires Streamable HTTP and no longer supports the older SSE transport. PayHelm's MCP endpoint (https://mcp.payhelm.com/mcp) supports Streamable HTTP natively, so this works out of the box.
Create an agent in Copilot Studio
Open Microsoft Copilot Studio and create (or open) an agent — name it "PayHelm".
Add PayHelm as a tool
Go to Tools → Add a tool → New tool → Model Context Protocol.
Enter PayHelm's MCP server details
Enter a server name, a short description of its reporting capabilities, and PayHelm's MCP server URL: https://mcp.payhelm.com/mcp
Configure authentication
Choose API key and paste your PayHelm API key (found in PayHelm → Settings → API Keys), or configure OAuth 2.0 if your organization requires it.
Create the connection
Select Create, establish the connection, then Add to agent. Copilot Studio requires Streamable HTTP — PayHelm’s MCP endpoint supports this natively.
Test it
Ask the agent a real question — "What were our sales last month?" — and confirm it returns live PayHelm numbers.
Publish the agent
Once you're happy with the responses, select Publish in Copilot Studio.
Make it available in Microsoft 365 Copilot
Open Channels → Teams and Microsoft 365 Copilot, select Make agent available in Microsoft 365 Copilot, then Add channel.
Roll it out to your team
Install it for testing, share it with authorized users, or submit it for organization-wide admin approval.
Start asking questions
Employees select the PayHelm agent in Copilot, or invoke it directly with "@PayHelm", to get live ecommerce answers.
This gives your team a PayHelm-connected agent inside Copilot — it doesn't automatically expose PayHelm data to every Copilot conversation, only to this agent. Your Microsoft 365 admin controls who can install and use it.
Built on open standards
Want a hand connecting it?
Leave your email and we'll send you a step-by-step setup walkthrough for your Microsoft 365 tenant.
No spam. One email with the setup guide.