Available Integrations
Last updated 1 day ago
Available Integrations
Liza connects to third-party systems in two ways:
- Native providers — integrated directly into Liza (OAuth, API key, or app password), with incoming webhooks / polling and, in some cases, two-way sync.
- Unified.to — a hub for many additional providers per category via a generic connect flow (see Integrations (REST)).
Native providers
Connection types: OAuth (log in with the provider), API key (token/subdomain or app-specific password) and Inbound (Liza provides a webhook URL that you register with the provider).
The Status column shows whether a provider is already enabled (✅ live, connectable in the Liza settings) or in preparation (🟡 planned, not available yet). Only ✅ live providers should be named to users as available — some planned ones already have an entry in the client, but connecting does not work yet.
Availability depends on the environment
An OAuth provider only appears in the client once OAuth credentials are configured for that environment — the catalogue is filtered server-side. When in doubt, check Settings → Users & apps → Integrations for what is actually offered. On top of that the plan caps the number of connected services (Free: 5).
INFO
Some providers are read-only/poll-based (e.g. MOCO, Apple CalDAV), others support two-way actions (e.g. Sentry: close an issue). The exact feature set is shown in Liza when connecting.
Connections can be attached to a list or to a single item; the events then land as blocks in that chat.
Unified.to Categories
Through the connect flow, many additional providers are also available per category:
crm, ticketing, calendar, messaging, storage, task, ats, accounting, ecommerce, hr, enrichment, marketing.
The MCP server exposes tools for these, such as search_crm_contacts, list_tickets, list_messaging_channels, search_files, list_external_tasks, and the generic unified_api_call — visible as soon as a matching connection exists.