leera IntegrationsA little closer. All connected.

Keep your favorite tools.
Bring the work together.

Turn incoming requests into work with a home.
Bring your project closer to the tools your team already knows.

Get started with leera Explore the connections

An incoming email. A clear next step.

Give the request a project, then give the work an owner.

EMAIL / CUSTOMER REQUEST

Project inbox

A CUSTOMER REQUEST

A quick change to my order

Alex MorganTo: your project inbox

9:41

Hi team,

I placed an order this morning. Could you help me update the delivery address?

Thanks,
Alex

Project inbox

LEERA / CUSTOMER EXPERIENCE

Customer experience

SHOP-142

Update the delivery address on an order

I placed an order this morning. Could you help me update the delivery address?

Status: To do
Assignee: MMaya Chen
Project: Customer experience

Request received through the project inboxActivity stays with the issue

THE HANDOFF, IN FOCUS

Example workflow. Configure a project email address and choose who triages new requests.

YOUR TOOLS. A SHARED THREAD.

Email, website feedback, and GitHub today. Sentry, GitLab and expanded Slack workflows in Preview. Figma and FigJam add design links and private previews in Preview.

01 / Familiar tools. More context.

Less passing things around.
More moving them forward.

A request, a piece of feedback, a development update. Each connection should make the next step clearer—and keep the people doing the work in the loop.

Figma & FigJam

Preview

Keep the design with the decision.

Add Figma and FigJam links to a document as inline links, cards or click-to-load interactive embeds. Connect your own Figma account to request a private static file or frame preview that your account can access.

Preview requires the matching deployment and live verification. An instance administrator configures the Figma app; each member connects in Workspace Settings → Design integrations. Interactive embeds use your Figma browser session and source sharing rules.

PREVIEW DETAILS

Inline links, cards and click-to-load embeds
Private file and frame previews using your own account
Source permissions checked for each private preview

Email

Available

A place for every incoming request.

Create a project email address and bring incoming requests into the work. Keep the queue close to the team responsible for following through.

For self-hosted deployments, configure the mail provider and domain for your instance.

THE DETAILS

Project email addresses
Incoming and outgoing email logs
Instance email configuration

GitHub

Available

Keep the code close to the issue.

Connect a GitHub account and choose its repositories. Put the issue key in a branch name or pull request title, and the issue lists that branch or pull request with its current state.

A workspace admin connects GitHub. Self-hosted instances use their own GitHub App, including GitHub Enterprise Server, at an address GitHub can reach.

THE DETAILS

Pull requests and branches linked by issue key
Open, draft, merged, and closed states on the issue
Optional status changes for each project

Slack

Preview

Progress belongs in the conversation.

The expanded Slack preview connects issue requests, conversations, project updates and selected QA reports. Verify installation and behavior on your instance before rollout.

Personal notifications go to members whose Slack account is linked and follow their Slack notification preferences. Deployment and live verification remain required.Slack preview setup and support

PREVIEW DETAILS

Project activity notifications
Issue requests and linked conversations
Context around the update

New / Integration previews

Connect the next handoff.

Sentry Cloud and GitLab.com workflows are in Preview. Deploy the matching release, connect your own provider account and verify a live workflow. Credentials alone do not establish a working connection or public Marketplace publication.

Sentry Preview

Verified issue alerts create linked bugs with recurring-error deduplication and bounded source context.

GitLab Preview

GitLab.com merge requests link by issue key, with optional workflow status changes and delivery recovery.

Explore the developer guide

02 / A good handoff starts here

One useful connection.
A better everyday rhythm.

Start with a request source your team already uses. Give it a destination, make the behavior clear, and follow the first request all the way through.

A deliberate connection

Choose the connection. Keep its destination clear.

Configure project email or a website widget for the requests you want to receive, or connect GitHub so pull requests and branches find their issues by key. Choose the project, check a representative submission, and keep the queue close to the team following through. Expanded Slack workflows are in preview pending live verification.

01
Choose its home.
Pick the project that should receive the request. Decide who owns the incoming queue and what the next step should be.
02
Make the connection.
Set up a project email address or configure your website widget. Choose the details that make a submission useful to your team.
03
Follow the thread.
Send a representative request. Check its content and visibility, confirm the right team can find it, and build from there.

A useful connection has a clear destination. A useful queue has someone looking after it.

03 / Your workspace, in the conversation

Your tools connect.
Your AI can, too.

Bring compatible AI clients into the same project context through leera’s MCP server. Connect with scoped access and keep the workspace at the center of the work.

Explore the MCP server

For coding sessions in Conductor, Superset, Pane, or Nimbalyst, start with the setup guide.

Read the agent manager guide

ClaudeCursorChatGPT

One workspace. Shared context.leera MCP server

IssuesProjectsDocuments

Compatible clients · Scoped workspace access

Build your connection

REST API & Webhooks Preview

REST API (Preview)

Read and update supported Planner and QA resources with a scoped personal access key. Use the versioned contract published by your instance.

Read the API reference

Webhooks (Preview)

Receive signed change events, choose projects, rotate secrets, inspect attempts, and redeliver retained events. Verify and deduplicate every request.

Build a receiver

04 / The practical details

A few good questions.

Can I embed Figma and FigJam in a Leera document?+

The Figma and FigJam Preview supports inline links, cards and click-to-load interactive embeds in the web editor. Interactive embeds follow Figma’s sharing rules and the viewer’s Figma browser session; organization-only and password-protected files still require the appropriate access. Deploy the matching release and verify a live workflow before rollout.

How do private Figma previews work?+

An instance administrator configures the Figma OAuth app in Instance Settings → Integrations. Each member connects their own account in Workspace Settings → Design integrations, then requests a private image preview from a link. Leera checks that account’s source access for every request. An available file thumbnail or static frame image and its private title stay with that viewer; they are not saved into collaborative document content, public pages or exports. Connecting does not sign the viewer into an interactive iframe.

Which design integrations are supported?+

Figma and FigJam are the design integrations in this Preview. It links designs and shows previews; it does not import editable design layers, synchronize files or comments, or change source permissions. Other design providers are not included, and no availability date is promised.

What do the new integration previews include?+

Sentry Cloud alerts can create or link issues. GitLab.com merge requests link by issue key and can apply configured workflow status changes. Deploy the matching release, connect your own provider account and verify a representative live workflow before relying on either connection. These previews do not establish Marketplace publication or full two-way synchronization. The REST API and signed outbound webhooks have their own Preview contract and setup guides.

How do GitHub pull requests link to issues?+

Put the issue key, such as SHOP-128, in the branch name or the pull request title, for example feature/shop-128-saved-address. The pull request or branch then appears on that issue with its current state. Copy branch name on an issue gives a name that links. Pull request descriptions and commit messages are not scanned, and a member can remove a wrong link.

Does connecting GitHub automatically change every ticket?+

No. Only issues whose keys appear in a branch name or pull request title are linked, and status changes are off until a project chooses them. Each project can pick a status for a created branch, an opened or ready pull request, a merge, and a pull request closed without merging. Branch and opened pull request changes only move an issue forward, a merge waits until no other linked pull request is still open or in draft, and a pull request closed without merging leaves a done issue alone and does not apply while another linked pull request is open, in draft, or merged.

Does Leera sync GitHub issues or post to pull requests?+

No. The GitHub connection reads pull request and branch events only. It does not import or synchronize GitHub issues, comment on pull requests, or change anything in GitHub.

Can a self-hosted instance connect to GitHub?+

Yes. An instance administrator registers the instance’s own GitHub App, on github.com or GitHub Enterprise Server, and enters its credentials in Instance Settings. GitHub must be able to reach the instance’s webhook address; an instance on a private network that GitHub cannot reach receives no pull request events.

Can we build a custom integration?+

Use the REST API (Preview) for supported Planner and QA operations and signed Webhooks (Preview) for change notifications. Create a REST-bound personal access key in Personal settings → API and use its running reference. Workspace administrators manage webhook endpoints. Both follow access controls and can be disabled by an instance operator.

Should we enable every integration at once?+

Start with the connections that remove a specific handoff in your workflow. Give each incoming queue an owner and check that the integration creates useful context before adding more sources.

leera Integrations

Bring your everyday tools
a little closer.

Give the conversations and requests around your project a place to become progress.

Get started with leera Talk to our team

Keep your favorite tools.
Bring the work together.