CRM
Salesforce
Read, write and bulk-update any object.
Official site: www.salesforce.com
What it does
- Query any object with SOQL, or search across them when you do not know where a record lives
- Read the schema of an object, so a request works against your custom fields rather than a guess
- Create, update, upsert and delete records one at a time
- Bulk-create and bulk-update, for the jobs that touch thousands of rows
- Read and write the notes attached to a record
A Salesforce token carries one permission level: whatever it was issued with. Point a model at it directly and the model inherits all of it — delete included, every field on every object, for anyone who can reach that model.
Here the token sits in a vault, roles decide who can reach it, and a policy decides what comes back.
Why through Tulina
Most systems now publish their own way for a model to reach them, and that is a good thing — it is what Tulina connects to. The connection was never the hard part. Deciding who may use it, what it is allowed to return, and what the model knows before it asks: that is.
The keys stay in one place
Connect Salesforce 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 is handed more access than they need. Revoke it once and everything running on it stops.
What leaves is filtered before it leaves
Roles decide who can reach Salesforce at all. Beyond that, a policy on the connector itself decides what comes back: fields dropped, identifiers masked or hashed, people pseudonymised. The data is minimised at the source rather than after it has already reached a model.
Every call is on the record
Runs are logged for the organisation — what was called, by whom, when. That is what makes an automated action reviewable after the fact, and what a security review asks for first.
The run starts knowing your company
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 Salesforce returns something usable instead of something generic.
Processes that run on Salesforce
Keep CRM accounts updated
Companies already in your CRM are watched for legal events, flagged before a rep ever walks into a call blind.
Qualify inbound leads
Every new lead is matched to its legal entity, scored on real headcount and filed accounts, and written back before a rep opens it.
Source and qualify leads
A target company gets searched across LinkedIn, ranked against your ICP, and the qualified shortlist lands in your CRM with email and mobile filled in.