Connect Bizinly to your own Lucy

If you have your own Lucy account — or use Claude, ChatGPT, or another assistant that supports secure connectors — you can connect it to your Bizinly workspace so it can act on your data directly: search your documents, draft and issue invoices, record payments, and more, from inside its own chat, without switching over to Bizinly first.

This is a different, more powerful step than the built-in Lucy panel: once connected, the assistant is working with your real data, on your behalf, exactly as if you had clicked through the screens yourself. See Meet Lucy for how the two compare, and What Lucy can do in your workspace for the full list of what it can do once connected.

Every connection is created under Admin → MCP & connections (owners; also reachable from Settings → Company).

Connecting Lucy

1. In Bizinly, open Admin → MCP & connections and press Create API key. Copy the key — it is shown once, right after creation.
2. In Lucy, open Connectors → Add custom, and fill in a name, your Bizinly workspace's address (https://<your-workspace-domain>/api/mcp), and the key.
3. Save, then ask Lucy something that needs your Bizinly data (see the examples below).

Connecting Claude or ChatGPT

Claude and ChatGPT (and other clients that discover connectors automatically, rather than accepting a pasted key) sign in instead of using a key directly:

1. In Claude or ChatGPT, add a custom connector and give it your Bizinly workspace's address (https://<your-workspace-domain>/api/mcp).
2. You'll be sent to sign in with your Bizinly account, then asked to press Allow.
3. Only an active member of your workspace can complete this step — an account that isn't part of your business is refused, rather than being given a connection that could do nothing.
4. The connection appears under Admin → MCP & connections alongside any key created by hand, named for the app that created it, and is revoked the same way.

Connecting Claude Desktop, or another client that runs locally

Some clients — Claude Desktop, for example — connect by running a small local command instead of signing in through a browser. Admin → MCP & connections has a ready-to-copy configuration for this: paste it into that client's own configuration, replace the placeholder with an API key created the same way as above, and restart the client.

Try asking

• "Who owes me money?"
• "Create an invoice for Northline for 3 consulting hours at 120 and one onboarding package"
• "Issue it and e-mail it"
• "Show unpaid invoices older than 30 days"
• "Draft a reminder for invoice INV-2026-00003"
• "Book a visit for order 1048 next Tuesday at 10"

Revoking access, and good practice

• The connection acts as whichever person created it — with exactly that person's own permissions, nothing more. If it can search but can't create or change something, the person who created it is missing that permission in Bizinly.
• Every action it takes goes through the same checks, and lands in the same activity log, as if you had done it yourself in the app.
• Revoke a key or connection from Admin → MCP & connections the moment it is no longer needed, and prefer a separate one per person or integration rather than sharing one.
• If the person who created a connection is later removed from your workspace, that connection stops working.

Troubleshooting

• The assistant says it can't connect — check the workspace address is exactly https://<your-workspace-domain>/api/mcp, and that the key hasn't been revoked.
• Sign-in is refused (Claude / ChatGPT) — only an active member of your workspace can complete the connector sign-in; ask whoever manages your team to add you first, then try again.
• It can find things but can't create or change them — the connection's owner is missing that specific permission; check or adjust it under Team members and roles.
• It asks to confirm before importing data — that's by design: importing customers or products always shows the plan first and writes nothing until you confirm.

Related: Meet Lucy, Lucy, your in-app assistant, What Lucy can do in your workspace, Team members and roles, Account security.