Integrations
See every integration Quackback offers, how events and event mappings work, how to pause or reconnect an integration, and what happens to linked issues when you delete a post.
Connect Quackback to the tools your team already uses. Send feedback and support events to chat tools, turn feedback into issues in your tracker, enrich users with CRM data, and automate the rest with no-code platforms.
Note: On Quackback Cloud, integrations are available on the Business and Enterprise plans. Self-hosted installs include every integration.
All integrations live in Admin > Settings > Integrations.
Available integrations
Notifications
- Slack: notifications, the "Send to Quackback" shortcut, and channel monitoring
- Discord: notifications in your Discord server
- Microsoft Teams: Adaptive Card notifications in Teams channels
- ntfy: push notifications to any device
Issue tracking
GitHub, Jira, Linear, and Azure DevOps also work with support tickets: create an issue from a ticket, and sync the ticket's status when the issue changes.
Support & CRM
Automation
Developer tools
- Webhooks: send events to any HTTP endpoint
- API overview: the REST API, with the full reference at /api/v1/docs on your workspace
- MCP server: connect AI tools and agents to your workspace
How integrations work
Quackback uses an event-driven integration system:
- Something happens in Quackback (for example, a post is created).
- Quackback dispatches the event.
- Each integration mapped to that event runs.
- The integration sends its notification or creates its issue.
Events
Integrations can respond to these events:
Event | Description |
|---|---|
| New feedback post submitted |
| Post status updated (for example, Planned to Shipped) |
| Post title or content edited |
| Post soft-deleted |
| Deleted post restored |
| Post merged into another post |
| New comment on a post |
| Comment edited |
| Comment deleted |
Event mappings
Configure which events trigger which integrations:
- Go to Admin > Settings > Integrations
- Select an integration
- Configure Event Mappings
- Choose which events to send
For example, only send to Slack when a post becomes "Planned".
Set up an integration
- Go to Admin > Settings > Integrations
- Click the integration you want to set up
- Follow the connection flow (usually OAuth)
- Configure notification settings
- Test the connection
- Enable the integration
On Quackback Cloud, Quackback provides the OAuth apps, so you connect in a few clicks. Self-hosted instances create their own app with each provider first. Each integration's article explains how.
Note: Configuring integrations needs the Owner or Admin role, or a custom role with permission to manage integrations.
Integration status
Each integration shows its current status:
Status | Meaning |
|---|---|
Connected | Working normally |
Paused | Temporarily disabled |
Error | Connection issue, needs attention |
Not Connected | Not yet set up |
Pause an integration
Temporarily disable an integration without disconnecting:
- Go to the integration settings
- Toggle Enabled off
- The integration pauses but credentials are preserved
Reconnect
If an integration shows errors:
- Check the error message
- Re-authenticate if tokens expired
- Verify the connected service is working
Security
OAuth tokens
Integration OAuth tokens are:
- Encrypted at rest using AES-256-GCM with purpose-specific keys derived via HKDF
- Scoped to minimum required permissions
- Revocable from both Quackback and the connected service
Webhook signing
Webhook deliveries are signed with HMAC-SHA256 so you can verify they came from Quackback. See Webhooks for details.
On post delete
When you delete a feedback post that has linked issues in an issue tracker (Linear, GitHub, Jira, and others), you can archive or close those issues at the same time. The delete dialog shows a checkbox for each linked issue.
Configure the default
Each integration has an On post delete toggle in its settings page. When enabled, the checkbox for that integration's linked issues is pre-checked in the delete dialog. You can always override it per delete.
What happens
- The post is soft-deleted first: this always succeeds
- Selected linked issues are archived or closed in parallel
- If an external API call fails, you'll see a warning toast: the post is still deleted
- The link's status is updated to
archived,closed, orerror
Note: Issue-tracking integrations archive or close linked issues: they never hard-delete them. You can reopen or unarchive in the external tool if needed.
Best practices
Start simple
Tip: Begin with one integration. Add more as your workflow matures.
Map relevant events
Don't send every event to every channel. Be selective:
- New feedback: a general notification channel
- Status changes: specific channels
- Comments: often skipped, or sent to a low-traffic channel
Monitor for errors
Regularly check integration status. Failed notifications can mean:
- Expired tokens
- Removed channels
- Service outages
Troubleshooting
Notifications not sending
- Check integration status for errors
- Verify event mappings are configured
- Check the target channel or endpoint exists
- Review recent activity logs
Duplicate notifications
- Check for multiple event mappings
- Verify you don't have duplicate integrations
- Review webhook retry settings
Connection lost
- Tokens may have expired
- Re-authenticate the integration
- Check the third-party service status
Related articles
- Slack: Send feedback from Slack and get alerts
- GitHub: Turn feedback into GitHub issues
- Webhooks: Send events to any HTTP endpoint
- API overview: Build your own integration with the REST API
- What's included on each plan: Which plans include integrations
Was this helpful?
Your feedback shapes what we write next.