LanternDOCS

Connectors

Connectors are integrations with external services that your agents can use as tools. When an agent has a connector attached, it can read from and write to that service -- searching emails, creating GitHub issues, posting Slack messages, and more.

In plain termsA connector is how you give an agent hands. On its own, an agent can only think and answer; connect Gmail and it can search your inbox, connect Slack and it can post to a channel, connect Stripe and it can look up a payment. You sign in to each service once (usually a normal OAuth "Allow" screen), and every agent you authorize can then use it — with per-tool rate limits from Budgets keeping usage in check.
Gmail
read · search · send
Google Calendar
events · availability
Slack
post · read channels
GitHub
issues · PRs · repos
Notion
pages · databases
Stripe
payments · billing
HubSpot
CRM · contacts · deals
Jira
issues · agile

Available connectors (17)

Communication

  • Slack (slack) -- read channels, post messages, manage threads; OAuth or bot token
  • Discord (discord) -- bot integration for servers and DMs
  • Telegram (telegram) -- bot messaging with inline buttons and media
  • Twilio (twilio) -- SMS, voice calls, and WhatsApp messaging; Account SID + Auth Token + phone number

Email & Calendar

  • Gmail (gmail) -- read, search, draft, and send emails; Google OAuth or app password
  • Google Calendar (google-calendar) -- read and create events, check availability

Docs & Storage

  • Google Drive (google-drive) -- access files and manage permissions
  • Google Sheets (google-sheets) -- read and write spreadsheet data
  • Notion (notion) -- access databases and workspace content; integration token

Dev Tools

  • GitHub (github) -- repositories, issues, pull requests; OAuth or personal access token
  • Linear (linear) -- issue tracking and project management; API key
  • Jira (jira) -- issue tracking and agile management; email + API token + domain
  • Sentry (sentry) -- error tracking and performance monitoring; auth token
  • Vercel (vercel) -- deployment management and project config; access token

CRM & Sales

  • HubSpot (hubspot) -- CRM contacts, deals, and marketing; API key
  • Salesforce (salesforce) -- CRM platform with full API access; username + password + security token

Commerce

  • Stripe (stripe) -- payments, subscriptions, and billing; secret key
Web search and web scrape are built-in agent tools, not connectors -- no installation required. They are always available and enabled per-session via the webSearch session flag.
Note: Custom connectors can be added by implementing the connector interface. See the SDK reference for details.

Setting up a connector

OAuth-based connectors

Most connectors (Gmail, Google Calendar, Slack, GitHub, Notion) use OAuth for authentication. The setup flow is:

  1. Navigate to Settings > Connectors in the dashboard
  2. Click the connector you want to enable
  3. Click Connect -- you will be redirected to the service's OAuth consent screen
  4. Authorize access and you will be redirected back to Lantern
  5. The connector is now available and can be attached to any agent
Tip: You can connect multiple accounts for the same service. For example, connect both your personal and work Gmail accounts, then assign different accounts to different agents.

API key-based connectors

Some connectors (Web Search, custom APIs) use API keys instead of OAuth. For these:

  1. Navigate to Settings > Connectors
  2. Click the connector and select Manual credentials
  3. Enter your API key or credentials
  4. Click Save -- credentials are encrypted at rest using your tenant's encryption key
Warning: API keys are stored encrypted and never appear in logs, traces, or run state. They are resolved at execution time inside the microVM.

Per-agent connector assignment

Connectors are enabled at the account level but assigned per agent. This means:

  • You connect your Gmail account once in Settings
  • For each agent, you choose which connectors it can access
  • An agent can only use connectors explicitly assigned to it

To assign connectors to an agent:

  1. Open the agent's detail page in the dashboard
  2. Go to the Configuration tab
  3. In the Connectors section, toggle the connectors this agent should have access to
  4. Click Save

How agents use connectors

When an agent runs, its assigned connectors are injected as tools that the LLM can call. For example, an agent with the Gmail connector can:

// The agent's LLM can call these tools automatically:
ctx.tools.gmail.search({ query: "from:boss@company.com subject:urgent" })
ctx.tools.gmail.draft({ to: "team@company.com", subject: "Summary", body: "..." })
ctx.tools.github.createIssue({ repo: "org/repo", title: "Bug: ...", body: "..." })

The LLM decides when to use each tool based on the agent's system prompt and the user's input. You do not need to write code to invoke connectors -- just assign them and the LLM handles the rest.

Connector permissions

Each connector requests the minimum set of permissions (OAuth scopes) needed for its functionality. You can review the exact permissions on the connector's detail page in Settings.

  • Gmail -- read and send email (not delete)
  • GitHub -- read repos, issues, PRs; create issues and comments
  • Slack -- read channels, post messages, manage threads
Tip: You can disconnect a connector at any time from Settings. Agents that depend on it will fail gracefully and report the missing connector in their run output.