API USE CASE

Structured catalog navigation

Your agent can walk categories or the category tree so humans and agents browse the portfolio the same way your CPQ is organized.

How you set it up

Read/brief walkthrough
  1. What you can do today. Have Claude navigate category structure in Salesbuildr and brief you before catalog recommendations go further, 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 category and category/tree reads so browsing matches how your CPQ organizes the portfolio. Paths: GET /category, GET /category/tree.
  4. Keep humans in the loop for decisions. Catalog navigation informs recommendations; commercial decisions stay with your team.

What you can do today
This example shows Claude navigating category structure in Salesbuildr and briefing you before catalog recommendations go further.

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 /category and GET /category/tree. 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.