Ticket Providers

Jira

Creates issues in your Jira Cloud instance. Uses the Jira REST API v3 with email + API token authentication.

Getting an API token:

1. Go to Atlassian API Tokens
2. Click "Create API token" and give it a descriptive label
3. Copy the token and use it as the apiToken value
4. Use the email address of your Atlassian account as the email value

{
  "provider": "jira",
  "baseUrl": "https://yourorg.atlassian.net",
  "projectKey": "SUP",
  "apiToken": "your-api-token",
  "email": "you@example.com",
  "issueType": "Task"
}

GitHub Issues

Creates issues in a GitHub repository. Uses the GitHub REST API with a personal access token. You can auto-apply labels to organize tickets.

Creating a personal access token:

1. Go to GitHub Fine-grained tokens
2. Click "Generate new token"
3. Select the target repository and grant Issues: Read and write permission
4. Copy the token and use it as the token value

{
  "provider": "github",
  "owner": "your-org",
  "repo": "support",
  "token": "ghp_xxxxxxxxxxxx",
  "labels": ["kody-ticket", "bug"]
}

Linear

Creates issues in a Linear team using the Linear GraphQL API. Issues are assigned to the specified team and can have labels applied automatically.

Getting an API key:

1. Go to Linear Settings → API
2. Create a new personal API key
3. Copy the key and use it as the apiKey value

{
  "provider": "linear",
  "apiKey": "lin_api_xxxxxxxxxxxx",
  "teamId": "TEAM-ID",
  "labelIds": ["label-id-1"]
}

Email

Sends ticket notifications via email using SMTP. The recipient address is required; all SMTP fields are optional to support future hosted email relay.

{
  "provider": "email",
  "to": "support@example.com",
  "from": "noreply@example.com",
  "smtpHost": "smtp.example.com",
  "smtpPort": 587,
  "smtpUser": "smtp-user",
  "smtpPass": "smtp-password"
}

Webhook

Sends ticket data to any HTTP endpoint. This is the most flexible option — use it to integrate with Slack, Discord, Notion, your own API, or any service that accepts webhooks.

Signature Verification

When a secret is configured, Kody includes an X-Kody-Signature header containing an HMAC-SHA256 hex digest of the request body. Verify this on your server to ensure requests are authentic and have not been tampered with.

{
  "provider": "webhook",
  "url": "https://example.com/api/tickets",
  "method": "POST",
  "headers": {
    "Authorization": "Bearer your-token"
  },
  "secret": "your-hmac-secret"
}

import crypto from "node:crypto";

function verify(body: string, signature: string, secret: string) {
  const expected = crypto
    .createHmac("sha256", secret)
    .update(body)
    .digest("hex");
  return crypto.timingSafeEqual(
    Buffer.from(signature),
    Buffer.from(expected),
  );
}