Book a demo
← API & Agents · Use cases
API USE CASE

Opportunity from conversations

Your agent can turn email, calendar, and call transcript context into a proposed Salesbuildr opportunity Upsert, put the customer ask in description (and custom fields if relevant), so the rep doesn’t retype what already happened.

Book a demo Back to API & Agents

How you set it up

Read/brief walkthrough
  1. Bring your own agent for conversations. Connect email, calendar, and call transcripts with the tools your team already uses (customer-controlled). Salesbuildr does not natively pull Fireflies, Modjo, or Gmail. Your agent brings that context, then talks to Salesbuildr over the Public API.
  2. Salesbuildr Public API key. In Salesbuildr (Admin): Settings → Integrations → API Key, create or regenerate the key, then send it as header api-key on your tenant’s /public-api base. Learn more: Public API help.
  3. Opportunity read + Upsert. Use Search / Get to read the opportunity; Upsert by external ID (including custom fields) to write proposed changes, include a contact and an owner, keep probability on a 0–1 scale (not percent), and put the customer ask in description; Win / Lose for status. (There is no separate “Update” operation name. Upsert is the write path.) Opportunity Notes in the product UI are for in-app timelines, they are not writable via the Public API yet (API timeline notes: coming soon / ask on a demo).
  4. Human review before apply or send. Have the agent propose opportunity changes from conversation context; a person reviews before Upsert / Win / Lose is applied, and before anything goes to the customer.

What you can do today
This example shows Claude reading a Salesbuildr opportunity and proposing an Upsert grounded in fictional email, calendar, or transcript context, especially the customer ask in description, for your review before anything is applied or sent.

What the API can do
Salesbuildr’s Public API also lets you create and update records, opportunity Upsert by external ID (including custom fields; contact and owner required; probability 0–1; description = customer ask), plus Win / Lose, and soft-delete (unlist) where supported. Opportunity Notes in the UI are not Public API–writable yet; API timeline notes are coming soon, ask on a demo. Details in the API reference / Public API help.

Writing through Claude
Step-by-step Claude recipes for upserting opportunities aren’t published here yet. Ask on a demo if you want that path. A person should still review before opportunity changes are applied or anything reaches a customer.

What that looks like

Live example

Illustrative session, fictional Acme MSP sample data only. Your agent uses its own email/calendar/transcript tools, then talks to Salesbuildr over the Public API.

Agent ↔ Salesbuildr Example session

Try this prompt

Paste into Claude (or another HTTP-capable agent) after you wire the Salesbuildr Public API. Uses Search / Get opportunity to read; Upsert by external ID is available for writes (description = customer ask). Fictional transcript context only. Propose, don’t apply writes in this self-serve walkthrough.

How to try this with Claude →

See this with your stack

Book a short demo, explore how your agent of choice could work with Salesbuildr for this use case.

Book a demo All use cases