Appearance
Slack integration
Slack works two ways here, and they are configured in different places. It is worth knowing which one you are asking for.
Platform alerts
Taufinity posts operational alerts to a Slack incoming webhook you supply. These are about the platform's own health and cost, not about your content.
| Alert | When |
|---|---|
| AI spend threshold | Generation cost crosses a configured threshold |
| Budget response | A spending cap engages and generation is throttled or paused |
| Monitoring incident | An alert fires against a deployed site or the platform |
| Canary heartbeat | A scheduled canary stops reporting |
| Agent run outcome | A background agent run finishes or fails |
Messages from your own playbooks
Any playbook can post to Slack itself using the webhook step pointed at an incoming webhook URL. The URL is stored as an organisation credential, so it never appears in the playbook configuration.
That is the route for anything content or business shaped: a draft dropped in a channel for review, a link to an approval screen, a morning digest built from a warehouse query.
What the Slack integration can be used for
Slack can be used for cost visibility, so a generation run that crosses a spend threshold is noticed the same morning rather than at the end of the month.
Slack can be used for failure alerting, so a paused pipeline surfaces in a channel instead of waiting to be discovered.
Slack can be used for review handoffs, dropping a draft or a link to the approval screen into the channel that reviews it.
Slack can be used for scheduled business digests, where a playbook queries the warehouse on a cadence and posts the result.
Slack can be used without giving Taufinity access to your workspace, because an incoming webhook posts to one channel and can read nothing.
Slack combined with other integrations
| Combination | What it gives you |
|---|---|
| Slack + Shopify | A daily revenue, orders and refunds digest, built by a scheduled playbook |
| Slack + webhooks | Any playbook step can post its own message, with the URL held as a credential |
| Slack + social channels | A link to the week's distribution queue, so approval happens in one sitting |
| Slack + playbooks | Every failure surfaced, with a link straight to the run |
What you need to connect Slack
- An incoming webhook URL for the channel you want to post into
- For playbook messages, that URL stored as an organisation credential
Frequently asked
Can people approve from inside Slack? Not today. The message carries a link to the approval screen. Interactive approval buttons are on the roadmap.
Does it read our messages? No. An incoming webhook is send-only. Taufinity has no read access to your workspace.
Can different playbooks post to different channels? Yes. Each webhook credential points at one channel, and a step chooses which credential to use.