ProspectingConnector
Tulina Enrichment
Job-change detection and subsidiary discovery, built into Tulina's own MCP server — no separate connector, in Claude or ChatGPT from the start.
What it can do
2 read
- 01Read
Check whether a contact has changed jobs, so a stale CRM record gets flagged instead of trusted
- 02Read
Discover a company's subsidiaries
Every other page here is a system Tulina reaches into. This one is not — it is a small enrichment service Tulina runs itself, alongside everything else, rather than a vendor's API wrapped in a connector.
It still goes through the same vault as any other key. Being ours does not mean it gets a shortcut past the policy that decides what a model can see.
How do you use Tulina's enrichment API from Claude or ChatGPT?
There's nothing to connect. Job-change detection and subsidiary discovery run through the same MCP server as everything else Tulina does, so they're already there — check whether a contact changed jobs, or list a company's subsidiaries, from the same chat as Claude or ChatGPT.
Why through Tulina
The connection was never the hard part.
Most systems now publish their own way for a model to reach them, and that is good: it is what Tulina connects to. The hard part is deciding who may use it, what it is allowed to return, and what the model knows before it asks.
The keys stay in one place
YouTeamOrganisation
Connect Tulina Enrichment once. The credential is encrypted in a vault, never held in clear, and never pasted into a chat or a workflow file. A person uses their own key where they have one, their team's where they do not, the organisation's after that, so nobody is blocked and nobody holds more access than they need. Revoke it once and everything running on it stops.
What leaves is filtered before it leaves
fields droppedmasked or hashedpseudonymised
Roles decide who can reach Tulina Enrichment at all. Beyond that, a policy on the connector itself decides what comes back. The data is minimised at the source rather than after it has already reached a model.
Every call is on the record
whatwhowhen
Runs are logged for the organisation. That is what makes an automated action reviewable after the fact, and it is what a security review asks for first.
The run starts knowing your company
namingkey accountsdecisions
A direct connection gives a model access. It does not tell it how your company names things, which accounts matter, or what was decided last quarter. Tulina carries that across every tool, so the same request against Tulina Enrichment returns something usable instead of something generic.
Processes that run on Tulina Enrichment
None published yet.