Connections catalogue

This is the full list of systems kanman connects to. To connect one, open Workspace settings > Connections and search for it, or for what you need (“tickets”, “alerts”, “wiki”). How connecting works, the safe defaults and who connects what are explained in How connections work.

Guides for the most used systems

All systems

Each of these systems has its own entry in the list. Reading is on once connected; anything that reaches people or customers stays Off until a team turns it on.

• Asana: reads tasks, comments and milestones; can comment on tasks or create them.
• monday.com: reads items, their updates and boards; can post updates or create items.
• ClickUp: follows tasks and comments, reads Docs and answers when someone mentions @kanman.
• Airtable: reads bases and tables; can add rows, for example to keep a log up to date.
• Figma: reads frames and comments and notices when a design changes.
• Zapier: receives events from your Zaps and can start a Zap, which reaches thousands of other apps.
• Zendesk and Freshdesk: read tickets to see which customers a problem affects; internal notes that customers never see.
• Intercom: reads conversations, adds internal notes and answers when a teammate mentions @kanman. Replies to customers stay off until a team allows them.
• HubSpot: looks up companies and tickets to see which customers a problem affects; notes on tickets.
• Stripe: payment health, revenue and new disputes. Read only: kanman never moves money.
• Okta, Microsoft Entra ID and Google Workspace Directory: who works where, in which groups and who reports to whom; Entra ID also shows who is away.
• Google Calendar: availability, change windows and public holidays before kanman plans deploys or asks people.
• Gmail: sends notifications and reports from a mailbox of your Google Workspace. kanman never reads mail.
• Google Drive & Docs: searches and reads your Docs and Sheets for context.
• Bitbucket (Cloud and Data Center): repositories, pull requests, comments and pipelines; reacts to reviews and failed builds. Sign in with Bitbucket Cloud, or use an API or access token.
• Jenkins: builds and deploy jobs, failed console output and test reports; can rebuild a flaky job.
• Snyk: issues and vulnerable dependencies of your projects, and new findings.
• LaunchDarkly and PostHog: feature flags and their targeting; PostHog also events, funnels and exceptions. Turning a flag off to stop an incident stays off until a team allows it.
• Dynatrace: reacts to problems and reads logs, services and deployments.
• AWS, Google Cloud and Microsoft Azure: services, deployments, costs, logs and the names of secrets, never their values. Read only.
• Cloudflare: Pages deployments and previews, zones and Workers.
• Kubernetes: the health of your workloads, rollouts and pod logs; can restart a deployment when a team allows it.
• Mattermost: reads channel threads and answers when someone mentions kanman; also on your own server through your runner.
• Miro: reads boards and their items for design context.
• Salesforce: looks up accounts and cases to see which customers a problem affects.
• Trello and YouTrack: read cards and issues; YouTrack also sprints, comments and articles, in the cloud or on your own server.
• Zoom: reads meetings and their transcripts.
• Argo CD, Octopus Deploy and Red Hat OpenShift: deployments, sync and rollout state, health.
• CircleCI, TeamCity and Harness: pipelines and builds, failed logs and test results; Harness also feature flags.
• Netlify: deploys and preview addresses.
• HCP Terraform / Terraform Enterprise: runs and their plans, and notices finished runs.
• Docker Hub, Harbor, JFrog Artifactory and Sonatype Nexus Repository: images and packages, and their scan findings where the registry has them.
• Better Stack, Honeycomb, Splunk, Icinga and Zabbix: alerts and checks, logs and queries for investigations.
• ilert and incident.io: incidents and who is on call; paging people stays off until a team allows it.
• Firebase Crashlytics: crash groups from your BigQuery export.
• Aikido Security, Aqua Trivy and Checkmarx One: security findings and vulnerable dependencies.
• Azure Key Vault: names of secrets and certificates and when they expire, never their values.
• Microsoft SQL Server, MySQL / MariaDB, other SQL databases, MongoDB and Redis: read-only queries on a replica, schema and migration state through your runner; Redis shows health and slow commands, never values.
• Snowflake, Google BigQuery, Databricks and Microsoft Fabric: read-only queries with time and cost limits; Databricks and Fabric also job and pipeline runs.
• dbt Cloud and Apache Airflow / Astronomer: runs, failed models, tasks and their logs; notices failed dbt Cloud runs.
• HashiCorp Vault: names, versions and dates of secrets, never their values.
• Mend, OWASP Dependency-Track, Semgrep and OSV.dev: vulnerable dependencies and security findings.
• npm Registry: package versions, deprecations and downloads.
• BMC Helix ITSM, TOPdesk and Zammad: incidents, changes and tickets; internal notes ask first, replies to customers stay off until a team allows them.
• Jira Service Management: requests with their comments, open incidents, problems and changes, in the cloud or on your Data Center through your runner; internal comments ask first, comments for the customer stay off until a team allows them.
• OpenProject and Redmine: work packages and issues, versions and comments, in the cloud or on your own server.
• Nextcloud: finds and reads files.
• Typeform: forms and their responses, as they come in.
• Metabase, Power BI, Tableau, Amplitude and Google Analytics 4: dashboards, reports and product numbers.
• App Store Connect: builds, TestFlight and reviews; replying to a review stays off until a team allows it.
• BrowserStack (with Percy): test sessions and visual review builds.
• Active Directory / LDAP and Keycloak: people and groups from your directory; LDAP is read through your runner.
• Email (IMAP): reads recent messages of a mailbox through your runner, without marking them read.
• Personio: who is absent and when, so kanman plans around it.
• Microsoft Dynamics 365 and Pipedrive: accounts, cases and deals, to see which customers a problem affects.
• SendGrid: bounces, blocks and delivery numbers; notices spikes of failed deliveries.
• Twilio, Discord and Google Chat: messages and calls; sending to people stays off until a team allows it.
• Google Play Console: releases, tracks and reviews; replying to a review stays off until a team allows it.
• Matomo, Mixpanel and Langfuse: product numbers and traces of your AI features.
• Phrase: translation progress and missing keys.
• Postman: collections, APIs and monitor results.
• TestRail and Xray: test runs and their results.
• Unleash: feature flags and their state per environment; switching a flag stays off until a team allows it.
• DigitalOcean, Hetzner Cloud and Port: servers, apps, deployments, costs and your service catalog.
• Red Hat Ansible Automation Platform / AWX: jobs and job templates; launching one stays off until a team allows it.
• Make, n8n and Microsoft Power Automate: scenarios, workflows and flows that call kanman or that kanman can start.
• Box and Dropbox: find and read files.
• Shortcut and Smartsheet: stories, epics, iterations and sheets.
• Bamboo, Buildkite and Spinnaker: builds, pipelines and their logs; Buildkite can rebuild a failed job when a team allows it.
• Flux CD, Heroku, Railway and Render: deployments and releases, their state and logs; rollbacks and deploys stay off until a team allows them.
• Pulumi Cloud and Spacelift: stacks, updates and runs of your infrastructure code.
• Axiom, Coralogix, Logz.io, OpenSearch, IBM Instana, Cisco AppDynamics and Jaeger: logs, traces, metrics and alerts for investigations.
• FireHydrant, Rootly and Grafana OnCall / IRM: incidents and who is on call; notes and acknowledgements ask first.
• Bugsnag / SmartBear Insight Hub: errors and releases; notices errors that come back.
• AWS now also reads CodePipeline and CodeBuild, Azure its Container Registry, and Google Cloud Cloud Monitoring alerts.
• Checkly, Pingdom, StatusCake, UptimeRobot, Uptime Kuma, Nagios, Netdata, VictoriaMetrics and SigNoz: checks, uptime and alerts; alerts open kanman’s incidents.
• Cachet: your status page’s components and incidents; posting an update stays off until a team allows it.
• Graylog and Sematext: log searches and alerts for investigations.
• Honeybadger, Raygun, Rollbar and LogRocket: errors, their occurrences and deploys; resolving an error asks first.
• Microsoft Clarity: how people use your pages, a few times a day.
• Maven Central: versions of Java packages.
• 1Password, CyberArk Conjur and Infisical: names of vaults, items and secrets, never their values.
• GitGuardian: leaked secrets found in your code, without the secret itself; resolving asks first.
• Black Duck Polaris, Codacy, Codecov, DeepSource, JetBrains Qodana and OWASP ZAP: code quality, coverage and security findings; a ZAP scan stays off until a team allows it.
• OpenText Fortify, Veracode, Wiz and Socket: security findings and risky packages; PyPI: versions of Python packages.
• Freshservice, HaloITSM, Ivanti Neurons for ITSM, ManageEngine ServiceDesk Plus and Matrix42: tickets, changes and problems; internal notes ask first, replies to requesters stay off until a team allows them.
• OTRS / Znuny, SysAid, Zoho Desk, Crisp, Plain and Pylon: support tickets and conversations; internal notes ask first, replies to customers stay off until a team allows them.
• IBM DOORS Next, PTC Codebeamer and Siemens Polarion: requirements, work items and test runs, also on your own servers.
• Jira Align, Jira Product Discovery and Productboard: epics, features, ideas and objectives.
• Plane, Taiga, Targetprocess, Teamwork.com, Wrike and Zoho Projects: work items, sprints and milestones; comments ask first.
• BookStack: books and pages for context.
• Canva: designs and folders, after you sign in with Canva.
• Oracle Database, CockroachDB, Neon and ClickHouse: read-only queries with limits; Oracle and CockroachDB through your runner.
• Airbyte, Dagster and Prefect: syncs, pipeline runs and their failures; starting one asks first.
• Looker, Apache Superset, Redash and Qlik Sense: dashboards, charts and saved queries.
• Coda, GitBook, MediaWiki, Nuclino, Outline, Slite, Stack Overflow for Teams, Wiki.js and XWiki: search and read your team’s knowledge; Outline drafts ask first.
• Google Forms, Microsoft Forms and Tally: form responses as they come in.
• Penpot: design files and their comments.
• Firebase: Hosting releases, App Distribution builds and Firestore documents.
• Chromatic, Bitrise and Bump.sh: visual review builds, mobile builds and API changes.
• Azure API Management: your APIs, products and subscriptions, never their keys.
• ConfigCat, Flagsmith, Flipt, GrowthBook and Statsig: feature flags, experiments and their state; switching a flag stays off until a team allows it.
• Crowdin, Lokalise, Tolgee and Weblate: translation progress and new keys.
• Plausible, FullStory and Pendo: visits, sessions and feature usage.
• Google Apigee and Kong Konnect: your APIs, proxies, services and routes.
• Tricentis qTest: test runs and their results.
• CalDAV and Exchange Server: calendars, so kanman knows when people are busy; Exchange reads message headers only, through your runner.
• Element / Matrix and Rocket.Chat: rooms and messages; posting stays off until a team allows it.
• tl;dv: meetings, transcripts and notes.
• Gerrit, Apache Subversion and Perforce Helix Core (through Helix Swarm): changes, reviews and code history.
• Proxmox VE, Rancher and VMware vSphere: virtual machines, clusters and workloads, through your runner where they live in your network.
• SAP Cloud ALM: projects, tasks, features and requirements.

Gmail, Google Calendar, Google Drive & Docs, the Google Workspace Directory and Microsoft Entra ID offer Sign in with your Google or Microsoft account; a service account key or an app registration works as well.

Logos

Some systems are shown with their vendor’s logo where the vendor allows it; all others show a neutral icon. Product names and logos only identify the systems kanman connects to, as the note at the bottom of these pages says. kanman is not affiliated with or endorsed by these companies.

Related pages

• How connections work
• Connections