CRM
HubSpot
Contacts, companies, deals and tickets, read and written directly.
Official site: app.hubspot.com
What it does
- Search and read contacts, companies, deals and support tickets
- Create and update records across all four objects
- Read and write notes attached to a record
Four objects — contacts, companies, deals, tickets — all read and write, plus the notes attached to each. A workflow that needs to both qualify a contact and log why doesn't need a second tool for that.
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 HubSpot 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 HubSpot 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 HubSpot returns something usable instead of something generic.
Processes that run on HubSpot
Brief every cold call before it starts
Every account on the call list gets a note before anyone dials, carrying the signals found on it, what the lead has said publicly, and one opener grounded in both.
Build a target list from a sentence
Describe the companies you want in one sentence, and get them sourced, scored on dated signals, enriched, deduplicated against your CRM, and staged as a campaign.
Catch churn signals and answer them
Usage falling away shows up in analytics before anyone notices on a call, and the drop is read against the account's history into one reactivation email.
CRM hygiene and prospect job changes
Duplicates merged and broken fields repaired on a weekly schedule, with prospects who changed employer followed to their new company and a recap posted to the team.
Draft the monthly investor update
Revenue, pipeline, the plan's own targets, and last month's commitments are pulled together into a draft with the numbers already in it.
Find buyers engaging with competitors
Everyone who engages with a competitor's posts gets found, scored against your ICP, enriched, and staged for outreach with a human approving the list.
Prepare for a demo from the last call
The last calls, the deal's state, and fresh research become one prep brief, plus a deck built around that company's own use cases, posted before the meeting.