youspot.com

What this user should deal with right now, computed from their sent mail, their calendar and their LinkedIn export: people who went quiet after real correspondence, people they are meeting this week, who they write to most, invitations nobody answered, and the shape of their network.

Research one specific company in depth — the same engine behind the CompanyResearch.

Look up the public registration (WHOIS) record for a website domain: who registered it, which registrar holds it, when it was created and last updated, when it expires, its nameservers, and its registry status codes.

Estimate what a domain name is worth (the /domainvalue appraisal): an estimated market value in dollars with the signals behind it — comparable sales, marketplace listings, an appraisal model, SEO data.

Send an email to the signed-in user at their own account email address.

Read the content of a file the user uploaded — use this when the answer may live in a document in their Second Brain: schedules, itineraries, contracts, exports, scans.

Download a file from a public http(s) URL and store it in the user's Second Brain as a file object — use when the user shares a direct link to a PDF, image, spreadsheet, or other file and asks to save, download, or keep it.

Import every contact or company from a file the user uploaded — a CSV or spreadsheet export, a .

Search the user's connected Gmail mailboxes and return matching messages, newest first — from, to, subject, date, and a short snippet of the body.

Fetch one Gmail message by its id from the user's connected mailbox, including the full plain-text body (rare header-only connections get headers and the snippet instead).

List the labels in the user's connected Gmail mailboxes — system labels (INBOX, STARRED, .

Create a DRAFT email in the user's connected Gmail mailbox, addressed to anyone — 'draft an email to jane@acme.

Archive one Gmail message — it leaves the inbox but stays in All Mail, fully recoverable.

List events from the user's connected Google Calendar, ordered by start time — summary, start/end, location, organizer, attendees and their RSVP status, and a meeting link when there is one.

List the calendars in the user's connected Google account(s) — name, id, whether it's the primary, and the user's access role.

Create one new event on the user's Google Calendar — title (summary), start, and end are required; description and location are optional.

Update one Google Calendar event — change its title (summary), description, location, or start/end times.

List objects in the user's graph, newest first, with counts by type.

Get one object from the user's graph, with the objects connected to it (its edges, e.

Rename or re-describe an object in the user's graph, or set its type-specific fields — a contact's email, headline or location, a company's funding stage, and so on.

Search the user's graph by matching a term against object names and descriptions — plus semantic matching over text-bearing objects (notes, facts, posts, links, files, emails), so a search finds what the user means, not just exact words.

Create a new object in the user's graph.

Set up a standing search the user wants watched — 'track LinkedIn posts that mention hubspot', 'track tweets mentioning @dharmesh', 'watch acme.

Connect two objects in the user's graph with a directed edge — e.

Delete an object from the user's graph.

Delete EVERY object of one type from the user's graph, however many there are: what to reach for when they ask to clear out a whole category ('delete all my HubSpot contacts') rather than one record.

Record one dated touchpoint with someone in the user's graph — an email exchanged, a call, a meeting, a LinkedIn touch, or a manually noted contact — so 'when did I last talk to them?

Merge two duplicate records in the user's graph into one — person or company only.

Permanently delete one object from the user's graph, along with every connection touching it.

Delete one connection between two objects in the user's graph — the edge from_object_id -> to_object_id of the given connection_type, nothing else; both objects stay.

How two objects in the user's graph are connected: the shortest chain of real relationships between them, up to 3 hops, e.

The objects in the user's graph directly connected to BOTH of two given objects — mutual contacts between two people, shared people between two companies.

The objects in the user's graph closest in MEANING to one object — nearest neighbours by stored embedding, so it finds related notes, facts, links, files, and posts even when no words match.

Set a dated follow-up about an object in the user's graph — 'follow up with Jane in March'.

Query the user's HubSpot contacts — the people synced from the HubSpot portals they've connected.

Query the user's HubSpot companies — the companies synced from the HubSpot portals they've connected.

Overview of the user's synced HubSpot data: which portals they have connected, how many contacts and companies came from each, and when each was last synced.

Read an invoice PDF the user uploaded and return its fields: supplier, invoice number, dates, currency, subtotal, tax, total, PO number, payment terms, and every line item.

Search the user's own LinkedIn connections by name, company, or job title.

Get the full profile for one of the user's LinkedIn connections: work history, education, skills, and their About summary.

Ask a free-form question about the user's LinkedIn connections that the other tools can't express: aggregates and rankings ('which companies do I know the most people at?

Ask a question about the user's LinkedIn invitations — the requests they sent and received.

Overview of the user's imported LinkedIn data: how many connections, invitations and messages they have, when it was last imported, and the companies they know the most people at.

The user's own LinkedIn posts with engagement numbers (reactions, likes, comments, shares) — newest first by default, or their earliest posts with sort='oldest'.

The user's LinkedIn post analytics from LinkedIn's own API (their connected account) — impressions, unique members reached, reactions, comments, and reshares.

Overview of the user's imported LinkedIn messages (DMs): how many messages and conversations they have, the date range covered, and how many they sent versus received.

The people the user has exchanged the most LinkedIn messages with, most-messaged first, with how many messages and when they last spoke.

List the Obsidian vaults the user has synced into their Second Brain: note counts, the folders each vault holds, its most-used tags, and when it last synced.

Search the notes synced from the user's Obsidian vault, by keyword and by meaning, and get back where each one lives in the vault with an excerpt around the match.

Browse the user's synced Obsidian notes without a search term — most recently changed first, optionally within one vault, one folder, or one tag.

Read one note from the user's Obsidian vault in full: its markdown, frontmatter, tags, the notes and brain objects its wikilinks point at, and the notes that link back to it.

Search for companies by describing them in plain English — the same engine behind the ProspectFinder app.

Search the Slack messages saved to the user's brain — by keyword and by meaning — newest first.

The saved messages of one Slack thread, oldest first: the parent and every reply the brain holds.

The Slack channels and DMs the user's brain knows about, per connected workspace, with whether each one is being saved (ingest) and how many messages are stored.

Post a message to a Slack channel or DM as YouSpot, optionally as a reply in a thread.

Add an emoji reaction (by name, e.

The user's own tweets, newest first, from their connected X (Twitter) accounts — text, engagement metrics (likes, replies, retweets, impressions), date, and link.

Live profile stats for the user's connected X (Twitter) accounts — name, @handle, follower count, following count, and total tweets, fresh from the X API.

Accounts the user follows on X (Twitter), from the synced follow graph — name, @handle, and bio.

Fetch and read the content of one public web page by URL — use when the user asks what a page or article says, or you need to read a prospect's or company's own site before a conversation.