Connecting your systems

The agent acts, not just answers.

Function tools, web tools, and MCP servers, so a call can check a balance, place an order, or book a slot in your systems while the caller waits.

01

Three kinds of tool

Function tools give you full control over URL, method, headers, authentication, and timeout. Web tools cover simpler HTTP calls. MCP tools connect an external server that manages its own catalogue of functions, which is useful when a system already exposes one.

02

Responses become variables

Output mapping pulls fields out of the HTTP response using JSONPath and names them as flow variables, so the next node can speak the customer's balance or branch on their plan. Values are only set when the call succeeds; the failure path is designed separately, on purpose.

03

Overrides per node

The same tool can behave differently at different points in a flow: a different endpoint, extra headers, an added query parameter. Overrides live on the node, so one tool definition serves many uses without being duplicated.

04

Test before you wire

Every tool can be run against the real endpoint from the platform before it is attached to a node. You see the response and the mapping, rather than discovering an auth problem mid-call.

The spec

TypeControl you have
FunctionURL, method, headers, params, auth, timeout. Full control
Web toolSimplified HTTP call, parameters only
MCPServer-managed catalogue, available across the workflow

More capabilities

Partner ecosystem

Trusted Across the
Technology Ecosystem

Hamsa works with leading technology companies, integrators, and solution providers to bring enterprise Voice AI to organizations across the region.