Bug reports, straight into your Teams channels

Every share becomes an Adaptive Card carrying the page, the environment, diagnostics and a link to the annotated screenshot. Setup is a single Workflows webhook, created in Teams and pasted into BugCapturer.

Live in three steps

Create the workflow in Teams, paste the URL into BugCapturer, confirm the test card.

1

Create a Workflows webhook

Open the channel β†’ β‹― β†’ Workflows, pick the template "Post to a channel when a webhook request is received", confirm the channel and Save.

β†’
2

Paste it into BugCapturer

Integrations β†’ Microsoft Teams β†’ Add integration. Only Power Automate hosts are accepted.

β†’
3

Confirm the test card

We post a test card when you save. Once it appears, every new share lands in that channel.

Everything a developer needs at a glance

Adaptive Cards render natively in Teams on desktop, web and mobile.

πŸ–ΌοΈ

Screenshot link

A link to the annotated screenshot is always included; Teams renders the image inline when it can fetch it.

🧭

Page & environment

Page title, linked to the sanitized URL, plus browser, OS and screen resolution.

πŸ”’

Diagnostics counts

Console and network error counts only β€” error contents can contain tokens and a channel is a public surface.

πŸ”€

One webhook, one channel

Add one integration per channel. Cards carry a single OpenUrl button, so the integration stays a thin notification layer.

Built like every other BugCapturer integration

Retries, delivery logs and auto-disable are shared with all other targets.

πŸ”

Retries with backoff

Workflows replies 202 Accepted on success; failures are retried twice (5s / 15s) before being recorded.

⏸️

Auto-disable

20 consecutive failures pause the integration and email you, so a disabled workflow cannot fail silently forever.

πŸ”’

Credential-safe

The webhook URL is treated as a secret: we only ever show its last 6 characters back.

🧾

Delivery log

Every attempt, status code and error summary is kept for the last 20 deliveries.

Teams retired the old Incoming Webhook connectors

If a tutorial tells you to open Channel β†’ Connectors β†’ Incoming Webhook, it is out of date: Microsoft retired those connectors on 22 May 2026 and connector URLs no longer work. The supported path is the Workflows app.

🚫

Use Workflows instead

BugCapturer rejects legacy *.webhook.office.com connector URLs and only accepts Power Automate hosts.

πŸ€–

Posted by the Flow bot

Cards appear as the Workflows bot. The icon and display name cannot be customised.

πŸ‘€

Owned by a person

A workflow belongs to whoever created it. Create it with a team account or add a co-owner, otherwise posting stops when that person leaves.