Skip to main content
Vireon Dynamics
Vireon DynamicsLiminal AIKoLiminalUse casesConnected WorkspaceFSL-1.1-MIT · free to use

Use case · Updated 2026-06-02

Your connected workspace

Work doesn't happen in one app, so the agent shouldn't live in one. Liminal's Integrations hub connects the tools you already use. Slack, Teams, Linear, Notion, Xero, GitHub, Google, Microsoft 365, and lets one agent carry a task across all of them.

What one request can span

“Summarize yesterday's standup thread, file the two bugs people mentioned, and post the link back to the channel.” That's three tools. Slack, Linear, Slack again, and one prompt. Because every connector registers as tools inside the same agent loop. Liminal chains them with context intact instead of making you re-explain in each app.

  • Slack: read channels and threads, post messages, upload files.
  • Microsoft Teams & Planner: messages and task boards on the 365 side.
  • Linear: search, create, and update issues and projects.
  • Notion: query databases and write pages.
  • Xero: invoices, contacts, and organisation data for small-business bookkeeping.
  • GitHub: repos, issues, and pull requests alongside the local git tools.

Set up in minutes, governed by approvals

Each connector is one-click hosted OAuth from the desktop app: no developer console, no API key copy-paste. Read operations run freely; writes (posting messages, creating issues, sending invoices) go through the same approval gate as everything else the agent does, so you always see the action before it lands in a shared workspace.

A real example: invoice follow-up

Ask the agent to find overdue invoices in Xero, cross-check the client's last reply in your inbox, draft a polite follow-up in your voice, and log a reminder task. Each step uses a different connector; the agent carries the amounts, names, and dates between them, and asks before the email goes out.

Beyond the built-ins

Power users can attach any OpenAPI 3.x spec or MCP server and the agent registers those endpoints as tools too, so internal systems sit alongside Slack and Xero in the same loop.

Liminal vs Zapier or Make for small teams

Zapier and Make are great for fixed if-this-then-that automations. Liminal is for tasks that need judgment: read a thread, decide tone, pull the right invoice, draft a reply, and ask you before sending. You describe the outcome in plain English; the agent picks the tools.

Because Liminal runs locally with approval gates, you get flexible multi-step work without giving a cloud bot blanket write access to every connector.

Typical setup for a connected workspace

Download the Liminal desktop app, connect Gmail or Outlook and Slack in the Integrations hub, add Linear or Notion if you track work there, and connect Xero if you chase invoices. Paste an OpenRouter key or sign in for managed inference on Pro. Your first useful prompt is often inbox triage or a standup summary posted back to Slack.

FAQ

Common questions

Can the agent act in these tools without asking?

Reads are free; writes are approval-gated by default. You can loosen this in trusted environments, but out of the box the agent shows you every outbound action first.

What if my tool isn't on the list?

Attach an OpenAPI spec or an MCP server and its operations become agent tools. The built-in list also keeps growing: see the changelog.

Does Liminal replace Slack apps or Xero add-ons?

It complements them. You keep Slack and Xero as your system of record. Liminal is the agent layer that reads across both and drafts actions you approve.

How is this different from ChatGPT with plugins?

ChatGPT plugins run in OpenAI's environment with limited tool depth. Liminal runs on your computer with 500+ tools, local session logs, OAuth to your real accounts, and any model you choose.