Business Tools Overview

Business Tools are workspace-scoped connectors that let Qefro assistants execute actions in your systems — order lookups, ticket creation, inventory checks, subscription changes, and more.

The AI does not call your APIs directly. Every action flows through the shared Business Tool runtime, whether the tool is implemented as REST/OpenAPI or as a Backend SDK handler.

Knowledge Base vs Business Tools

Capability	Knowledge Base	Business Tools
Data source	Documents, websites, uploaded files	Your live APIs / backend handlers
Answers	Static or indexed content	Real-time system of record
Examples	“What is your return policy?”	“Where is order ORD-1002?”
Auth	Workspace content access	Per-tool credentials + optional end-user identity
Changes	Re-index when docs change	Re-test when APIs or handlers change

Most production assistants use both: RAG for policies and FAQs, Business Tools for account-specific actions.

Business Tools vs Business Actions

Term	Meaning
Business Tool	Configuration — URL, method, auth, schema, or SDK handler name
Business Action	One runtime invocation of that tool during chat

See What are Business Actions?.

Two integration paths (same runtime)

Path	When to use	Admin Console surface
REST / OpenAPI	Existing HTTPS APIs, vendor CRUD, OpenAPI specs	REST tab, OpenAPI import
Backend SDK	Customer auth, OTP, workflows, org-owned logic	SDK Connections + Sync Tools

Compare in depth: REST vs Backend SDK.
Mix both in one workspace: Mixed integrations.

Real-world examples

Use case	Typical path	Example tool
Download invoice	SDK (auth: required)	download_invoice
Create support ticket	REST POST	create_ticket
Search CRM	REST / OpenAPI	crm_contact_search
Restart server (Employee AI)	REST with scoped key	infra_restart_pod
Generate report	REST async job	report_generate
Cancel subscription	SDK + authorize	subscription_cancel
Inventory lookup	REST GET	inventory_balance_get

Runnable examples: Examples catalog.

Channels (V1)

Channel	Business Tools
Website Widget	Supported
WhatsApp	Supported
Admin Playground	Supported (test chat)
Internal Portal	Knowledge only — no END_USER_IDENTITY forwarding yet

Where to start

First Business Tool

1. Pick a workspace — Tools are workspace-scoped (e.g. Support vs HR).
2. Choose integration path — REST for existing APIs; SDK for auth-heavy flows.
3. Configure + test — Console Test Tool before enabling chat.
4. Enable for channel — Widget / WhatsApp; add identify() when needed.
5. Monitor logs — Review execution logs after pilot traffic.

Step-by-step guides

• Connect REST APIs — manual REST tool
• Import OpenAPI — bulk from spec
• Register SDK Business Tools — @qefro-ai/backend

Deep dives

• Business Tool Runtime — canonical architecture and pipeline
• Authentication
• Identity forwarding (REST)
• Identity resolution (SDK)
• Parameters reference

Note

Qefro is an orchestration runtime, not an identity provider. Your organization owns customer lookup, login, OTP, JWT issuance, and authorization. Qefro forwards identity and executes tools under your configuration.

FAQ

Do I need Business Tools on day one?

No. Many teams launch with knowledge-only Customer AI, then add tools when Q&A is stable.

REST or SDK?

REST for existing HTTPS APIs. SDK when authentication, OTP, or multi-step workflows belong in your backend. See REST vs SDK.

Where are secrets stored?

Encrypted at rest on REST tools and SDK connections. Never in widget JavaScript. See [Secrets](/docs/security/secrets).

Related topics