Order status
Without Sanka
The customer record may not include the latest fulfillment state.
With Sanka
Breeze calls Sanka's order API and returns the current status.
Connect HubSpot Breeze to live order and billing data
Let HubSpot Breeze customer agents answer order, delivery, inventory, and billing questions by calling governed Sanka APIs instead of relying on incomplete CRM fields.
Ask anything...
Breeze Integration
Changes will appear here
Trusted by 1,000+ teams
Overview
Give Breeze the back-office context it needs
Customer agents with real context
Breeze can respond with current order status, delivery state, billing context, and other operational details stored in Sanka.
Governed API actions
Expose only the Sanka endpoints and fields each agent needs, with API keys, permission boundaries, and action protection levels.
Back office stays in Sanka
Keep orders, inventory, delivery, invoices, and accounting workflows in Sanka while HubSpot remains the customer engagement layer.
Workflow
How the Breeze action connects to Sanka
- 01Open the customer agentStart from HubSpot Service Hub and open the Breeze customer agent action settings.
- 02Create the order lookup actionAdd trigger phrases and define the order reference field the agent should collect from the customer.
- 03Connect the Sanka APISet the GET endpoint, pass the order reference into the URL, and store the Sanka API key as a HubSpot secret.
- 04Protect the actionChoose the action protection level and keep the returned fields limited to what support should see.
- 05Test the responsePreview the agent, provide a customer email and order number, and confirm Breeze returns the Sanka order status.
Compare
Why Breeze needs a back-office data layer
| Workflow | Without Sanka | With Sanka |
|---|---|---|
| Order status | The customer record may not include the latest fulfillment state. | Breeze calls Sanka's order API and returns the current status. |
| Delivery timing | Delivery updates stay with operations or inventory teams. | Sanka exposes delivery and shipping context to the agent. |
| Billing questions | Invoices, balances, and payment status live outside the support view. | Billing and AR records can be referenced through governed Sanka endpoints. |
| Action safety | A generic agent action can leak too much data or run without review. | Sanka keeps API scope, permissions, logs, and approvals around the workflow. |
| Operations handoff | Support teams still open another system or ask operations manually. | The agent answers first and escalates exceptions with context. |
Delivery timing
Without Sanka
Delivery updates stay with operations or inventory teams.
With Sanka
Sanka exposes delivery and shipping context to the agent.
Billing questions
Without Sanka
Invoices, balances, and payment status live outside the support view.
With Sanka
Billing and AR records can be referenced through governed Sanka endpoints.
Action safety
Without Sanka
A generic agent action can leak too much data or run without review.
With Sanka
Sanka keeps API scope, permissions, logs, and approvals around the workflow.
Operations handoff
Without Sanka
Support teams still open another system or ask operations manually.
With Sanka
The agent answers first and escalates exceptions with context.
Customer quotes
Don't take our word for it.
We want inventory, sales management, tax, and accounting to connect smoothly while keeping operating cost and time low.
Sanka does more than inventory control. It can manage purchasing, billing, orders, and shipping in one place.
By implementing Sanka, we expect to connect reel racks with shop-floor inventory data so we can calculate requirements based on accurate stock.
FAQ
Frequently asked questions
Does this require replacing HubSpot?
No. HubSpot remains the customer engagement layer. Sanka supplies the operational data and governed API actions behind the agent.
Which Sanka records can Breeze reference?
Start with orders, delivery status, inventory, invoices, and payment status. The exact endpoints and fields should match the support use case.
How do we keep agent actions safe?
Limit endpoint scope, store API keys as secrets, use HubSpot action protection, and keep Sanka logs and permissions around the operational records.
Can this support more than order lookup?
Yes. The same pattern can expand to delivery updates, invoice status, return eligibility, purchase status, and other back-office records.