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
| Provider | ID | Categories | Connection |
|---|---|---|---|
| GitHub | github | repo, task | OAuth |
| Jira | jira | task, project | OAuth |
| Linear | linear | task, project | OAuth |
| Asana | asana | task, project | OAuth |
| HubSpot | hubspot | crm, marketing | OAuth |
| Salesforce | salesforce | crm | OAuth |
| Google Workspace | google | calendar, mail, storage | OAuth |
| Microsoft 365 | microsoft | calendar, mail, storage | OAuth |
| Stripe | stripe | payments, billing | OAuth |
| Sentry | sentry | monitoring, errors | OAuth |
| AppSignal | appsignal | monitoring, errors, performance | API token |
| MOCO | moco | time-tracking, project, billing | API key (subdomain) |
| Apple Calendar | apple_caldav | calendar | App-specific password |
| Zapier | zapier | automation | REST hooks (Docs) |
| n8n | n8n | automation | REST hooks |
| Custom Webhook | custom | webhook, integration-hub | Webhook URL |
INFO
Some providers are read-only/poll-based (e.g. MOCO, Apple CalDAV), while others support two-way sync (e.g. Sentry: close an issue; AppSignal). The exact feature set is shown in Liza when you connect.
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.