Personal and team-wide notifications
Each user controls toast and email choices under Notifications. Webhooks are organization-level integrations under Develop → Webhooks, making them the right channel for a team room, incident channel, or release feed.
Clickable alerts while a user is signed in.
Account-level delivery when the recipient is outside Maxlona.
Adaptive Cards posted by a Teams Workflow for selected events.
What can be sent to Teams?
Choose the signals a channel needs, or select every available event for a complete operational feed. Scope a webhook to one flag or environment when needed.
| Area | Events | Useful for |
|---|---|---|
| Flags | created, updated, deleted, archived, promoted, toggled | Release visibility |
| Approvals | pending, approved, rejected | Review queues and governance |
| Kill switch | activated, cleared | Incident response |
| Billing | subscription activated/canceled, payment succeeded/failed | Account health |
Connect Microsoft Teams
Create a Teams Workflow
In the target Teams channel, open Workflows and choose the template that posts to a channel when a webhook request is received. Select the Team and channel, finish setup, and copy the generated URL.
Find more info →Add the webhook in Maxlona
Go to Develop > Webhooks, select Add Webhook, paste the Workflow URL, and choose Microsoft Teams as the channel type.
Choose events and scope
Select the event types the channel should receive. Leave Flag and Environment at Any for an organization-wide feed, or narrow them for a release or incident channel.
Test and verify delivery
Save the webhook and select Test. Confirm the Adaptive Card in Teams, then use Deliveries in Maxlona to inspect responses or replay a failed attempt.
- Flag:
- new-payment-screen
- Environment:
- Prod
- Project:
- Mobile App
- Action:
- enabled
- Actor:
- me@server.com
Delivery and security
Reliable delivery
Every attempt is recorded. Failed requests retry with exponential backoff up to five attempts, and operators can replay a delivery.
Treat the URL as a secret
Anyone holding a Workflow URL may be able to post to it. Keep it out of source control and replace the workflow URL if exposed.