Skip to content

Add system-scoped webhook routing for offboarding and drift notifications#27

Draft
Copilot wants to merge 6 commits intodevfrom
copilot/add-webhook-configuration-options
Draft

Add system-scoped webhook routing for offboarding and drift notifications#27
Copilot wants to merge 6 commits intodevfrom
copilot/add-webhook-configuration-options

Conversation

Copy link

Copilot AI commented Feb 22, 2026

Webhook delivery was effectively global, which limited control for workflows like user offboarding and drift alerts. This change adds optional system-scoped webhook paths so specific flows can route to dedicated endpoints while preserving existing default webhook behavior.

  • Notification settings: add scoped webhook fields

    • Added optional offboardingWebhook and driftWebhook to notification config persistence and execution paths.
    • Updated config listing logic so these fields are treated as config fields (not log categories).
    • Updated OpenAPI for ExecNotificationConfig to include both new optional properties.
  • Offboarding alert routing

    • Offboarding completion alerts now call scheduled alerting with TaskType = 'Offboarding'.
    • Scheduled webhook alert logic now resolves offboardingWebhook from notification config for offboarding tasks and passes it via -altWebhook.
    • If not configured, alerting falls back to existing default webhook resolution.
  • Drift alert routing

    • Drift management now resolves webhook target from notification config (driftWebhook) first.
    • If unset, existing template-level driftAlertWebhook remains the fallback.
  • Focused regression coverage

    • Added endpoint tests validating:
      • persistence of scoped webhook settings in notification config
      • offboarding webhook override selection in scheduled task alerting
# Scoped override with fallback behavior
$webhook = if ($NotificationConfig.driftWebhook) {
    $NotificationConfig.driftWebhook
} else {
    $Settings.driftAlertWebhook
}
Original prompt

Currently there is limited options for webhook outputs within the system, without letting people send wehioks everywhere perhaps we can have a more detailed webhook configuration section in settings that would allow you to configure webhook paths for different systems. Like the user off boarding wizard can go the the default not if configured go to the iffboarding webhook path. I think drift templates also red have this as an option but this would instead be configured for the system. Any other endpoint this would be good for?


💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

Copilot AI and others added 3 commits February 22, 2026 03:24
Co-authored-by: Zacgoose <107489668+Zacgoose@users.noreply.github.com>
Co-authored-by: Zacgoose <107489668+Zacgoose@users.noreply.github.com>
Co-authored-by: Zacgoose <107489668+Zacgoose@users.noreply.github.com>
Copilot AI changed the title [WIP] Add detailed webhook configuration section in settings Add system-scoped webhook routing for offboarding and drift notifications Feb 22, 2026
Copilot AI requested a review from Zacgoose February 22, 2026 03:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants