Integrations
Feedback is only useful once it reaches the place your team already plans work. FeedbackKit turns a feature request into a ticket in your tracker, and keeps the two in step as the status changes.
Issue trackers
Nine providers can create a ticket from a piece of feedback, individually or in bulk, and keep a link back to the original request.
| Provider | Create | Status sync | Comment sync | Vote count |
|---|---|---|---|---|
| GitHub | Yes | Yes | No | No |
| Linear | Yes | Yes | Yes | No |
| Notion | Yes | Yes | Yes | Yes |
| ClickUp | Yes | Yes | Yes | Yes |
| Monday.com | Yes | Yes | Yes | Yes |
| Airtable | Yes | Yes | Yes | Yes |
| Asana | Yes | Yes | Yes | Yes |
| Trello | Yes | Per-status list | Yes | No |
| Basecamp | Yes | Yes | Yes | No |
The table is deliberately specific rather than a row of ticks. Capabilities are not uniform: GitHub creates and closes issues but does not mirror comments, and vote-count sync needs a numeric field the provider can hold. Trello moves a card only where you have mapped a target list for that status.
Notifications and CRM
Four more providers do something other than create tickets.
Slack
Posts notifications to a channel through a webhook. There is no ticket to create.
HubSpot
Contact sync, so the people leaving feedback line up with your CRM records.
Salesforce
Contact sync into Salesforce.
Email Campaign
Contact and campaign sync for product announcements.
Getting set up
Integrations are configured per project in the admin, and are available on the Pro and Team plans. See pricing for the plan limits, or the documentation to connect an SDK first.