Lovelace Developer Portal
Overview
Auth Hub
Studio
Agents Cloud
Skills
Memory Platform
Lattice Cloud
Hosting
Ada CLI
MCP Gateway
Ada
Periscope
Editor Extensions
Skip to main content

Connected Apps

Lovelace works best when it can meet your team where work already happens. Use this page to find the right guide for connecting an outside app or service.

Choose What You Want To Connect

Start with the Lovelace product you are using, then open the guide for the app or service you want to connect.

Lovelace productGuides
AdaConnect Ada to apps, Slack, Linear, GitHub, Discord, Email
Ada CLIConnect editors, Use Ada CLI in CI/CD
Lattice CloudUse OpenAI-compatible clients, Use your own computer
MCPConnect clients, Use tools, Use resources
Editor ExtensionsUse Neovim

If a supported connection is missing from this table, the portal docs need a user-facing setup guide for it.

What A Good Setup Guide Should Do

A setup guide should help you finish a real task, not explain Lovelace internals.

It should tell you:

  • whether the guide is for you
  • what access you need before you start
  • what the outside app will ask you to approve
  • what changes after you approve it
  • what to do immediately after setup
  • where to review or turn off the connection later
  • what happens to your Lovelace history if you turn it off
  • how to fix the most common problems

You should not need source code, internal runbooks, or architecture docs to get a supported connection working.

What To Check Before You Approve

Before approving any outside app connection:

  1. Confirm the Lovelace workspace is the one your team uses.
  2. Confirm the outside workspace, team, repository, or account is the right one.
  3. Read what the outside app says Lovelace will be allowed to do.
  4. Stop if the approval screen asks for something that does not match the guide.

For Ada pages, the guide should explain approval screens in everyday language. You should not need to understand technical terms to decide whether to continue.

After Setup

A guide should give you one visible first check. Examples:

  • Ada appears in Slack and answers a direct message.
  • A command works from the CLI.
  • A client can send a request to Lattice Cloud.
  • An editor extension can sign in and show account state.

If the guide does not tell you what success looks like, the guide needs more detail.

Turning A Connection Off

Turning a connection off usually stops Lovelace from using that outside app. It does not always delete work that already belongs to your Lovelace account.

Use the guide for the app you connected. It should say:

  • where the off switch is
  • who can use it
  • what stops immediately
  • what stays available in Lovelace
  • how to connect the app again later

Related

  • Ada
  • Connect Ada to apps
  • Use Ada in Slack
  • Use Ada in Linear
  • Use Ada in GitHub
  • Authentication
  • MCP

Build and deploy AI agents with ease.

Quick Start

  • Getting Started
  • Build Your First Agent
  • Platform Concepts
  • Examples & Tutorials

Develop

  • Create an Agent
  • Connect an MCP Server
  • API Reference
  • CLI Tools

Platform

  • Agents Cloud
  • Roadmap
  • Platform Changelog
  • Status

Resources

  • Discord
  • GitHub
  • Support
  • Developer Blog
Lovelace logo
Lovelace
Made with ❤️ by Reasonable Tech CompanySupport
TermsPrivacy
All systems operational

Home

Getting Started

Agents

Memory & Context

Workflows

Sessions

Workspaces

Tools

Resources

Authentication

Integrations

Deployment

Platform Architecture