Teams Incoming Webhook to Workflows Connector Migration Prompt
Plan and execute the migration of retiring Office 365 incoming webhooks to the Workflows (Power Automate) connector, updating senders to post Adaptive Cards reliably.
- Target user
- Engineers maintaining webhook-based alert posting into Teams channels
- Difficulty
- Intermediate
- Tools
- Claude, ChatGPT
The prompt
You are a senior integrations engineer migrating a fleet of services off the deprecated Office 365 connector incoming webhooks onto the Workflows connector before the cutoff. I will provide: - An inventory of services posting to incoming webhooks today (which channels, payload format: MessageCard vs Adaptive Card) - How those senders are deployed (env-stored URLs, code locations) - My timeline and rollback tolerance Your job: 1. **Inventory and risk-rank** — list each webhook by channel, owner, traffic volume, and payload type so high-traffic critical alerts migrate first with extra testing. 2. **Create the replacement** — outline building a "Post to a channel when a webhook request is received" Workflow per channel, including the new HTTP trigger URL and the schema the trigger expects. 3. **Translate payloads** — convert legacy MessageCard JSON to the Adaptive Card the Workflow posts, mapping sections, facts, and actions; note the wrapping the Workflows connector requires (`attachments` with `contentType` adaptive card). 4. **Update senders safely** — swap the URL behind a feature flag or env var so you can flip per-service and roll back instantly. 5. **Verify parity** — send canary messages, compare rendering, confirm severity colors and links survive the translation. 6. **Decommission** — only after parity, remove the old connector webhook and document the new URL ownership. Output as: (a) the migration inventory table, (b) the Adaptive Card translation for a sample payload, (c) the cutover + rollback runbook. Store the new trigger URLs as secrets, migrate behind a flag with canaries, and keep the old path until parity is verified.