Chat integration
The weekly briefing, in the channel.
Weekwright composes a weekly digest — coverage gaps, pending time-off, compliance warnings, who is over their cap — and posts it into Slack as properly formatted Block Kit rather than a wall of text.
- Category
- Chat
- Setup
- 5 minutes, once
- Who sets it up
- An admin or owner
- Plans
- The delivery channel is ungated; the weekly manager briefing it delivers is a Pro-plan feature.
What you get
Slack + Weekwright.
- The same composed briefing that goes out by email, rendered as native Slack Block Kit with sections and dividers.
- Set-up is one incoming webhook URL. No Slack app to install, no OAuth scopes, no workspace admin review.
- Saving the webhook posts a test message first — and if that test fails, Weekwright refuses to save the URL at all, so a broken channel never silently swallows the briefing.
- The URL is validated against a SSRF gate before anything is sent: private IP ranges, cloud metadata endpoints, and embedded-credential URLs are rejected.
Setup
How it works.
- 1
In Slack, create an incoming webhook for the channel you want (Slack: Apps → Incoming Webhooks → Add to Slack → pick the channel).
- 2
In Weekwright, open the briefing settings and paste the webhook URL. Admin or owner only.
- 3
Weekwright posts a test message immediately. If it does not arrive, the URL is not saved — fix it and retry.
- 4
From then on, the weekly briefing posts to that channel alongside its email delivery.
Honest limits
What this does not do.
Every integration has edges. Better you read them here than discover them the week you go live.
- One-way. Weekwright posts into Slack; it does not read messages, and there are no slash commands or interactive buttons. Approving time-off still happens in the app.
- It is one channel per org, not per location or per manager.
- It delivers the weekly briefing — not every notification. Shift-level alerts go through in-app notifications and email, deliberately, so Slack does not become noise nobody reads.
- An incoming webhook posts to the channel it was created for. Moving the briefing to a different channel means a new webhook URL.
Common questions
Slack FAQ.
Do I need to install a Slack app?
No. It uses a standard Slack incoming webhook, which you create in your own workspace and paste into Weekwright. Nothing is installed on the Weekwright side and no OAuth scopes are requested.
Can my team run scheduling commands from Slack?
Not today, and we would rather say so than ship a half-working slash command. The integration is one-way notification delivery. Scheduling actions happen in the app or the mobile app, where the permission checks and audit trail live.
What is in the weekly briefing?
The composed digest covers the upcoming week's coverage gaps, pending time-off decisions, compliance warnings, and cross-week load signals — the things a manager would otherwise go looking for on a Sunday night. The briefing itself is a Pro-plan feature.
One tool for the schedule, wired into the rest of your stack.
Free for a single location, no credit card. The delivery channel is ungated; the weekly manager briefing it delivers is a Pro-plan feature.