API USE CASE

Governed price lists & discounts

Your agent can list pricing books and read quote discount groups so guidance stays on approved lists and policies, not invented in chat.

How you set it up

Read/brief walkthrough
  1. What you can do today. Have Claude look up price lists and discount groups in Salesbuildr and brief you before pricing guidance goes out, bring your own agent in your Azure / tenant so Salesbuildr does not need blanket access to mail, Teams, or calendar.
  2. Salesbuildr Public API access. Issue scoped credentials and authenticate with the api-key header on your tenant’s /public-api base.
  3. Endpoint families for this scenario. This scenario uses pricing-book and quote-discount-group reads so price and discount guidance stays governed. Paths: GET /pricing-book, GET /quote-discount-group.
  4. Human review before send. Use the agent to brief and draft from CRM/CPQ truth; keep a person in the loop before anything goes to the customer.

What you can do today
This example shows Claude looking up price lists and discount groups in Salesbuildr and briefing you before pricing guidance goes out.

What the API can do
Salesbuildr’s Public API also lets you create and update records, and soft-delete (unlist) where supported, details in the API reference / Public API help.

Writing through Claude
Step-by-step Claude recipes for creating quotes or moving deals aren’t published here yet. Ask on a demo if you want that path. A person should still review before anything reaches a customer.

What that looks like

Live example

Illustrative session, fictional Acme MSP sample data only. Your agent 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 GET /pricing-book and GET /quote-discount-group. Fictional placeholders only.

See this with your stack

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