---
title: Integration Tools
subtitle: Tools powered by connected third-party services
slug: how-to-tools-integration-tools
section: Tools
description: Learn how urvo integration tool instances are created, synced, and executed via urvo and your backend proxy.
---

## Overview

Integration tools let your agent take actions in connected services like CRMs, calendars, support platforms, and productivity apps.
urvo manages and handles all integration tools for you.
Integration tools can be added once the integration has been added in the user's workspace.

## End-to-end flow

1. Connect your service via **Integrations** (OAuth or API key, depending on provider).
2. Once connected in your workspace, enable the specific integration tools you want.
3. Add those integration tools to an agent from the dashboard.
4. During a call, urvo handles the tool execution by resolving credentials and calling the underlying integration API.

## What gets created under the hood

When you enable an integration tool, urvo creates an **integration tool instance** tied to:

- the integration tool template (the action definition)
- your workspace connection (credentials + account context)

It also creates a corresponding workspace tool record so the tool appears in the Tools list and can be synced to agents.

## Integration proxy flow

Integration tools run through urvo using a webhook-style proxy endpoint:

`/api/v1/integrations/webhook/{workspace_id}`.

The proxy uses the tool identifier sent in the request to locate the correct tool instance and then:

- resolve credentials
- build the request (base URL + endpoint + template-defined schemas)
- apply provider-specific request transformations
- return the response back to the calling flow

## Tool name mapping

In practice, the proxy looks for the tool name in either the **request headers** or the **JSON payload** (depending on the webhook format).
That tool name is what links the webhook call back to your enabled integration tool instance.

## Request parameter schema

Each integration tool template defines how urvo should collect parameters from the transcript.
That schema can include query parameters, path parameters, and request body structure.

## Next steps

- Learn how to configure conversation control with [Built-in Tools](/how-to/tools/built-in-tools).
- If you want direct control over an HTTP endpoint, see [Webhook Tools](/how-to/tools/webhook-tools).