get_company before writing anything about a company, so you add to the research rather
than replacing it — update_company replaces the notes field it is passed.
A company’s website is their own domain, not a job-board link. Nothing else depends
on it, but it is what puts their logo on the pipeline, so it is worth setting whenever you
learn it.
log_activity takes either an applicationId or a contactId, never both. With a
contact id it becomes that person’s history — their page shows it and their “last
touched” date moves. update_contact’s nextFollowUpAt is where “ping them in two
weeks” lives, and due pings surface in list_follow_ups alongside due applications.
The descriptions below are quoted verbatim from what the server sends a connected
assistant, which is why they address it rather than you. They are reproduced rather than
rewritten so this page cannot drift from what your assistant actually receives.
list_companies
List companies
Every company on file, with how many applications and contacts each one has, plus lastAppliedAt (when you last applied there) and openApplications (how many are still live). Use this to answer ‘who have I applied to’, to find a companyId before calling get_company, or to spot companies missing a website — the website is what makes their logo appear in the pipeline. Pass search to match on name, industry, location or notes; pass filter to cut the list: ‘active’ = something still in flight, ‘applied’ = ever applied, ‘never-applied’ = researched but never sent anything, ‘with-contacts’ = you know someone there.
get_company
Get a company
Everything on file for one company: website, industry, size, location, your research notes, every application you have with them, and every contact who works there. This is the tool to call before writing anything about a company, so you add to what is known rather than replacing it.
create_company
Create a company
Add a company before you have applied to them — somewhere to keep research while you decide. Applications create their company automatically, so reach for this only when there is no application yet. Names are unique per person; creating one that already exists is an error rather than a silent merge.
update_company
Update a company
Change what you know about a company. Only the fields you pass are touched, but each one REPLACES what was there — notes especially, so call get_company first and write back the whole thing if you are adding to research rather than replacing it. Setting website is the single thing that makes their logo show in the pipeline; a job board URL is not their website.
Overwrites or deletes.
delete_company
Delete a company
Remove a company record. Refuses while applications still point at it — move or delete those first, so tidying up a company can never take an application with it. Contacts survive and simply lose their employer.
Overwrites or deletes.
List contacts
Recruiters, hiring managers and referrals. Narrow by application, by company, by a search across name, title, email, notes and employer, or by filter: ‘ping-due’ = their follow-up date has arrived, ‘with-application’ = attached to an application, ‘no-company’ = no employer on file. Returns each person with their company and the application they are attached to.
Get a contact
One person in full, with their company and the application they belong to. Call this before update_contact so you know what you are about to overwrite. Also returns their timeline — every call, coffee and reply logged with log_activity, newest first — so ‘when did I last talk to them’ is answered from here.
Update a contact
Change a person’s details. Only the fields you pass are touched, and each REPLACES what was there — read first with get_contact if you are adding to notes or otherLinks rather than replacing them. Pass company to move them to a different employer (created if it does not exist), or an empty string to detach; same for applicationId.
Overwrites or deletes.
Delete a contact
Remove a person. Their company and any application they were attached to stay.
Overwrites or deletes.
Create a contact
Save a person: recruiter, hiring manager, referral, friend at the company. Record every way you can reach them — linkedin, twitter, instagram, github, website, and otherLinks for anything else — because the one that matters is whichever they actually answer on, and a name with no way to contact it is a dead row.
