Notifications
Connect Slack
B2B quote alerts, delivered straight into Slack.
Overview
Slack + TackQuote
TackQuote's Slack integration posts to Slack on three quote events — a quote is sent, a buyer accepts one, and a quote enters approval — and on any workflow you build with the Notify Slack automation action. A buyer viewing a quote or requesting a revision still produces no Slack message. Delivery is a single Slack incoming webhook per workspace, so every message lands in the one channel that webhook was created against; there is no per-event channel routing. If the webhook is missing or Slack rejects the post, the event alerts are dropped and logged rather than retried — but a Notify Slack automation action FAILS the workflow run and records the reason, so an unconnected workspace is visible rather than silent.
TackQuote connects to Slack with an incoming webhook URL you paste in. There is no TackQuote Slack app and no OAuth flow.
Before you start
What you'll need
- Slack Free, Pro, Business+, or Enterprise Grid
- Permission to create an incoming webhook in the channel you want messages in
- TackQuote Basic plan or above
Setup
How to connect Slack
Create a Slack incoming webhook
In Slack, create an incoming webhook for the channel you want TackQuote to post in. The channel is chosen here, in Slack — that choice is what decides where every TackQuote message lands.Paste the webhook URL into TackQuote
In TackQuote Integrations → Slack, paste the hooks.slack.com URL. There is nothing else to configure: the three events that post on their own are fixed and cannot be enabled, disabled or re-routed. Anything beyond them is built as a workflow automation using the Notify Slack action.Tell your team the rep is named, not pinged
There is no email-to-Slack-member mapping to set up, because TackQuote does not build Slack mentions. The rep’s name appears as text in the message.Test and confirm
Send a test notification from TackQuote settings. Once it appears in the channel the webhook is bound to, you're live.
Capabilities
What you get
Event-Based Alerts
Three events reach Slack on their own: quote sent, buyer acceptance, and a quote entering approval. Created, viewed, commented, rejected, expired and converted do not post to Slack automatically — but any trigger TackQuote fires can be routed to Slack yourself with the Notify Slack automation action.
One Channel Per Workspace
TackQuote stores a single Slack incoming webhook per workspace, so every message goes to whichever channel you created that webhook against. Sending different events to different channels is not supported: Slack does not let an incoming webhook be redirected by the message payload, which is also why the Notify Slack automation action has no channel box.
Rich Message Format
The quote-sent message carries the quote number, buyer name and email, amount, and a link to the buyer portal. The acceptance message carries the quote number, buyer name, amount and rep name, but no link.
Rep Named, Not Mentioned
Messages show the owning rep’s name as plain text. Slack only turns a real Slack member ID into a mention, and TackQuote holds no mapping from a TackQuote user to a Slack member, so nobody is notified by name — watch the channel rather than relying on a ping.
FAQ
Slack questions
Is there a TackQuote Slack app, or is it webhook only?
An incoming webhook is the only method. TackQuote has no Slack app and no OAuth flow, so the webhook URL is what you connect with.
Can we send notifications to private Slack channels?
Yes — create the incoming webhook against the private channel and TackQuote posts there. There is no TackQuote app to add to the channel.