Skip to content
Quillboard
Integrations

Connect your feedback to the tools you already use

Quillboard pushes status changes on your suggestions out to Slack, a Discord channel, GitHub Issues, Linear, or Jira — configured per community under Settings → Integrations.

Integrations are a Pro+ feature. Stored credentials are AES-256-GCM encrypted at rest, delivery rides a retrying outbox (a transient provider outage won’t drop events), and you can Test any integration before saving. See pricing.

Which events fire

An integration delivers when a suggestion transitions to any status you select: under_review · planned · in_progress · completed · rejected. GitHub / Linear / Jira also open a tracking issue and, where supported, sync the status back.

Slack

Delivers a message to a Slack channel via an Incoming Webhook.

  1. 1In Slack, go to api.slack.com/apps → Create New App → From scratch (or reuse an app).
  2. 2Enable Incoming Webhooks, click Add New Webhook to Workspace, and pick the target channel.
  3. 3Copy the webhook URL (https://hooks.slack.com/services/…) and paste it into the Slack integration.

Discord channel

Posts to a Discord channel via a channel webhook — this is separate from the Quillboard bot.

  1. 1In Discord: Server Settings → Integrations → Webhooks → New Webhook.
  2. 2Choose the channel, then Copy Webhook URL (https://discord.com/api/webhooks/…) and paste it in.

GitHub Issues

Opens and updates a GitHub Issue for tracked suggestions.

Repositoryowner/repo
Access tokenA fine-grained PAT scoped to the repo with Issues: Read and write (or a classic token with the repo scope) — stored encrypted.

Linear

Creates Linear issues in a team.

API keylin_api_… (Settings → API → Personal API keys)
Team IDyour team key, e.g. ENG

Jira

Creates Jira issues in a project.

Hosthttps://you.atlassian.net
Emailthe Atlassian account that owns the token
API tokenfrom id.atlassian.com → Security → API tokens — stored encrypted
Project keye.g. FEED

Notes

To rotate a credential, delete the integration and re-add it with the new token (tokens are write-only once saved — never shown back). Prefer to pull instead of push? A scoped API key plus the read-only API lets you fetch the same data into your own tooling — see the docs overview.

Integrations · Quillboard