Build with Bridge.

Get the activity history (emails, meetings, calls, notes) for a specific contact. Use when the user asks about past interactions, communication history, or "when did I last talk to…". Pass the contact UUID — if you only have a name, call bridge_contacts_search first.

Log an activity (email, meeting, call, note, message, SMS, WhatsApp) for a contact. Use when the user says they had a meeting, call, message, or interaction with someone and wants to record it. Also the default way to save a new fact or update about a person ("he is leading a new fund"): use type NOTE. It appends to their timeline and never overwrites existing notes. Put where you met in the subject ("Met at UCLA Anderson demo day") so it is searchable. occurredAt defaults to now; for an earlier time pass ISO 8601 with the user's UTC offset. Pass the contact UUID — call bridge_contacts_search first if you only have a name.

Get open commitments (promises/action items) the user has made or that others have made to them. Use when the user asks "what do I owe?", "what have I promised?", "what does [contact] owe me?", "what are my open commitments?", "what do I need to follow up on?". Returns commitments AI-extracted from emails, meetings, and notes. Pass the contact UUID for the optional contactId filter — call bridge_contacts_search first if you only have a name.

Create a new contact. Call bridge_contacts_search first and reuse an existing contactId; ask before creating from a first name. displayName required. Optional: email, phone, company, title, location, notes, meetingContext, education, tags, linkedinUrl, websiteUrl, githubUsername, xHandle, instagramHandle. Copy name and company exactly as given. meetingContext = where you met. Applies immediately; undoable for 24h in Bridge. If deduplicated=true, the fields in notApplied were NOT saved; record them with bridge_activity_log. Pass the returned contactId to bridge_deals_create. Set education on school+year info ("Brown 2027") — seeds enrichment. A social URL goes in its matching field. bio, birthday, photo, custom fields cannot be set here. Tags: bridge_tags_manage. CRITICAL: only set email/phone/any social field when the user EXPLICITLY names BOTH the field and the value. NEVER infer from vague language, memory, or earlier search/OSINT — a wrong identity silently attaches another person. If asked to find a link, ask the user to paste it.

Get the full profile for a specific contact by UUID. Use after bridge_contacts_search to retrieve detailed information about a person, or when the user asks for details about a specific contact. Pass the contact UUID — call bridge_contacts_search first if you only have a name.

Search the user's contacts by name, company, school, location, role, or keywords. Use when the user asks about people in their network, wants to find contacts matching criteria, or asks "who do I know at…" style questions. Also call it before creating or updating anyone, to reuse the existing contactId: name matches any part of the stored name, so if the full name finds nothing try the surname alone. contextKeywords match notes, meeting context and logged activity text (e.g. who the user met at an event). Each keyword is a case-insensitive substring and any one match counts, so pass the most specific phrase ("demo day") rather than broad words.

Send one of the user's contacts to another Bridge user. The transfer is pending until the recipient accepts/declines or it expires (30 days). Both sides see status via bridge_contacts_transfers_list.

Accept a pending contact transfer sent to you. The contact is added to your CRM, deduplicated against anyone you already know.

Decline a pending contact transfer addressed to you. The sender sees the decline; no contact is added.

List pending and historical contact transfers involving the user. direction=inbox (received), outbox (sent), or all.

Update a contact's profile fields. Use when the user explicitly tells you to change a field on a specific contact. Allowed fields: company, title, location, education, bio, notes, birthday, email, phone. CRITICAL: only set email or phone when the user explicitly names BOTH the field and the new value (e.g. "set Sarah's email to sarah@new.co"). NEVER infer email/phone changes from vague language ("looks like Sarah moved jobs"). Only change company or title when the user states the new value, and copy it exactly. notes REPLACES the whole existing note: to add a fact, meeting or update about someone, use bridge_activity_log instead, and set notes only when the user asks to rewrite the note. The name cannot be changed here. For tags, use bridge_tags_manage. Pass the contact UUID — call bridge_contacts_search first if you only have a name.

Create a new deal in a pipeline. Pass the pipeline UUID, stage UUID, and title. Optionally link a contact (UUID). Use bridge_pipelines_list to resolve pipeline/stage IDs and bridge_contacts_search to resolve contact IDs.

List the user's deals. Optionally filter by pipeline UUID, stage UUID, contact UUID, or status. Use when the user asks "what deals do I have", "show my pipeline", or "deals with [contact]". Pass UUIDs for filters — call bridge_pipelines_list first to resolve pipeline/stage names, bridge_contacts_search for contact names.

Move a deal to a different stage in its pipeline. Use when the user says "move [deal] to [stage]", "[deal] won", or "mark as closed". Pass the deal UUID + target stage UUID — call bridge_deals_list first to resolve the deal, bridge_pipelines_list to resolve the stage.

Retrieve emails the user has recently forwarded to their Bridge inbox address (e.g. u_xxx@in.bridge-ai.social). Use when the user asks: "did you get the email I forwarded?", "check my forwarded mail", "what just came in", "show me the email I sent over". Returns sender, subject, snippet, matched contact (if any), and reply links. If nothing is returned, tell the user no recent forwards arrived and surface their forwarding address so they can verify they sent it to the right place.

Record what the user is looking for (an 'ask') on their networking profile, so the matcher can surface relevant people. Use when the user (via their own connected agent) states something they want — e.g. 'looking for a technical co-founder', 'raising a seed round', 'want intros to fintech operators'. This writes the USER'S OWN ask — never another person's. Pass a concise `what`; optionally a `why` for context.

Record something the user can offer or help with (an 'offer') on their networking profile, so the matcher can surface people who need it. Use when the user (via their own connected agent) states something they can give — e.g. 'happy to advise seed-stage founders', 'can intro to VCs', 'offering design feedback'. This writes the USER'S OWN offer — never another person's. Pass a concise `what`; optionally a `why` for context.

Set a single field on the user's OWN networking profile so the matcher has self-authored context. Use when the user (via their own connected agent) states a profile fact about THEMSELVES — e.g. their title, company, industry, bio, expertise, or what they're open to. Allowed fields: displayName, title, company, industry, location, bio, expertise, openTo, email, phone, linkedinUrl, twitterUrl. High-sensitivity fields the user has locked (e.g. email/phone) will be rejected — that is expected; ask the user to edit those in the app. This writes the USER'S OWN profile only.

Create a pipeline with its stages. Pass a name and a type; omit `stages` to seed the standard stages for that type, or pass your own ordered list. Optionally attach the pipeline to a Project by UUID. Call bridge_pipelines_list afterwards (or read the returned stage UUIDs) to file deals into it.

List the user's sales/investor pipelines with their stages. Use when the user asks 'what pipelines do I have', 'show me my pipelines', or before referring to a specific pipeline by name.

Summarize a sales pipeline by stage with deal counts and total value. Use when the user asks 'show my pipeline', 'how is X pipeline doing', or compares stages. Returns each stage with deal count, total value, and top deals.

Search the user's private imported event, trip, cohort, or list contexts and return the contacts attached to each context with exact relationship classifications. Use for questions like "who was listed in X?" or "who was on X trip/cohort?". LISTED_ONLY means the person only appeared in the imported source. Shared context never means participants know each other.

Create a reminder for the user. Use when the user asks to be reminded about something — following up with a contact, a deadline, or any future task. dueAt is an exact time: resolve relative dates like "next Tuesday" from today in the user's time zone, use 9:00 local if no time was given, and pass it with that UTC offset (2026-10-13T09:00:00-07:00). Ask the user if you do not know their time zone. Pass the contact UUID for the optional contactId — call bridge_contacts_search first if you only have a name.

Add or remove tags on a contact. Use when the user says "tag [contact] as [x]" or "remove the [x] tag from [contact]". Pass the contact UUID — call bridge_contacts_search first if you only have a name. Provide at least one of addTags / removeTags.

Find warm introduction paths to a target contact. Returns people who know the target well, split into "Ready" (strong on both sides — you can ask for the intro) and "Opportunity" (they know the target well but you need to build your relationship with them first). Use when the user asks "how can I get introduced to X?", "warm intro to X", "who can introduce me to X?", "do I have any mutual connections with X?". Pass the target contact UUID — call bridge_contacts_search first if you only have a name.