laylight

Integrations

Integrations

Laylight reads the systems your organisation already works in. The core connectors below have their own page stating what they read and what they let you ask, and anything else with a documented API can be connected through Omni.

Core connectors

These are the systems most organisations keep their context in. Each page states exactly what the connector reads, what it adds to your context and how it works.

SlackWhat it reads and answersGitHubWhat it reads and answersGoogle DriveWhat it reads and answersNotionWhat it reads and answersLinearWhat it reads and answersConfluenceWhat it reads and answersOutlookWhat it reads and answersSupabaseWhat it reads and answersGoogle CalendarWhat it reads and answersOmniConnect anything with an API

Need a different one?

The system holding your context is always the one nobody supports. Rather than asking you to wait for a connector to be hand-built, Laylight includes Omni: point it at an OpenAPI description and it discovers the operations that system exposes, classifies which of them read data, and compiles a working connector against the same contract the built-in integrations use. Parsing is deterministic, so a generated connector cannot invent an endpoint that does not exist.

If X has a documented API, it can be connected. That includes the internal service that will never appear on anybody’s integrations page.

Connector catalogue

96 systems teams ask us about, grouped by what they are for. Systems in bold have a dedicated connector page. Everything else is reachable through Omni where it publishes an API, and the ones people ask for most are what we build by hand next.

Communication

Slack, Microsoft Teams, Discord, Telegram, Gmail, Outlook, Front, Twist, Zoom, Google Meet

Code and engineering

GitHub, GitLab, Bitbucket, Jenkins, CircleCI, Sentry, PagerDuty, Datadog, Grafana, Vercel

Documents and knowledge

Notion, Confluence, Google Drive, SharePoint, Dropbox, Box, Coda, Guru, Slab, Mintlify

Project management

Linear, Jira, Asana, Monday, ClickUp, Trello, Basecamp, Shortcut, Height, Productboard

CRM and sales

Salesforce, HubSpot, Pipedrive, Attio, Close, Gong, Outreach, Apollo, Clay, LinkedIn

Data and warehouses

Supabase, Postgres, Snowflake, BigQuery, Databricks, Redshift, MongoDB, ClickHouse, dbt, Airtable

Support

Zendesk, Intercom, Freshdesk, Help Scout, Crisp, Plain

People and finance

Workday, BambooHR, Rippling, Gusto, Greenhouse, Lever, Stripe, QuickBooks, Xero, Ramp, Brex

Product, design and marketing

Figma, Amplitude, Mixpanel, PostHog, Segment, Google Analytics, Webflow, Contentful, Sanity, Mailchimp

Calendar, storage and identity

Google Calendar, Outlook Calendar, Calendly, Okta, WorkOS, Auth0, Google Cloud Storage, Amazon S3, 1Password

Request a connector

If the system your context lives in is not listed, tell us which one at [email protected]. Connector priority is set by what people actually ask for, so this is the fastest way to move something up the list.

How connections work

Every connector is authorised through the provider’s own OAuth flow and scoped to the specific channels, folders, spaces, repositories, mailboxes, calendars or tables you choose. Access is read-only for retrieval, and revoking a connection stops further access immediately. See Security for how that data is handled, or Product for how the context is assembled once it arrives.