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

# Apps

> Slack, Microsoft Teams, Zendesk, Freshdesk, Shopify and Stripe: what connects and what each one does.

Beyond your [CRM](/integrations/crm) and your [calendar](/integrations/calendars), these apps
connect under **Settings, then Integrations**.

## Slack

Connect your Slack workspace and pick which channel escalations and alerts post into.

The connection is a single authorisation that covers both posting alerts and choosing a channel, so
you do not have to create and paste a webhook URL by hand. An escalation destination set to Slack
without naming a channel uses the connected workspace's default.

Slack is an alert destination rather than a full team assistant. To reply to customers and act on
your workspace from chat, see [Telegram](/assistants/telegram).

## Microsoft Teams

Teams is an alert destination. Escalations and alerts arrive as a card with the details and a link
into the conversation.

Connecting Teams means creating a workflow in Teams that accepts incoming posts and pasting its
address into Vorel. The console tells you exactly which of Microsoft's several similar-looking
mechanisms to use, because picking the wrong one produces a connection that appears to work and
silently delivers nothing.

## Zendesk and Freshdesk

Connect your existing helpdesk so conversations that need a ticket become one, and so your agents
keep working in the tool they already use.

## Shopify

Connect your store so the agent can answer questions about orders and products from real data rather
than from a static knowledge entry that goes stale every time your catalog changes.

## Stripe

Connect Stripe for payment collection during a conversation. Payments run through a redirect to the
payment provider's own hosted vault, so card details never touch Vorel. See
[Payments](/security/payments).

## Product analytics

Segment, Amplitude, PostHog and Mixpanel connect as [trigger sources](/automation/triggers) rather
than as apps, because what you want from them is the ability to act on a product event. Connect them
in the Sources tab of the trigger studio.

## Anything else

Two general-purpose routes:

* **[Webhooks](/integrations/webhooks)** push Vorel's events to your endpoint
* **[The API](/api-reference/introduction)** lets you pull and write

And for AI clients specifically, the [MCP endpoint](/assistants/mcp) exposes your workspace directly.