Current information in.
Controlled actions out.

The Integration Agent gives Web and Voice conversations access to approved business capabilities while API credentials, validation, and execution stay server-side.

One universal tool library

Connect by capability, not by industry.

These are connection patterns. Each business enables only the adapters and tools it has configured and permitted.

Typed functions that turn a customer request into a bounded task.

CapabilityReadsCan requestControl

Order and catalogueProducts, availability, order statusSearch, check, redirect, cart requestIdentity check for customer-specific data

SchedulingServices and current availabilityBook or reschedule a slotConfirmation before the final write

PaymentsPayment or invoice statusSend an approved payment pathNo raw card data; sensitive changes need approval

Lead and CRMPermitted customer and account fieldsCreate or update a lead recordExplicit public-field mapping

Use the right data path

Knowledge sync and live tools solve different problems.

Keeping them separate improves freshness, authorization, cost control, and answer quality.

Knowledge path

For descriptive information that changes deliberately.

Product descriptions, services, policies, help content, and approved public facts can sync through the knowledge pipeline.

Upsert by stable content ID
Skip unchanged content by hash
Retrieve tenant-scoped context at answer time

Live tool path

For information and actions that need authorization now.

Inventory, order status, appointments, payment state, and customer identity stay behind authenticated tools.

Validate a typed request schema
Use scoped credentials server-side
Filter the result before responding

For teams with developers

Push approved content when it changes.

@voomate/connect lets a trusted backend send public business content into the same knowledge pipeline. It retries quietly, deduplicates unchanged content, and keeps the tenant key out of browser code.

await voomate.sync({
  tenantKey: process.env.VOOMATE_TENANT_KEY,
  type: "product",
  id: product.id,
  content: publicProductContent,
  metadata: { sourceUrl: product.url }
});

A controlled connection boundary

The model requests. The backend decides.

ResolveResolve tenant
Derive tenant context from the scoped session or server key.
PermitCheck permission
Confirm that the business enabled the requested tool.
ValidateValidate input
Reject malformed or out-of-scope arguments before execution.
ExecuteExecute privately
Call the external system with server-held credentials.
FilterFilter and log
Return only safe fields and record the outcome for review.

Connect one useful tool.
Prove the full loop.

Start now See the product

Current information in.Controlled actions out.