Chat integration
The weekly briefing, in Teams.
Same composed digest as Slack and email, rendered as a Teams card. Set up with a channel webhook, which means no app package to submit and no tenant-wide consent to chase.
- 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
Microsoft Teams + Weekwright.
- The weekly manager briefing as a native Teams card rather than a pasted block of plain text.
- One channel webhook to configure. No Teams app package, no tenant admin consent, no Graph permissions.
- A test post on save — a URL that fails the test is refused rather than stored.
- The same SSRF gate as every other outbound URL in the product: private ranges, metadata IPs, and lookalike hosts are rejected before a request is made.
Setup
How it works.
- 1
In Teams, add an Incoming Webhook connector to the target channel and copy the generated URL.
- 2
In Weekwright, paste it into the briefing settings. Admin or owner only.
- 3
A test card posts immediately; if it fails, the URL is not saved.
- 4
The weekly briefing then posts to that channel on its normal schedule.
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 notification delivery. No bot, no mentions, no actionable buttons — approvals happen in the app.
- One channel per organization, not one per location or per manager. Fanning the briefing out to several channels is easiest done with a Power Automate flow on your side.
- Microsoft has been migrating Teams connectors toward Power Automate Workflows. If your tenant has retired the classic Incoming Webhook connector, a Workflows-generated URL that accepts a JSON POST works with the generic renderer.
- It delivers the weekly briefing, not individual shift alerts. Those stay in in-app notifications and email on purpose, so the Teams channel does not turn into noise the team mutes.
Common questions
Microsoft Teams FAQ.
Is there a Weekwright app for Microsoft Teams?
No, and that is deliberate. A channel webhook delivers the briefing today with no app package, no submission process, and no tenant-wide consent. A full Teams app is only worth building if customers need two-way interaction.
What if my tenant has disabled Teams connectors?
Create a Power Automate workflow with an HTTP-request trigger that posts to the channel, and use that URL. Weekwright can also emit a generic JSON payload for a receiver that expects its own shape.
Can I send it to more than one channel?
Not currently — it is one briefing webhook per organization. Fan-out to several channels is easiest handled by a Power Automate flow on your side.
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.