Perplexity
Coming soonNot available yet. This page describes a feature we are still building, so it is not in your dashboard today. Everything below is what it will do when it ships.
Connect Botvee as a custom remote connector in Perplexity. The connector gives Perplexity live, permission-checked Botvee tools for conversations and Computer workflows.
Before you start
- A Botvee account with access to the workspace you want to manage
- A Perplexity Pro, Max, or Enterprise plan that includes custom remote connectors
- On Enterprise, permission from an administrator to add or use custom connectors
Botvee connection URL
Use this exact URL when Perplexity asks for the remote MCP server:
https://api.botvee.ai/mcpHow to connect Perplexity
- 1
Open Connectors
In Perplexity, open Account settings, then Connectors. Enterprise administrators can use Enterprise settings and Connector permissions
- 2
Add a custom connector
Click Custom connector, choose Remote, and enter Botvee as the name
- 3
Enter the endpoint
Paste the Botvee MCP server URL shown above
- 4
Choose OAuth
Select OAuth authentication and continue; Botvee supports automatic public-client registration and does not use an API key
- 5
Approve access
Sign in to Botvee, review the account and permissions, then click Allow access
- 6
Use it
Enable or mention Botvee in a conversation or Computer workflow and first ask which Botvee account is connected
What Perplexity can do
| Area | Available actions |
|---|---|
| AI agents | Review, create, and edit accessible agents |
| Inbox | Read conversations and waiting counts |
| Support tickets | Review, create, claim, update, and assign tickets |
| Read received email and create unsent drafts | |
| Bookings | Review and edit bookings |
| Leads | Review and add leads |
| Ecommerce | Review products, orders, COD and recovery activity, alerts, and feature status |
Security and confirmation
- OAuth tokens are scoped to Botvee and never reveal the user’s password
- Current role, workspace, agent assignments, and section permissions are checked on every call
- Read operations can run without changing records
- Before a write, Perplexity must show the exact proposed change and wait for explicit approval
- Botvee records the connector, user, tool, result, and duration in the MCP audit log
Prompts to test
Which Botvee account is connected?
Show my AI agents, waiting inbox count, and latest unassigned support tickets. Do not change anything.
Prepare one safe test change, show the exact before and after values, and wait for my explicit confirmation before using a write tool.Disconnecting
Remove Botvee from Perplexity Connectors when it is no longer needed. Botvee’s OAuth revocation endpoint invalidates the connection tokens; reconnecting requires sign-in and approval again.
Troubleshooting
- Custom connector is missing: Check that the Perplexity plan and organization policy allow custom remote connectors
- Perplexity asks for an API key: Change authentication to OAuth
- Botvee tools do not appear: Remove and recreate the connector so Perplexity performs fresh tool discovery
- A tool is refused: The connected Botvee role, assignment, plan, or workspace state does not permit that action
Can’t find what you are looking for? Contact support
