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

# Product overview

# Product overview

**FinalSay** (*HITL Relay*) connects **automations** to **people** when a workflow needs a human decision. You use the same backend whether you work in the browser, on a phone, or from tools like n8n and Zapier.

## Surfaces

| Surface                              | Role                                                                                                                                                                                                                     |
| ------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| **[Web dashboard](./web-dashboard)** | Sign in, switch workspaces, create agents, generate workspace API keys, review approvals, manage team and workspace settings, and run the **Quickstart Integration** flow—all in the browser.                            |
| **Mobile app**                       | Same account and workspaces; optimized for **on-the-go approvals**, **push notifications**, and device features such as biometric unlock. See [Getting started](./getting-started) and [Mobile app (FAQ)](./mobile-app). |
| **Agent API** (`/v1/*`)              | What **automations** call with `X-Agent-Id` and `X-Api-Key`. Not your personal password. See [API overview](../api-reference/overview).                                                                                  |
| **MCP**                              | Optional protocol bridge to the same Agent API for MCP-capable clients. See [MCP](../integrations/mcp).                                                                                                                  |

Automations always use **Agent ID + workspace API key**. Those values come from the **web dashboard** or **mobile app** (workspace owners create keys).

## Typical flow

1. A workspace **owner** creates agents and (when needed) a **workspace API key**.
2. An automation sends `POST /v1/approvals` with question, context, and options. **`timeout` is optional** on REST (dashboard defaults apply; partial overrides allowed). **`request_id`** is optional; the API can assign one. [MCP](../integrations/mcp) always uses dashboard timeout defaults.
3. A human resolves the request in the **web dashboard** or **mobile app** (or both may be available to your team).
4. The automation gets the outcome via **callback** or **polling**. Details: [How it works](./how-it-works).

## Related

* [Web dashboard](./web-dashboard)
* [Getting started](./getting-started)
* [Credentials](./credentials)