When a customer leaves feedback, the worst thing that can happen is nobody seeing it until three days later. By connecting Feedbaxster to Slack, new suggestions, issues, and status changes appear in a channel your team already watches — no extra tab, no email to dig through.
The setup takes about five minutes.
What you'll need
- A Feedbaxster account with a business set up and an owner or manager role
- A Slack workspace where you have permission to install apps
No paid Slack plan required. The free tier works fine.
Step 1: Create a Slack app
Head to api.slack.com/apps and click Create New App. You'll see two options — pick From scratch.
Give your app a name. Something like Feedbaxster or Feedbaxster Notifications works. Select the workspace you want to send notifications to, then click Create App.
You'll land on the app's settings page. Don't worry about most of what's here. You only need one feature.
Step 2: Turn on Incoming Webhooks
In the left sidebar, under Features, click Incoming Webhooks. Flip the toggle at the top of the page to On.
That's all you need to enable. Incoming Webhooks let external services post messages to a Slack channel by sending data to a URL. No OAuth flow, no bot permissions, no scopes to configure.
Step 3: Create a webhook for a channel
Scroll down and click Add New Webhook to Workspace.
Slack asks you to pick a channel. This is where Feedbaxster notifications will land. Some naming ideas:
#feedbackfor one central place for all customer input#customer-feedbackif your team already uses#feedbackfor internal product discussions#alertsif you prefer mixing feedback with other operational notifications
Pick the channel and click Allow. If the channel doesn't exist yet, create it in Slack first, then come back.
After clicking Allow, you'll see a new Webhook URL in the list. It starts with https://hooks.slack.com/services/ followed by a long string. Click Copy.
Step 4: Add the webhook in Feedbaxster
In your Feedbaxster dashboard, go to Settings > Integrations and click Add Slack.
The setup form has three fields:
Name — A friendly label for this integration. If you're sending to #feedback, just call it feedback. If you plan to set up multiple channels for different event types, name them accordingly (e.g., feedback-ops, new-feedback).
Webhook URL — Paste the URL you copied from Slack. It must start with https://hooks.slack.com/ or Feedbaxster will reject it.
Events — Choose which events trigger a Slack message. Feedback events like suggestion.created, issue.created, and suggestion.analyzed notify you when new feedback arrives or when the AI finishes analyzing a suggestion. Status changes like suggestion.status_changed, issue.assigned, and issue.resolved keep the team updated as feedback moves through your workflow. You can also subscribe to activity events (comments, QR scans), team events, and moderation alerts. Pick what matters and skip the rest — you can change this later.
Click Create Integration.
Step 5: Send a test message
Back on the integrations page, find the Slack card you just created and click Test. Feedbaxster will send a sample message to your channel.
If it works, you'll see a toast confirming delivery. Switch to Slack and check the channel. You should see a formatted message with a header, event details, and a button to view more.
If the test fails, double-check that the webhook URL is correct (no trailing spaces, no missing characters), the Slack app still has the webhook enabled, and the channel you selected exists and hasn't been archived.
What the notifications look like
Feedbaxster formats Slack messages using Block Kit, so they're structured rather than plain text. A typical notification includes a header with the event type (e.g., "New Suggestion" or "Issue Resolved"), fields showing status, priority, and sentiment when available, the customer's name if they provided one, and a "View Details" button linking back to your dashboard.
You can't customize the message template, but the default structure covers the essentials without being noisy.
Setting up multiple channels
You're not limited to one Slack integration. A common setup for larger teams: #feedback receives suggestion.created and issue.created for the front-line team, #feedback-ops gets suggestion.status_changed, issue.assigned, and issue.resolved for managers tracking workflow, and #moderation gets spam.spike_detected so you know if something unusual is happening.
Each integration is independent. Create a separate webhook URL in Slack for each channel, then add each one in Feedbaxster with the relevant events.
Disabling or removing an integration
To pause notifications temporarily, toggle the switch on the integration card. The webhook stays configured but Feedbaxster stops sending to it.
To remove it entirely, click the trash icon. This deletes the integration from Feedbaxster but doesn't touch the Slack app itself. To clean up on the Slack side too, go back to api.slack.com/apps, select your app, and remove the webhook URL from the Incoming Webhooks page.
Checking delivery history
Every Slack notification Feedbaxster sends is logged. Click Logs on any integration card to see which events were sent, when, the HTTP response code, and whether delivery succeeded or failed.
This is useful for debugging when you suspect messages aren't arriving. A 200 response means Slack accepted the message. Anything else points to a problem with the webhook URL or the Slack app configuration.
The gap between a customer leaving feedback and your team acting on it is where things get lost. A Slack integration closes that gap to near-zero. Set it up once and every piece of feedback finds its way to the people who can do something about it.