Available Integrations

Last updated 24 days 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 ​

ProviderIDCategoriesConnection
GitHubgithubrepo, taskOAuth
Jirajiratask, projectOAuth
Linearlineartask, projectOAuth
Asanaasanatask, projectOAuth
HubSpothubspotcrm, marketingOAuth
SalesforcesalesforcecrmOAuth
Google Workspacegooglecalendar, mail, storageOAuth
Microsoft 365microsoftcalendar, mail, storageOAuth
Stripestripepayments, billingOAuth
Sentrysentrymonitoring, errorsOAuth
AppSignalappsignalmonitoring, errors, performanceAPI token
MOCOmocotime-tracking, project, billingAPI key (subdomain)
Apple Calendarapple_caldavcalendarApp-specific password
ZapierzapierautomationREST hooks (Docs)
n8nn8nautomationREST hooks
Custom Webhookcustomwebhook, integration-hubWebhook 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.