> ## Documentation Index
> Fetch the complete documentation index at: https://docs.yourhomie.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Introduction

> Give your assistant the ability to take actions and fetch live data during a chat with organization-wide tools.

<CardGroup cols={2}>
  <Card title="HTTP Tool" icon="wrench" href="/en/user-guide/tools/custom-tools">
    Create an HTTP request tool that lets the assistant fetch live data or take an action mid-chat.
  </Card>

  <Card title="Email tool" icon="envelope" href="/en/user-guide/tools/email-tool">
    Let the assistant send emails from a verified sender during a chat.
  </Card>
</CardGroup>

Tools extend what your assistant can do during a conversation. Out of the box, the assistant answers from your knowledge. With tools, it can also **take actions** and **fetch live data** — for example, look up an order's current status, check stock, or send an email — by calling an HTTP request you configure or by sending email from your verified sender.

Tools are defined once at the **organization** level and then **assigned to the assistants** that should use them. When a shopper's question matches what a tool does, the assistant calls the tool, uses the response, and continues the conversation naturally.

## How tools work

* A **HTTP tool** describes an HTTP request: a URL, method, headers, and parameters the assistant fills in.
* The **email tool** sends email from a sender you have set up.
* You **test** a tool before it goes live, so you know the request and response are correct.
* You **assign** a tool to each assistant that should use it. Once assigned, the assistant decides when the tool is relevant and calls it on its own during a chat.

## Two ways to build a tool

On the platform, open **Tools** and select **New tool**. From there you can:

* Start from scratch by choosing a type — **HTTP Request** or **Email**.
* Start from a ready-made **template**, such as *Shipment tracking*, *Lead capture*, or *Handover to support*, and adjust it to your needs.

## Credentials and security

Tools often need to talk to authenticated systems. Keep credentials out of the tool definition itself:

* **Secrets** store API keys and other sensitive values that tools reference without exposing them in plain text. See [Settings › Secrets](/en/user-guide/settings/secrets).
* **Auth connections** handle authentication — including OAuth — so a tool can act against a third-party service on your behalf. See [Settings › Auth Connections](/en/user-guide/settings/auth-connections).

## Availability

<Note>
  Whether Tools are available, and how many HTTP tools you can create, depends on your plan. When you reach the limit, delete a tool you no longer need or upgrade your plan.
</Note>

## Next steps

<CardGroup cols={2}>
  <Card title="Create an HTTP tool" icon="wrench" href="/en/user-guide/tools/custom-tools">
    Configure, test, and assign an HTTP request tool step by step.
  </Card>

  <Card title="Set up the email tool" icon="envelope" href="/en/user-guide/tools/email-tool">
    Send emails from the assistant using a verified sender.
  </Card>
</CardGroup>