Setup guide

Connect Claude to Pixl

Ask about conversations and leads, reply to customers, set up agents, send WhatsApp campaigns, schedule calls and check results, all from a chat with Claude. You approve the connection once, and Claude works with the same permissions you have.

Your connector address

Your connector address is shown in Connections › Developers › Claude & AI apps, with a copy button. It is different for each environment, so copy it from there rather than from a guide.

claude.ai or Claude Desktop

In Claude, open Settings › Connectors and choose Add custom connector.
Paste the connector address and save.
Click Connect. A Pixl page opens: sign in if asked, pick the workspace Claude should work in, choose how much it can do, and click Allow.

If your organisation uses Claude Team or Enterprise, an owner may need to add the connector first.

Claude Code

Run claude mcp add --transport http pixl followed by the connector address from Connections › Developers. Then type /mcp in Claude Code, pick pixl, and sign in. The same Pixl approval page opens in your browser. It warns you that the connection comes from an app on your computer: only continue if you just started it.

To connect without a browser, for example on a server, create an API key for one workspace in Connections › Developers and add it as a header: --header "Authorization: Bearer pxl_…".

A key follows the same rules as a Claude sign-in

Guests can't use one. When the owner turns off “Members may connect AI apps”, members' keys are refused too. Keys used from Claude are listed on the Claude & AI apps card, where you can revoke them. Revoking a key stops it everywhere, not only in Claude.

What Claude can do

Everything your role in the workspace allows, in the areas you picked on the approval page:

Agents
Conversations and replies
Contacts
WhatsApp templates and campaigns
Calls
Knowledge
Automations
Orders
Results
Billing (view only, plus top-up links)

You approve what reaches customers

Sends to many people at once (campaigns, or turning on automations that message customers), calls, publishing an agent and deletes show a preview first and need your OK. Single replies and one-off template messages go straight through after Claude's own per-action prompt, and are never sent twice by accident. Keep Pixl's send and delete actions set to “ask” in Claude: if you choose “always allow”, Claude stops asking.

“Pause all sending” stops what Claude sends, not what is already running. While it is on, Claude's own sends (replies, template messages, campaigns, calls, email replies and follow-ups sent now) are refused or held, and Claude can't turn an automation on. Automations that are already on, and follow-ups your agents have planned, keep sending: turn those off in the dashboard.

What Claude can never do

These stay in the Pixl dashboard, for you to do yourself:

Make payments, change your plan or change spending limits
Buy or release phone numbers
Approve items waiting for your OK (“Ask me first”)
Launch or change ads
Invite people, change roles or remove members
Record that someone agreed to be messaged or called
Delete or transfer the workspace
Create API keys or change connected apps

The same rules that protect your customers in the dashboard apply to Claude too: opt-outs, message windows, calling hours, do-not-call lists, your balance and template approval.

See or remove connections

See your connections. Every connection is listed in Connections › Developers › Claude & AI apps. Owners and admins see everyone's in the workspace.
Remove a connection. Click Revoke and it stops working at once.
Automatic removal. Connections also end when you change your password, sign out of other sessions, turn off two-factor sign-in, or leave the workspace.
Who may connect. Workspace owners can turn off “Members may connect AI apps”. Owners and admins can still connect. It is off by default for health workspaces.

Every change and send Claude makes is recorded in your workspace's Activity, marked “via Claude”. What Claude only reads is not listed there.

Building your own integration?

The developer docs cover the API: sending templates, contacts and consent, and webhooks.

Stuck on a step?

Tell us where it stopped and what it said, and we'll help you finish the setup.

Talk to us