The problem with HTML in a message
Upload a page to a channel and Slack renders it as a code block. Everyone in the thread has to download the file, find it, and open it locally — and half of them are on a phone. The content was fine; the container was wrong.
What to do instead
Publish the file and post the link. The reader clicks once and sees the rendered page, and the link is unguessable, so a message forwarded out of the workspace is still governed by whatever gate you put on the page.
curl -X POST https://read.botook.ai/sites \
-H "Authorization: Bearer otr_live_YOUR_KEY" \
-F file=@launch-status.htmlIs there an app to install?
Not in this deployment. A distributed Slack app means an app listing, a review, and an OAuth install flow per workspace, and none of that is something a self-hosted deployment should be forced to inherit. Everything below gets the same result with pieces you already control.
A workflow step, no app review
Slack's own workflow builder can call a webhook. Point one step at a small function that publishes the file and posts the URL back into the channel:
# in a Cloudflare Worker, a Lambda, or whatever you already run
const published = await fetch("https://read.botook.ai/sites", {
method: "POST",
headers: { authorization: "Bearer otr_live_YOUR_KEY" },
body: form, // the file from the Slack event
}).then((r) => r.json());
await fetch(SLACK_WEBHOOK_URL, {
method: "POST",
body: JSON.stringify({ text: "Private link · " + published.url }),
});One click on the message shortcut in the workflow, one launch of the step, and the thread has a link instead of a code block.
Or let the agent post it
If the agent that wrote the page is already in your workspace — a Slackbot, an assistant, a CI job — give it the key and let it publish and post in one turn. The tool call is the usual one:
publish_html({
content: "<!doctype html><title>Q3 review</title>…",
expires_in_hours: 168,
password: "optional",
agentation: true
})Gate it before it is shared
A message gets forwarded; that is what messages are for. The gate travels with the page, not with the message:
- Password — a passcode the client already has, checked before any content is served.
- Work-email gate — only addresses at one domain may open it.
- Expiry — the link stops existing after N hours, permanently.
- Burn after read — the first successful open is the last.
Files that are not HTML
Markdown is rendered on the way in, so a design note pasted into a channel becomes a readable page rather than a screenful of asterisks. An SVG diagram is hosted as-is. A zip of a build directory is unpacked and served as a tree.
Where the links live afterwards
In the dashboard: every page you have shared, its opens and unique viewers, and one button to revoke. Anyone with the link can read; nobody without it can find it, because there is nothing to find — the token is 22 random characters and the page is never indexed.
If you do want a real app
Nothing stops you: this is your deployment. Create a Slack app in your own workspace, give it
a message shortcut, complete the OAuth install against your own workspace only, and have the
handler call POST /sites. There is no review to pass for an internal app, and the
server side is the one curl above.
What the unfurl looks like
Slack expands a pasted link into a card. The card here uses a real screenshot of the published page, so the thread shows what the page is rather than a bare URL. A gated page is the exception: it unfurls as a placeholder on purpose, because an image of a password-protected page would hand over the thing the password was protecting. Take the gate off and the screenshot is regenerated without anyone having to ask for it.
Who opened it
Posting a link into a busy channel tells you nothing about whether anyone read it. The engagement endpoint does — aggregate only, which is the right amount for a colleague:
curl -s https://read.botook.ai/sites/SITE_ID/engagement \
-H "Authorization: Bearer otr_live_YOUR_KEY" | jq '{opens,unique_viewers,read_to_end}'Opens and unique viewers are different numbers, and the gap between them is usually the answer to "did the channel read this, or did one person read it eight times?"
Threads end; links should too
A status page posted on Tuesday is misinformation by Friday. Give it an expiry that matches the half-life of the content, and it removes itself — the record and the stored object both go, which is better than a stale page quietly staying correct-looking:
curl -X PATCH https://read.botook.ai/sites/SITE_ID \
-H "Authorization: Bearer otr_live_YOUR_KEY" \
-H "content-type: application/json" \
-d '{"expires_in_hours":72}'Questions
Does the recipient need an account?
No. The link opens in any browser with no login.
Can I stop a link that left the channel?
Delete the site, or revoke that one share token and leave the others alone.
Does it work in a DM?
The link is just a URL — DM, channel or email, it behaves the same.