Integrations

Connect FeedbackFlow to the tools your team already uses. Turn feedback into tracked issues, route alerts to chat, and keep both sides in sync with signed webhooks.

Manage all four from Integrations in the dashboard. Each shows a connection toggle and a “connected” badge, and requires the integrations.manage permission to change.

GitHub

Create and link GitHub issues from feedback items. Enable the GitHub tab and provide:

  • A personal access token with repo scope (stored encrypted).
  • The owner and repository to file issues against.
  • A webhook secret so inbound updates can be verified.

Add a repository webhook pointing at your instance so a closed issue can move the linked feedback along:

# GitHub → Settings → Webhooks → Add webhook
Payload URL:  https://app.feedbackflow.app/api/integrations/github/webhook
Content type: application/json
Secret:       <your webhook secret>

Jira

Push feedback into a Jira project as tickets. Enable the Jira tab and provide your domain, account email, an API token, and the target project key (uppercased). Add a webhook secret to receive status updates back.

Slack

Post messages to a channel on feedback events. Enable the Slack tab and provide a bot user OAuth token, the target channel ID, and a signing secret. Then choose which events to send:

  • New feedback — every new submission, or only high/critical.
  • Status changes — when an item moves between states.

Microsoft Teams

Drive the same notifications into a Teams channel. Enable the Teams tab, paste an incoming webhook URL, name the channel, and pick your notification events.

Linking issues to feedback

Once a connector is enabled, open any feedback item and use Create issue to file a new GitHub issue or Jira ticket, or link an existing one. The external reference and its last-synced time appear in the item's Linked issues panel.

The number of active integrations is plan-limited: 1 on Free, 4 on Pro, unlimited on Enterprise.

Webhook verification

Inbound webhooks are verified against the per-provider secret you configured, so only legitimate events from your connected tools are accepted. Keep these secrets private; rotate them from each integration's tab if one is exposed.