Liddr Docs

Appearance

Available connectors ​

These connectors bring org-shared structure, work artifacts, and authored knowledge into your shared knowledge graph. Once connected, each one keeps your graph current and tags everything with its source, so Know, Signal, and Forge can reason across every source at once.

Only org-shared, non-sensitive systems belong here. Personal, record-level, or sensitive data is reached per user through personal connectors instead — see the access principle for why.

To connect any of these, see Connecting sources.

What you'll provide

Most connectors need an access token or API key, plus optional scoping such as a workspace, organization, or base URL. A few need extra required details to work at all — those are called out below.

Per-connector setup guides

For the exact credentials and minimum scopes a connector needs — for both ingest (read) and reverse sync (write) — see the Connector setup guides in the sidebar. Guides exist for GitHub, GitLab, Bitbucket, Jira, Confluence, Figma, New Relic, and AWS.

Core connectors ​

These are always available in Connections, ready to connect:

  • Jira — projects, issues, and workflow structure. You'll provide an Atlassian account email and an access token, plus your site URL and a project.
  • Confluence — pages and spaces. Uses the same Atlassian credentials; you'll provide a space.
  • GitHub — repositories, issues, and pull requests. You'll provide an access token and the organization and repository to pull.
  • Figma — design files and frames. You'll provide a Figma access token; the file is chosen when you sync.
  • New Relic — observability data. You'll provide an API key, plus region and account.
  • Salesforce — structure and metadata (record-level data stays in personal connectors).
  • ServiceNow — instance structure and records configured for org-shared use.

Dev & code ​

  • GitLab 🦊 — projects, issues, and merge requests from GitLab SaaS or self-managed. You'll provide an access token; optionally a group scope and base URL.
  • Bitbucket 🪣 — repositories and pull requests from a Bitbucket Cloud workspace. You'll provide an app password, workspace, and username.
  • Azure DevOps 🔷 — projects and work items from Azure DevOps Services. You'll provide a personal access token and organization.

Project management ​

  • Linear 📐 — issues and projects. You'll provide an API key.
  • Asana 🅰️ — projects and tasks from an Asana workspace. You'll provide a personal access token; optionally a workspace scope.
  • ClickUp ✔️ — tasks and teams. You'll provide an API token.
  • Monday 🟪 — boards and items from Monday.com. You'll provide an API token.
  • Trello 📋 — boards and cards. You'll provide an API key and token.
  • Shortcut ⚡ — stories and epics from your Shortcut workspace. You'll provide an API token.
  • Height 📐 — tasks and lists from your Height workspace. You'll provide an API key.

Product ​

  • Productboard 📦 — features and customer feedback notes. You'll provide an access token.
  • Aha! 💡 — features and ideas from Aha! product management. You'll provide an API token and your subdomain.

Incident & ops ​

  • PagerDuty 🚨 — incidents and services. You'll provide an API token.
  • Opsgenie 🔔 — alerts and services (SaaS or EU region). You'll provide an API key; the base URL is editable for region.
  • Sentry 🛡️ — projects and unresolved issues (SaaS or self-hosted). You'll provide an auth token; optionally an organization and base URL.

Data & docs ​

  • Notion 📓 — pages and databases from a Notion workspace. You'll provide an integration token.
  • Confluence — see Core connectors.
  • GitBook 📘 — spaces from your GitBook documentation. You'll provide an API token; optionally an organization scope.
  • Guru 🧠 — cards from your Guru knowledge base. You'll provide an API token and user.
  • Stack Overflow 📚 — questions and articles from Stack Overflow for Teams. You'll provide an access token and team.
  • Coda 🔵 — docs and tables from a Coda workspace. You'll provide an API token.
  • Contentful 📝 — published entries from a Contentful space. You'll provide a Content Delivery API token and space; optionally an environment.
  • WordPress 📰 — posts and pages from a site. You'll provide the site URL; optionally an application password and user (leave blank for public sites).
  • Miro 🟨 — boards from a Miro workspace. You'll provide an access token.
  • Databricks 🧱 — jobs and SQL warehouse definitions (structure only, not row data). You'll provide an access token and host.

Liddr — grounded in your reality, linked to the evidence.

© Liddr