Connectors
Last updated About 2 hours ago
Connectors
Formerly "Integrations"
What Liza now calls a connector used to be called an integration. It is the same thing; only the wording in the interface changed.
Connect Liza with the tools you already use – calendars, developer tools, CRM, monitoring, and more. Events from connected services land as blocks in the chat of a list or a single task.
What can be connected
Depending on the provider you connect via login (OAuth), API key, app-specific password, or webhook URL.
In preparation
Linear, Jira, Asana, HubSpot, Google Workspace and Microsoft 365 exist but are not usable yet — even though the client may already show an entry. The current state is listed under Available Connectors.
Not everything is visible everywhere
Only what is actually connectable in your environment is offered. On top of that, your plan caps the number of connected services (Free: 5).
Connecting
There are two ways:
- Settings → Users & apps → Connectors or Settings → Personal → Connected apps – for connections that persist.
- Inside a list: via "Add connector" – the events of that service then flow into this list's chat. With "Link external source" you attach them to a single task instead.
Some providers are read-only or poll-based (e.g. MOCO, Apple CalDAV), others support two-way actions (e.g. Sentry: close an issue). The exact feature set is shown when connecting.
Your own connectors
For services Liza does not ship with, you build a connector yourself – with nothing for us to release. Your own connector can do two things, separately or together:
- Receive events – the other service sends a webhook, and a block appears in the chat of a list.
- Run actions – Liza calls the service's API, for example to create a record or restart something.
Settings → Own connectors – an entry of its own next to Connectors, not inside it. It only shows for admins and owners, and only if the plan allows own connectors.
Three ways to build one
All three go through the same validation. What the assistant produces can be edited as JSON afterwards, and the other way around.
Draft first, then active
A new connector starts as a draft and receives nothing yet. Before you activate it, the check step shows what a sample response would actually become – which event entry matches, and which block comes out. That is worth doing: a definition can be formally correct and still point at the wrong fields.
The states are draft, active, and switched off. Switching off stops reception without losing the definition.
What to know
- Own connectors require Pro. They count against your plan's quota like any connected service.
- Credentials are not part of the definition. Tokens and passwords live in the connection, as with any other connector. Whoever reads the definition sees no secrets.
- No code. A definition is descriptive text (JSON), not a program. It can only do what the format provides for – map fields, fill templates, make requests.
- The AI can operate connectors too if you ask it to – create, check, and trigger actions. The tools are documented under MCP tools: connectors.
Entry missing?
Two things have to come together: the feature must be released for your environment, and the plan must allow it. If either is missing, the menu entry does not appear at all – rather than letting you fill in a form that is rejected on save.
More providers (for developers)
Through the generic connect flow many more providers are reachable per category (CRM, ticketing, calendar, messaging, storage, tasks …) – see Available Connectors.
For developers
You can build your own automations and integrations using the Public API, Webhooks, and Zapier hooks.