> For the complete documentation index, see [llms.txt](https://docs.uptiq.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.uptiq.ai/agent-builder/build/apps-and-services.md).

# Apps & Services

**Apps & Services** is the catalog of pre-built integrations with third-party SaaS products — email senders, payment processors, messaging platforms, and similar. Each entry in the catalog is a ready-to-connect integration: the platform supplies the connector, you supply the credentials, and the agent gains the ability to take actions in that service through skills the connector exposes. Use this page to give the agent reach into systems your business already runs on, rather than authoring an API Call skill from scratch.

Manage Agent → Apps & Services catalog

Reach this page from **Manage Agent → Integration Tools & Connectors → Apps & Services** in the left navigation.

### The catalog <a href="#the-catalog" id="the-catalog"></a>

The right pane lists the available integrations. Each row carries:

* The service's logo
* The service's name (for example, `Resend Email`, `Stripe`, `Twilio WhatsApp`)
* A one-line description of what connecting will let the agent do
* A `Connect` button revealed on hover, on the far right

The catalog observed during capture included Resend Email, Stripe, and Twilio WhatsApp. The full catalog can be larger; use the search box at the top right of the pane (`Search integrations…`) to find a specific service quickly.

> **Note** The `Connect` button is hidden until you hover over the row. On touch devices without hover, the row itself may need to be tapped to reveal the button. This is worth knowing if you can't find an obvious affordance for adding an integration.

### Connecting an integration <a href="#connecting-an-integration" id="connecting-an-integration"></a>

Hover the row and click **Connect**. The platform initiates the integration flow for that service — typically an OAuth handshake, sometimes a credentials form. Once authorized, the integration becomes available to the agent through whatever skill or capability that connector exposes (some connectors register one skill; some register several).

> **Note — Depth gap** The post-Connect flow (OAuth handshakes, credential forms, the per-service capabilities surfaced after connecting) was not exercised during capture. Each integration's connect-flow detail is queued for a future capture pass.

### Where connected integrations show up <a href="#where-connected-integrations-show-up" id="where-connected-integrations-show-up"></a>

After connecting an integration, you'll see effects in three places:

* **The Layout canvas** — the integration may appear as a new node in the Skills band, similar to the MCP connector discs.
* **Skills & Capabilities** — the skill (or skills) the integration registers will show in the agent's skill list.
* **The agent's responses** — at runtime, the agent can invoke the connected service through the registered skill.

### Apps & Services compared to MCP Tools <a href="#apps-and-services-compared-to-mcp-tools" id="apps-and-services-compared-to-mcp-tools"></a>

Both **Apps & Services** and **MCP Tools** add external capability to the agent. The distinction:

* **Apps & Services** catalogs pre-built integrations with SaaS products. The connector is supplied by the platform; you supply credentials.
* **MCP Tools** catalogs Model Context Protocol servers — a more general protocol for connecting external tools. Some entries in the MCP catalog are also SaaS connectors; others are data APIs (CoinAPI, Alpha Vantage), search APIs (Tavily), or knowledge-base retrieval (AWS Knowledge Base).

When the action you want to give the agent involves a recognized SaaS product (sending email through Resend, charging through Stripe), check Apps & Services first. When it involves a data API or a more generic tool, MCP Tools is the right catalog.

### Why this matters <a href="#why-this-matters" id="why-this-matters"></a>

Most useful agents need to reach beyond text generation — to send a confirmation email, to log a record in a system of truth, to query a live data source, to message a user on a different channel. Apps & Services makes that reach a configuration step rather than a coding step. Every integration you connect here is one less skill you'd otherwise author yourself, and one less custom auth flow you'd otherwise maintain. The trade-off is that the catalog covers what the catalog covers — for services not in the catalog, the API Call skill type remains the general-purpose escape hatch.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.uptiq.ai/agent-builder/build/apps-and-services.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.