Agent Builder examples

Copy and adapt these prompts in Agent Builder. Each example assumes you have admin access and existing resources named as shown.

Assistant configuration

Update master prompt

Update the "Website Support" assistant master prompt:
- Answer only from attached knowledge bases and tools
- Always cite document titles
- If the question is about billing, offer to connect with a human
Show me the diff before saving.

Change model

Switch "Website Support" to GPT-5.4 mini for lower latency.
Keep all other settings the same.

Knowledge bases

Attach KB to assistant

Attach the "Help Center" knowledge base to the "Website Support" assistant.
Confirm the attachment list when done.

Trigger re-index

Re-index the "Product Catalog" knowledge base — we uploaded 12 new PDFs today.
Tell me when indexing status is ready.

Tools

Add order lookup tool

Create an API tool called get_order_status for "Website Support":
- GET https://api.ourstore.com/orders/{order_id}
- Use the "Production API" credential
- Required param: order_id (string)
- Description: Look up order status for a customer
Show me the tool config before creating.

Attach existing tool

Attach the "check_inventory" tool to "Sales Assistant".
Test it with SKU "WIDGET-42" and show me the result.

Deployments

Widget appearance

For the "Production Widget" deployment:
- Primary color #F97316
- Greeting: "Welcome! Ask us anything about your order."
- Add suggested question: "Where is my package?"
Preview changes before applying.

Allowed domains

Add https://staging.ourstore.com and https://*.ourstore.com to the
Production Widget allowed domains list.

Multi-step workflows

New assistant from scratch

Create a new assistant "Returns Bot":
1. Model GPT-5.4 mini
2. Attach "Returns Policy" knowledge base
3. Master prompt focused on return eligibility and timelines
4. Attach get_order_status tool
Walk me through each step and wait for confirmation.

Audit before go-live

Review the "Website Support" assistant configuration:
- List attached KBs and tools
- Flag anything missing for a customer support use case
- Do not change anything without asking

Tips

Tip	Why
Name resources explicitly	Avoids ambiguity across assistants
Ask for diffs	Review before confirming writes
One major change per turn	Easier to undo if needed
Say “do not save yet”	Agent Builder will plan without writing

Related

• Confirmations
• Undo
• Limits