Last updated

Webhook Channels

A webhook channel sends work-item events from Windshift to an external HTTP endpoint. Use it to notify another system when selected work changes.

This is different from an incoming source-control webhook. GitLab project callbacks belong to SCM Integrations.

Configure an outbound webhook

Creating a channel requires a system administrator. Assigned channel managers can maintain its configuration.

  1. Open Admin, then Channels.
  2. Create an outbound Webhook channel.
  3. Enter the receiving endpoint URL.
  4. Configure a secret and any required request headers.
  5. Select all items or specific workspaces as the scope.
  6. To send events automatically, enable automatic triggers and select the event types.
  7. Send a test webhook and review the result.
  8. Enable the channel and save its settings.

The event picker offers item creation, update, deletion, assignment, and status change events. Configuring a URL alone does not enable automatic triggers.

Scope and access

Prefer specific workspaces when the receiving system does not need instance-wide work. Collection-based scope is not implemented for webhook delivery in 0.9.5, even though older configuration data can contain that scope type.

Manually triggering a webhook requires channel management and view access to the item's workspace. Viewing an item alone is not permission to send it to an external system.

Treat the endpoint as a data recipient. Review the event payload, selected workspaces, secret handling, and custom headers before enabling delivery. A successful test proves that the test request was accepted, not that every future event will be processed correctly.

Use an HTTP Request action step when the external call belongs inside a workspace flow with conditions and other steps. A webhook channel is an event subscription, not a replacement for that flow.