Integrations

Lithora connects to the tools your engineering work already runs through. Most providers use OAuth; Cloudflare and Microsoft Teams connect by pasting a credential.

Integrations · syncing

0/3

Syncing connections…

Lithora sits at the center, keeping your repos, chat, and files in sync.

Connecting a tool

Open Dashboard → Integrations.
Find the provider's card and click Connect.
For OAuth providers, authorize Lithora on the provider's own site. You are returned to the integrations page when it completes.
For Cloudflare and Microsoft Teams, paste the credential in the dialog. Lithora verifies it before saving — Cloudflare tokens are checked against the API, and a confirmation card is posted to the Teams channel.

Plan gating is enforced on the server

GitHub and Discord connect on any plan. Every other provider requires Pro or Scale, and the check runs on the API, not just in the UI — calling the connect endpoint directly on a locked account returns a 403 asking you to upgrade.

Supported integrations

GitHub

OAuth

Every plan

The deepest integration: link repos, push tasks as issues, and drive automations from PRs and CI.

• Repos, issues, and two-way issue sync
• Create, comment on, label, and close issues
• Inbound webhooks for issues, PRs, and CI runs
• Automation triggers and actions, plus AI actions

GitLab

OAuth

Pro & Scale

Link GitLab projects and work with issues and merge requests. Self-managed GitLab is supported.

• Projects, issues, and merge requests
• Create, comment on, label, and close issues
• Create branches and merge requests
• Automation and AI actions

Bitbucket

OAuth

Pro & Scale

Link Bitbucket Cloud repositories and work with issues and pull requests.

• Repositories, issues, and pull requests
• Create issues, comments, and PRs
• Automation and AI actions

Jira

OAuth

Pro & Scale

Connect Jira Cloud and browse projects and issues with JQL.

• Projects and issue search via JQL
• Create, transition, assign, and comment on issues
• Automation and AI actions

Linear

OAuth

Pro & Scale

Two-way sync between Lithora tasks and Linear issues — for teams migrating from Linear or running alongside it.

• Create and link issues
• Inbound webhook sync
• Outbound (two-way) sync
• Backlog import via the import dialog

Slack

OAuth

Pro & Scale

Post updates to channels, DM people, and start work from a Slack message.

• Send channel messages and DM users
• Slash commands and interactivity
• Events feed back into Lithora
• Automation and AI actions

Discord

OAuth

Every plan

Link your Discord account to Lithora so the two identities are connected. The bot that would carry slash commands and DMs is not deployed yet.

• Link and unlink your Discord account
• Your linked teams, projects and members are readable by the integration

Microsoft Teams

Webhook URL

Pro & Scale

Post Lithora notifications into a Teams channel using an incoming webhook.

• Channel notifications
• Automation actions
• Connect by pasting the webhook URL — a confirmation card verifies it

Google (Drive & Calendar)

OAuth

Pro & Scale

Browse Drive files, read your calendar, and create calendar events from tasks.

• Drive files (read-only)
• Calendar read plus event creation
• Automation and AI actions

Notion

OAuth

Pro & Scale

• Notion SSO sign-in
• One-time page and database import

Figma

OAuth

Pro & Scale

Connect Figma and embed live files and frames next to the work that ships them.

• OAuth connect, refresh, and disconnect
• Embed Figma files and frames in workspaces and tasks

Vercel

OAuth

Pro & Scale

Surface Vercel projects and recent deployments, and act on them from Lithora.

• Projects and deployment status
• Redeploy and cancel deployments
• Team-scoped installs
• Automation and AI actions

Cloudflare

API token

Pro & Scale

Connect with a scoped API token to browse zones and Pages projects.

• Zones and Pages projects
• Purge cache, deploy, and roll back Pages
• Automation and AI actions

GitHub gets a page of its own because it does the most — GitHub PR & CI sync.

Connection health

Each provider card carries a live health state, the connected account, and a “last synced” timestamp. A connection can be in one of three states:

Connected: The stored token was verified against the provider.
Needs reconnect: The token expired or was revoked at the provider. Use Reconnect on the card — a banner also surfaces this per provider.
Disconnected: Nothing is connected for this provider yet.

GitHub and Linear also offer Sync now, which opens the backlog import dialog so you can pick what to bring in. Every other provider syncs through event webhooks automatically, so there is nothing to press.

Outbound webhooks

If you need to reach a tool Lithora does not integrate with, send it events directly from Settings → Webhook Center: outbound events signed with HMAC-SHA256, automatic retries, and a dead-letter queue for deliveries that never succeed.

Scale plan

The Webhook Center runs on the custom integrations entitlement, which is included with Scale and with custom Enterprise plans.

Not connectable yet

These are not connectable today. They are listed for transparency — do not build a process on them until they appear in Dashboard → Integrations. You can register interest from that page so you hear when one lands.

SentryPagerDutyGoogle Calendar sync (two-way)MCP server

Permissions and security

Integrations are authorized at two levels:

User level: Your own connection and personal notifications — for example Slack DMs.
Team level: Shared syncing and channel notifications. Managing these requires a team admin.

Token handling

Integration tokens are encrypted at rest and can be revoked at any time from the provider's card. Disconnecting removes Lithora's stored token; for providers with no revocation endpoint of their own, Lithora also points you at the provider's connected-apps page so you can complete the revocation there.