Is infioo a built-in Perplexity connector?

No. Perplexity curates its own connector list and takes proposals from companies through a form; infioo isn't on it, so you add it as a custom connector by URL. A listing wouldn't change the connection: same sign-in, same permissions, same tools.

Do I need an API key?

No. Perplexity's custom connectors support sign-in; a key is only a fallback, and a weaker one.

What can it do with my infioo account?

Thirteen read tools covering the daily brief, contacts, conversations, schedule, invoices, tasks and the knowledge base, plus five writes: create a task, create a contact, tag a contact, draft a reply, mark an appointment complete. Marking an appointment complete can't be undone, and it can start your usual thank-you and review request under your own approval settings, just as it does in the app.

Can it text my customers or send an invoice?

Not directly. Sending a message, and anything that creates, sends or syncs an invoice, is not exposed to any chat connector. A drafted reply waits in your inbox behind the Approve button. Marking an appointment complete can start your reviews agent's usual thank-you and review request, which follows your own approval settings.

Can I try it before signing up for infioo?

Yes. Use https://infioo.ai/api/mcp/demo instead - no account, no email, read-only, a fictional plumbing business.

Does the server have to be publicly reachable?

It already is. A connector backend reaches infioo.ai over the public internet rather than from your device, and infioo.ai is hosted - no tunnel, nothing to self-host.

How do I disconnect it?

Revoke it in infioo under Settings -> Connections -> Connected assistants; it stops working on its next request. Removing the connector in Perplexity stops Perplexity using it but may not tell infioo, so revoke it in infioo too.

INFIOO in Perplexity: Connect Your CRM as a Custom MCP Connector

One server, and your own books behind it

Perplexity is where a lot of owners already ask questions. The gap has always been that it could answer about the world and not about your world - what is booked, who is late, what a customer said last Tuesday.

A custom MCP connector closes that. We did not write a Perplexity integration; we wrote one standards-compliant MCP server and let any client that speaks the protocol come and get it.

"What needs me today?"Late money, unanswered messages, the jobs actually on today.

"Who owes me, and how long?"Oldest first, with amounts, straight off the ledger.

"Catch me up on the Whitmore job."Conversation, appointments and invoice in one answer.

"Task: order the flange before Friday."A real task in the real CRM, not a line in a chat you will lose.

How to connect it: six steps

Needs Perplexity Pro, Max or Enterprise - not the free plan. Plans move, so Perplexity's help centre has the current rule. On Enterprise, an admin decides whether members may add their own connectors.

Copy this URL:

https://infioo.ai/api/mcp

In Perplexity on the web, open account settings -> Connectors -> + Custom connector, then Remote.
Name it INFIOO and paste the URL.
Set authentication to OAuth. Leave client ID and secret empty - Perplexity registers itself.
Set transport to Streamable HTTP, not SSE - infioo has no SSE endpoint.
Tick the acknowledgement box and click Add, then click the connector card to sign in to infioo, choose which business and which permissions, and approve.
In a new thread, turn the INFIOO connector on and ask "what needs me today?" If your real brief comes back, you are done.

Nothing else to paste: you sign in to infioo when Perplexity asks, unless you use the key fallback below. Leave any client ID, client secret or advanced OAuth fields empty - Perplexity registers itself, and infioo issues no client secret.

Perplexity then reads the tool list off the server itself - nothing to configure tool by tool, and no install, hosting or tunnel: infioo.ai is already on the public internet.

If sign-in doesn't work: the API-key fallback

An owner can mint an automation key in infioo under Settings -> Connections. It is shown once, so copy it then. In Perplexity, choose API Key as the authentication instead of OAuth and paste the key - infioo accepts it as a bearer token or in an x-api-key header.

An automation key is different. It always carries read and write (never approve), isn't tied to a person's role, and works until an owner revokes it in Settings -> Connections. Use it only where sign-in isn't possible.

Try it first, with no account

Use this URL at step 2 and set authentication to None.

https://infioo.ai/api/mcp/demo

No sign-in, no email, nothing to cancel - a fictional plumbing company carrying a normal week's mess. Read-only, and the assistant is told the data is invented as soon as it connects.

Eighteen tools. Five write. None send.

18tools Perplexity can call

13read your business

5write to your records

0that can send or bill

Can

Read contacts, conversations and messages
Read the schedule, invoices and open tasks
Search your knowledge base
Create a task or a contact
Tag a contact
Draft a reply for your approval
Mark an appointment complete

Cannot

Send a message to a customer
Create, send or sync an invoice
Post publicly as your business
Add anyone to a marketing list
Touch billing, team invites or payroll
Manage API keys
See another business's data

Drafting is not sending. A reply Perplexity writes becomes a pending draft behind the Approve button already in your inbox. And the right-hand column is not a setting - those tools are absent from the connector, each with its reason recorded in code and a test that fails if one sneaks back. There is a daily write ceiling per business too, so a confused loop cannot run away with your records.

Permissions, and who may grant them

On the sign-in screen you grant from three permissions - read, write, approve - and your role caps what you may hand over, so plugging in an assistant is never a way to gain access you did not have. Owners and managers may grant all three; staff cannot grant approve; an accountant can grant nothing.

When you connect by signing in, access tokens last fifteen minutes, refresh tokens rotate, and your role is re-checked on every call against live membership - so a change in infioo narrows the connection on the next question.

When Perplexity calls an infioo tool, the answer - customer names, messages, amounts - goes to Perplexity and becomes part of that chat, kept under Perplexity's terms and your settings there. infioo doesn't copy your records anywhere else.

Honest limits

Booking and invoice proposals are not offered from chat yet. Both belong in the owner's approval queue, which today assumes a pending item came from one of your agents - so a proposal from a chat connector would fail the moment you pressed Approve. That code guards real money, so it changes carefully or not at all.

An API key is a high-trust credential. It can read every customer, conversation and invoice in the business and make the five changes above - roughly owner access minus the ability to move money. Treat it like a password, and revoke it in Settings the moment a device goes missing.

We haven't tested infioo end to end in Perplexity yet. The server follows the published MCP specification and Perplexity's documented connector setup, so it should work. If it trips, tell us at hello@infioo.com.

Connect your shop to Perplexity

in Perplexity