API USE CASE

On-brand building blocks

Your agent can inventory quote templates and quote widget templates, the reusable sections and layout rules behind consistent proposals.

How you set it up

Read/brief walkthrough
  1. What you can do today. Have Claude inventory quote templates and widgets in Salesbuildr and brief you before sections are reused, 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 quote-template and quote-widget-template reads so proposals stay on-brand with reusable sections. Paths: GET /quote-template, GET /quote-widget-template.
  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 inventorying quote templates and widgets in Salesbuildr and briefing you before proposal sections are reused.

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 /quote-template and GET /quote-widget-template. 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.