Tool reference
KnowWho gives your assistant thirteen tools. You will never call one by name. This page is for people who want to know what is actually happening, and for anyone reviewing the connector.
Reading
None of these change anything. Your assistant can run them without asking you first.
search
Finds people, companies, events, notes, interactions and opportunities by the words in them: names, any of a person's email addresses, and what was written down. Near misses and misspellings still match. An exact email, full name or company name short circuits straight to that record. Search by meaning is planned and not live yet.
get_person
Everything known about one person. Their details and tags, every place they work now and where they worked before, every interaction, every note, open tasks, and who they are connected to.
get_company
Everything known about one company. Who works there, what has happened with them, any live opportunities, and how it relates to other companies: its members or the networks it belongs to, its clients and suppliers, its parent or subsidiaries, its partners.
get_opportunity
Everything known about one opportunity. Value, stage, status, who is involved and in what role, and the history of what has happened.
query
Structured questions across the whole book, returning just the fields that answer the question. Open tasks, live opportunities, people not contacted since a date, everyone carrying a tag, every member company of a network, and so on.
Writing
These change your book. Your assistant confirms before running the ones that modify or remove existing data.
record_encounter
The main capture tool. Takes a whole account of what happened and records the meeting, the people in it, the company, the notes and the commitments in one call. Every person, company and event is matched before anything is written, so an ambiguous name stops the capture before it starts rather than halfway through. Returns a readable confirmation of exactly what it did.
Tags and contact details given for someone already in your book are not applied by a capture. The confirmation says so, and one follow-up sentence adds them.
Exists because capture used to be eight or ten separate calls, and anything that takes eight calls will eventually half-fail in a way nobody notices.
create_entity
Creates one person, company, note, task, event or opportunity, with tags if you give them. A tag you have used before is reused, however you spell it. Only adds, never modifies.
link
Connects two things. A person to their employer, a note to who it is about, a person to an opportunity with their role in it, one company to another: a member of a network, a client of a supplier, a subsidiary of its parent, or a partner, with dates and notes if you have them. People can work in more than one place, so a new job never ends an old one by itself: your assistant asks whether they have left.
update_entity
Changes something that already exists. Email addresses, phone numbers and tags are added and removed one at a time, so changing one never loses the others.
update_link
Changes a connection, such as someone's role in a deal.
delete_entity
Removes a record.
delete_link
Removes a connection without removing either thing it connected.
Feedback
send_feedback
Sends a note about KnowWho itself to the people who build it: a feature you want, something that broke, something that works well. Your assistant asks before sending. It never carries anything about the people in your book.
How writes behave
Every write comes back as one of four things:
Done. Here is what was written.
Cannot proceed. Here is why, in terms you can act on. Nothing was written.
Needs a decision. The name was close to something that already exists. Here are the candidates. Nothing was written. Say which one you meant, or say to create a new one.
Plan limit. Your plan's limit on people or companies has been reached. Nothing was written. The response says what the limit is and where to change plan.
Every response also states what was assumed. A company created because it did not exist. A fuzzy name match accepted. A date defaulted to today. Assumptions are reported as facts, so you see them and can correct them.
Safety annotations
Read tools are marked read-only, so they run without a confirmation prompt each time.
Write tools are marked according to what they can do to existing data. create_entity and record_encounter only ever add, so they are not marked destructive. Everything that modifies or removes existing data is, which means your assistant asks before running it.
Limits worth knowing
Responses are scoped and paginated rather than returning everything at once. No tool returns your whole book in one go, because that helps nobody and costs you context.
Errors come back as something you can act on rather than a generic failure. Every error carries a reference such as KW-7F3A2B. Quote it if you get in touch and we can find exactly what happened.
Next: Troubleshooting