Pull insights from call recordings
Conversation intelligence from a name, company or email: the right sales call found in your CRM or recordings, returned with a summary, the link saved back.
- Starts
- Question asked in chat
- Steps
- 5
- Checks and gates
- 0
- A person decides
- Never, runs alone
Trigger · Chat
Question asked in chat
Someone asks for a call by name, company or email, and that question is the run's only input.
Claude runs the rest autonomously
- 1
AI pins down the person and company.
A work email yields a person and a company, while a free mailbox yields a person only, never a guessed company.
- 2
AI finds the matching CRM record.
FolkFolk
The person or company is found in the CRM by whatever you were given, with the record confirmed if the name was ambiguous.
- 3
AI reuses a link already saved.
FolkFolk
A recording link already saved in a field, a note or a logged interaction is used first, since that is where it usually sits.
- 4
AI locates the call in the recordings.
GranolaGranola
If the CRM had nothing, the call is found by participant email and separately by company domain, since it may sit under a colleague.
- 5
AI returns the call and logs the link.
FolkFolk
The call comes back with its date, participants and a summary, and its link is saved to the CRM if it wasn't already there.
"Can you find the call where they mentioned X" is a five-minute detour for whoever gets asked. Open the CRM, guess at which note has the link, fail, open the recording tool, search by a name that might not match how the call got logged, and often give up before finding it.
Most of the time the answer is already sitting in the CRM from the last person who looked: a pasted link in a note nobody thought to search for directly. The rest of the time, the recording tool itself resolves it in one search, by whichever identifier actually works. Either way, the pointer gets saved back, so the same lookup is instant next time.
What you get
The right call, with its link, date, participants and summary, returned in seconds and the pointer saved back to your CRM for next time.
How AI finds a call recording from a name or email
The only input is the question someone asks in chat: a name, a company or an email address. Before searching anything, the agent works out what that input actually identifies.
- An email at a company domain gives both a person and a company. Both are kept, since the call may be logged against a colleague rather than the exact person named.
- An email at a free mailbox, such as Gmail or Outlook, gives a person only. A company is never inferred from a free-mailbox domain.
- A bare company name may be ambiguous. Two similarly named companies is a question worth asking, so the agent resolves it to one record before going further.
It then finds the matching record in Folk, by email for a person or by name or domain for a company. From a person it reads the linked company; from a company it lists the people.
Checking the CRM before the recordings tool
Checking the CRM first is what makes this fast most of the time. Someone has usually already found this exact call and pasted the link somewhere, and re-deriving it from scratch wastes a search that a well-placed field or note already answered. The agent looks in three places, in order:
- Any custom field on the company or contact record that holds a recording link, listing the record's fields first when the name of that field is unknown, instead of assuming there is none.
- Notes on the company and the contact, searched by company name, contact name and the recording tool's own domain, since a pasted call URL contains it.
- Logged interactions, which often carry the link, or at least a date that narrows the next search to a single day.
When one of them has the link, that is the answer: the most recent match comes back, with a count of any others.
Searching the recordings when the CRM has nothing
When the CRM has no pointer, the agent searches Granola by the participant's exact email and separately by the company's domain, a year back by default. Searching by company domain as well as the person catches the case a name-only search misses: a call is often recorded against whoever hosted it, so the person you were asked about may show up on a colleague's call instead of their own. If the person's own address returns nothing, the domain search runs before anyone concludes there is no call.
If several calls match, the most recent one wins and the others are listed, never dropped silently. The answer carries the call link, its date, the participants, a one-paragraph summary, and the CRM record it belongs to.
Why the link gets written back
Writing the pointer back after a direct hit on the recordings tool is what turns this from a one-off answer into a system that gets faster every time it runs. The link is set in a field or logged as a note, so the next lookup for the account finds it in the CRM. Skip that step and the same account gets the slow path again next time, indefinitely. It is the same idea as a company brain: an answer found once stays where the next person looks.
A call that cannot be found is reported as not found. The agent never invents a call, a date or a quote, and never reconstructs a call from notes and presents it as a recording.
The prompt
The real prompt behind the steps above, detailed enough that an agent with the same tools can run it as written. The Run buttons copy the full version, which also carries the steps for connecting those tools.
# Find the recording of a call from a name or email
You have access to your CRM and a call-recording tool. Run this for
**[an email address or a company name]**.
## 1. Pin down the person and company
- An email at a company domain gives you both a person and a company —
keep both, since the call may be logged against a colleague rather
than the exact person you were given.
- An email at a free mailbox (gmail, outlook, and similar) gives you a
person only. Never infer a company from a free-mailbox domain.
- A bare company name may be ambiguous. Resolve it to one record before
going further — two similarly-named companies is a question worth
asking rather than a guess worth making.
## 2. Find the matching record in your CRM
Search by whichever axis you have — email for a person, name or domain
for a company. From a person record, read their linked company; from a
company record, list its people. If the company name was ambiguous,
confirm which record before continuing.
## 3. Reuse a recording link already in your CRM
Most of the time, the pointer is already there — someone pasted the
link into a note, an interaction, or a dedicated field the last time
they found it. Check, in order:
- Any custom field on the company or contact record that looks like a
recording link — list the record's custom fields first if you're not
sure what it's called in your CRM, rather than assuming it's absent.
- Notes scoped to the company and the contact — search by company name,
contact name, and the recording tool's own domain, since a pasted
call URL contains it.
- Logged interactions — these often carry the link, or at minimum a
date that narrows the next step to a single day.
If you find a match, that's the answer — return the most recent one,
and note how many others exist. There's no need to query the recordings
tool directly once the CRM already has the pointer.
## 4. Locate the call in your recordings, if the CRM had nothing
Search by the participant's exact email, and separately by the
company's domain over a reasonable window (a year back is a sensible
default) — the call may be recorded against a colleague rather than the
exact person you started from, which is exactly the case your CRM
couldn't answer. Fetch the matching call: title, date, duration,
participants, and a summary.
If several calls match, the most recent one wins — list the others
rather than dropping them silently. If searching by the person's own
address returns nothing, retry on the company domain before concluding
there's no call.
## 5. Return the call and log the link back
Answer with: the call link, its date, the participants, and a one
paragraph summary — plus which CRM record it belongs to.
If the call was found by querying the recordings tool directly and your
CRM had no pointer to it, write it back — set the field, or log a note
— so the next lookup for this account is a step-3 hit instead of a
step-4 one.
## Output
Report: which step resolved the call (CRM pointer vs. direct query),
the call details, how many other matches existed if more than one, and
whether a pointer was written back to the CRM.
Why run it with Tulina
A prompt helps one person. A process moves a team.
Pasted into a chat, the prompt above works once, for whoever pasted it. In Tulina, "Pull insights from call recordings" becomes a process the team shares, that keeps its history, runs on its own, and stays inside the same security perimeter as the tools it calls.
The whole team works on the same one
PersonalTeamOrganisation
A process lives where it belongs: yours, your team's or the whole organisation's. Whoever runs it can improve it, and everyone starts from the best version instead of explaining the job again.
Every edit is a version
v1v2v3
Each change is a new version with the previous one kept, so a bad edit is undone by restoring an earlier one. Every run records the version it followed, and what a run teaches goes back into the process.
It runs without you
schedulewebhookon demand
A hosted agent runs the process on Tulina's own infrastructure, on a schedule or when an event arrives, and keeps going when you close the chat. Nothing to host. Every run is tracked to its outcome.
Inside the same security perimeter
vaultrolesrun log
Credentials stay in the vault, never in the prompt. Roles decide who may run what, every call is logged, and a step a person has to approve waits for that person.
Questions about searching call recordings with AI
Also on Folk
Other processes that run mainly on Folk. The tools they share with this one are lit.
Find contacts for signal accounts
Companies that already showed interest but have nobody linked get the right people found by role, deduped, and added to outreach automatically.
- Shares
- Folk
Interest signal received6 steps →
Re-engage quiet accounts
Quiet paying accounts get one relevant note each, grounded in what they said last, with the outreach date stamped back so nobody's emailed twice.
- Shares
- Folk
Weekly schedule7 steps →
