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.

JM
James Morton
Written By James MortonLast updated 8 days ago

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 AI assistant (@Quackback and /quackback), and the "Send to Quackback" shortcut
  • 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. When the issue changes status, GitHub and Linear update the ticket using your ticket status mapping. Jira and Azure DevOps send the change to the integration's Sync history for review.

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:

  1. Something happens in Quackback (for example, a post is created).
  2. Quackback dispatches the event.
  3. Each integration mapped to that event runs.
  4. The integration sends its notification or creates its issue.

Events

Integrations can respond to these post, comment, changelog, and status events. Conversation, ticket, SLA, assistant, and approval events also exist.

Event

Description

post.created

New feedback post submitted

post.status_changed

Post status updated (for example, Planned to Shipped)

post.updated

Post title or content edited

post.deleted

Post soft-deleted

post.restored

Deleted post restored

post.merged

Post merged into another post

post.unmerged

Merged post split back out

post.mentioned

Someone is @-mentioned on a post

post.owner_assigned

An owner is assigned to a post

post.voted

A vote is cast on a post

comment.created

New comment on a post

comment.updated

Comment edited

comment.deleted

Comment deleted

changelog.published

Changelog entry published

status.incident_created

Status page incident created

status.incident_updated

Status page incident updated

status.maintenance_scheduled

Maintenance window scheduled

status.maintenance_started

Maintenance window started

status.maintenance_completed

Maintenance window completed

status.component_changed

Status page component changed state

Event mappings

Configure which events trigger which integrations:

  1. Go to Admin > Settings > Integrations
  2. Select an integration
  3. Configure Event Mappings
  4. Choose which events to send

For example, send only new posts from your Bug Reports board to a #bugs channel in Slack.

Set up an integration

  1. Go to Admin > Settings > Integrations
  2. Click the integration you want to set up
  3. Follow the connection flow (usually OAuth)
  4. Configure notification settings
  5. 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

Off

Paused: the integration is temporarily disabled

Error

Connection issue, needs attention

No badge

Not yet set up. Open the integration to connect it.

Paused integrations

To pause an integration without disconnecting it, open it in Settings > Integrations and turn off its switch. The switch is called Integration enabled on most integrations, Notifications enabled on Discord, ntfy and Microsoft Teams, and Webhook enabled on automation tools such as Make. While it is off, Quackback stops sending events to that service and keeps its connection and settings. A paused integration shows an Off badge in the integration list and on its page. Turn the switch back on to resume.

Reconnect

If an integration shows errors:

  1. Check the error message
  2. Re-authenticate if tokens expired
  3. 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
  • Revoked with the connected service when you disconnect, where that service supports it

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), the delete dialog shows a checkbox for each linked issue. Checked issues are added to the integration's Sync history for review. Quackback doesn't archive or close them for you: open each one in the tracker and archive or close it there.

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
  • Each checked linked issue is added to Sync history for manual review
  • Quackback never archives, closes, or deletes issues in the tracker itself

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

  1. Check integration status for errors
  2. Verify event mappings are configured
  3. Check the target channel or endpoint exists
  4. Review recent activity logs

Duplicate notifications

  1. Check for multiple event mappings
  2. Verify you don't have duplicate integrations
  3. Review webhook retry settings

Connection lost

  1. Tokens may have expired
  2. Re-authenticate the integration
  3. Check the third-party service status

Was this helpful?

Your feedback shapes what we write next.

Related articles

SlackConnect Slack to get notified about new feedback, status changes, comments, changelog and support activity, ask the Quackback AI assistant questions, and send any Slack message to Quackback with a shortcut.ZapierConnect Zapier with a Catch Hook webhook URL to trigger Zaps when feedback is submitted, a status changes, or someone comments, and see the payload for each event.DiscordConnect Discord to post rich embed notifications to your server's channels when new feedback arrives, a post status changes, or someone comments.ClickUpConnect ClickUp to create tasks in a chosen list from new feedback and review status changes when a linked ClickUp task's status changes.