Layercue
Integrations

Plug into the tools your team lives in.

14 integrations across design, engineering, communication, and identity. 9 live today, the rest landing this quarter.

The five most-used integrations

Figma
Slack
Linear
GitHub
Notion
In their tools

Layercue meets reviewers where they already work.

Same decision, three surfaces. Notifications go where each role lives — and Layercue stays the source of truth.

Slack

Reviewers reply where they already are

Layercue posts threaded notifications scoped to each project. Reviewers respond inline; the structured record stays in Layercue.

Setup guide
Northwind# design-review
L
LayercueAPP11:24 AM

Maya Okonkwo opened a review on Checkout / Payment step v4.

The CVV field needs more breathing room

At 320px the CVV is flush with the card-number field. Suggest 56px width with 12px gutter.

Pin · Payment step·2 replies·1h ago
👀 4  ✅ 2  🔥 1

Linear

Decisions become tickets, not meetings

When a decision is made, Layercue auto-creates a Linear issue with the rationale, dissent, and a back-link to the surface.

Setup guide
LinearNW · Eng
NW-2419 In progressAuto-created from Layercue
Checkout · CVV field width regression at 320px

From Layercue decision #cvv-field-width: cap CVV input at 56px with 12px gutter. Verified pattern with checkout team. Affects v4 payment step.

Assignee
DRDevon Reyes
Project
Checkout v4
Priority
● High
Cycle
Cycle 41 · ends Fri
Layercue threadlayercue.com/d/cvv-field-width →

GitHub

PRs carry the design rationale

Open a PR that references a Layercue decision and Layercue posts the summary inline — reviewers see the why without leaving the PR.

Setup guide
northwind/checkout-webPR #4188 · Open
Layercue · Decision shippedjust now
Cap CVV field width to 56px with 12px gutter at ≤320px

Implements Layercue decision #cvv-field-width from the Checkout v4 payment step review. Closes NW-2419.

Decision rationale: 320px viewport caused CVV to flush against card-number field. Verified pattern with checkout team. Maya O., Devon R., Priya S. approved.
+14 −6·2 files changedView in Layercue →

Design tools

4 integrations · 1 live
Figma
● Live

Two-way sync with Figma comments. Pin from inside the file, decisions flow back as resolved threads.

Setup guide
Sketch
● Beta

Mirror reviews from Sketch files. Same pinning model, same decision log.

Setup guide
Framer
● Beta

Review live Framer prototypes with state-aware pins.

Setup guide
Webflow
● Beta

Review marketing pages on Webflow staging. Pin to a breakpoint, scope to a CMS item.

Setup guide

Engineering

3 integrations · 3 live
Linear
● Live

Decisions auto-create Linear issues with the rationale, dissent, and surface link attached.

Setup guide
GitHub
● Live

PR-bound reviews. Layercue posts a decision summary to the PR when the surface ships.

Setup guide
Jira
● Live

Decisions sync to Jira tickets with field mapping. Supports custom workflows and transitions.

Setup guide

Communication

3 integrations · 2 live
Slack
● Live

Notification routing per project. /layercue slash command opens a review without leaving Slack.

Setup guide
Loom
● Live

Attach Loom recordings to a pin. Async crit gets a face without scheduling a call.

Setup guide
T
Microsoft Teams
● Soon

Channel notifications, threaded reviews inside Teams.

Setup guide

Project management

2 integrations · 1 live
Notion
● Live

Embed decisions and changelogs in Notion docs. Live updates, no copy-paste.

Setup guide
Asana
● Soon

Sync decisions to Asana tasks with project-level mapping.

Setup guide

Identity & access

2 integrations · 2 live
Okta
● Live

SAML SSO and SCIM provisioning for the Team plan.

Setup guide
Google Workspace
● Live

Sign in with Google, sync directory, scoped to your domain.

Setup guide
For builders

The API our integrations are built on.

Read pins, write decisions, subscribe to changelog events. We don’t hide anything our own team uses.

~/projects/layercue-bot · sync.ts
import { Layercue } from "@layercue/sdk";

const lc = new Layercue({ token: process.env.LAYERCUE_TOKEN });

// Subscribe to decisions on a project surface
const stream = await lc.surface("checkout-redesign").decisions.subscribe();

for await (const decision of stream) {
  await linear.issues.create({
    title: decision.title,
    description: decision.rationale,
    labels: ["design-decision"],
    projectId: PROJECT_MAP[decision.surface.id],
  });
}
Don't see your tool?

Build on the open API.

Webhooks, OAuth apps, and a TypeScript SDK. Build the integration your team needs in an afternoon.

14-day Pro trial · SOC 2 Type II · 99.95% uptime SLA on Team