Skip to content

Integrations

What Vorkhurry connects to

Nine connections, listed with what each one actually does. If it is not on this page, it is not built.

Development

Connect the repository so the issue tracker knows what shipped.

GitHub

GitHub App, installed on the repositories you choose

Link branches, commits and pull requests to the issues they belong to, and let a merge move the issue.

  • Issue keys in branch names, commit messages and pull-request text are matched against your project keys
  • Each match is recorded as activity on that issue
  • A pull-request event can transition the issue — through the workflow's own guards, never around them
  • Webhook deliveries are signature-verified and recorded once, so a redelivery does not double-apply
  • Only the installation id is stored; tokens are minted per call and expire in an hour

Communication

Send the events your team cares about to the place they already are.

Slack

OAuth app — a bot token, stored encrypted

Post issue, comment and sprint events into the channels you route them to.

  • Choose which event types a workspace receives
  • Route per project to a specific channel, with a default channel for everything else
  • Messages are posted through chat.postMessage to a channel id or #name
  • Delivery runs on a background queue, so a Slack outage never slows down the app

Microsoft Teams

Incoming Webhook connector — a channel URL you paste in

The same events, delivered as message cards to a Teams channel.

  • Connect several channels by giving each URL a label
  • Route per project to a labelled channel
  • Events render as a Teams MessageCard with the status colour

Migration

Bring existing work in, row by row, with a preview before anything is written.

Jira

API credentials for your Jira site

Import issues from a Jira instance through its API.

  • Preview what will be imported before anything is created
  • Map Jira statuses onto your own workflow statuses
  • Per-row validation and conflict resolution — create, update or skip
  • Resumable: a re-run updates what it already imported rather than duplicating it

Linear

API credentials for your Linear workspace

Import issues from Linear through its API.

  • The same preview, mapping, validation and conflict steps as every other source
  • Per-row status, so a partial import reports exactly which records failed and why

CSV

File upload

Upload a file and map its columns — the path that works from anything.

  • Map arbitrary columns onto issue fields and workflow statuses
  • Validation runs before the import, not during it
  • The same resumable, row-level job as the API-based importers

AI providers

Your organization's own account, your own key, your own choice of models.

OpenAI

Your own API key, encrypted at rest and never returned

Use your organization's OpenAI account for AI assist.

  • Enable specific models and set a default
  • Per-feature model overrides
  • A monthly budget cap, and a per-call usage record

Anthropic

Your own API key, encrypted at rest and never returned

Use your organization's Anthropic account for AI assist.

  • Enable specific models and set a default
  • Per-feature model overrides
  • A monthly budget cap, and a per-call usage record

Google Gemini

Your own API key, encrypted at rest and never returned

Use your organization's Google AI account for AI assist.

  • Enable specific models and set a default
  • Per-feature model overrides
  • A monthly budget cap, and a per-call usage record

Signing in

A different thing from an integration: these authenticate a person. Which ones are offered depends on what your deployment has configured.

  • Email and passwordArgon2id hashing
  • Magic linkSingle-use, emailed
  • Two-factorTOTP with recovery codes
  • MicrosoftOAuth — enabled per deployment
  • GitHubOAuth — enabled per deployment

Building your own

Two things exist for connections Vorkhurry does not ship. Outbound webhooks subscribe an endpoint to domain events and deliver a signed payload, with a delivery log and a ping button to test it. Personal access tokens are scoped credentials for scripts and CI, issued and revoked from your own profile.

Start with your team, not with a sales call

Create a workspace, invite the people you work with, and bring your existing issues in from Jira, Linear or a CSV.