Connectors

Enrich from the web asks the public web. A connector asks somewhere you already have an account.

If you pay for Apollo, you have a data source Dhaga can't match — and you're already paying for it. Connect it once in Settings → Connectors, and an Enrich from Apollo button appears beside Enrich from public web ✦ on every person and company page.

What a connector is

A credential you own, stored encrypted, that Dhaga spends on your behalf.

That last part is the whole difference. When you press Enrich from public web, Dhaga pays for the search. When you press Enrich from Apollo, Apollo bills your Apollo account, in Apollo's own credits, exactly as if you'd looked the person up there yourself. Dhaga's only cost is reading the answer, which is why a connector run costs 2 credits against enrichment's 20.

Your plan, permissions and credits at the provider still apply. A free Apollo account has restricted enrichment, and if Apollo refuses, you'll see Apollo's own reason — not a generic failure.

Connecting one

Go to Settings → Connectors. Each available provider offers one of two things, and which one it is isn't a choice we made:

Apollo takes an API key. Create one in Apollo, paste it in, give the connection a name. The key is checked against Apollo before it's saved — a credential that doesn't work is refused rather than stored for you to discover later.

Apollo MCP uses OAuth. There is no key to paste: you press Connect, authorize Dhaga in Apollo's own consent screen, and come back. It reaches Apollo's MCP server, which exposes far more than lookups — so Dhaga pins the specific tools it may call when you connect, and refuses anything that sends mail or creates records even if it were pinned by mistake.

Name your connections for the account, not the product — "Apollo (work)" — if you're ever likely to have two.

Your key is never shown again

Once saved, a credential is write-only. The settings page shows the last four characters and nothing else, and there is no Reveal button anywhere in Dhaga.

This is deliberate, and it isn't about trusting you: a revealed key is one screenshot, one screen-share, or one shoulder away from being someone else's, and nothing can un-leak it afterwards. If you need to change it, Replace it — same connection, same name, new key.

Using one

The button sits beside the web one, and behaves the same way: the work runs in the background, keeps going if you leave the page, and lands as a note on that person or company. That note yields facts, each with its receipt, which you confirm or reject like any other. Delete the note and everything it produced goes with it.

Each button has its own state. If Apollo is out of credits, the web button still works — they fail independently, for unrelated reasons, and say which.

When something goes wrong

Two failures are yours to fix, and both say so plainly rather than blaming Dhaga:

• "Reconnect in Settings" — the provider rejected the credential. A key was revoked or rotated, or an OAuth grant expired. The connection is marked Needs reconnecting and offers the repair inline.
• "Your provider account is out of credits" — the connection is fine; the account behind it has nothing left to spend. Nothing to fix in Dhaga.

Removing one

Remove deletes the credential. It does not delete the notes or facts that connector produced — those are yours, they're already part of your graph, and they stay exactly where they are. The button says so before you confirm it.

Removing a connector is also not how you delete the data: that's deleting the notes, same as anything else in Dhaga.

What connectors are not

• Not automatic. Like every enrichment in Dhaga, a connector runs when you press the button. Nothing is looked up in the background, and connecting an account does not begin a sync.
• Not a bulk import. A connector answers about one person or one company at a time. Pulling a whole Apollo list into your contacts is a different thing and doesn't exist yet.
• Not your own server. Only providers Dhaga ships can be connected today — you can't point it at an arbitrary MCP URL.

Plans

Connectors are a Pro-and-up feature. On a plan without them the section still renders — you can see what you'd get — but the add and connect controls are greyed with the reason beside them, rather than accepting the click and failing afterwards. Already-configured connections are never greyed by a plan lapse: a working integration isn't taken away, and neither is the button that removes it. On a self-hosted instance there is no plan, and everything is included.

Adding a provider to a self-hosted build is one module and one registration — see Add a connector.