CRMConnector
Lightfield
Search, create and update Lightfield accounts, contacts and opportunities from Claude or ChatGPT, through Tulina's own MCP server, not Lightfield's hosted one.
Official site: lightfield.app
What it can do
2 read/1 write/1 send
- 01Read
Search and read accounts, contacts and opportunities
- 02Write
Create and update records, including custom objects
- 03Read
Read the workspace's own field definitions before writing to it
- 04Send
Send an email from the CRM
The field model belongs to each workspace, so the keys a write has to use are the ones your team created — not a universal schema anyone can assume. Reading the definitions first is the whole difference between an upsert that lands and a 400. And the search index trails a write: after creating something, read it back directly rather than searching for it, or you will see the state from before.
How do you connect Lightfield to Claude and ChatGPT?
Through Tulina's own MCP server, not Lightfield's own hosted one. Search accounts, contacts and opportunities, create or update a record against your workspace's own field definitions, and send an email from a connected inbox — 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 Lightfield 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 Lightfield 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 Lightfield returns something usable instead of something generic.
Processes that run on Lightfield
None published yet.