Project Webhooks

The Webhooks tab enables configuring HTTP endpoints to receive real-time notifications when specific events occur in your project. External systems receive instant POST requests instead of polling the API, enabling automated workflows and integrations with custom applications.

Overview

The interface displays a table of pre-defined webhook events organized by category. Each event has an endpoint URL field where you enter your receiving server's address. When an event occurs, GitScrum sends an HTTP POST request to the configured URL with event data.

The header shows statistics including the total number of loaded webhooks and how many are currently active (have a URL configured).

Webhook Categories

Events are grouped into expandable categories. Click a category header to expand or collapse its events.

Tasks

Webhooks for task-related events:

Task Created (issues.store) - Triggered when a new task is created
Task Updated (issues.update) - Triggered when task fields are modified
Task Moved on Board (issues.move.board) - Triggered when a task changes workflow stage
Task Assignees Changed (issues.assignees) - Triggered when task assignments change
Task Deleted (issues.destroy) - Triggered when a task is removed
Task Moved to Project (issues.move.project) - Triggered when a task is transferred to another project
Time Tracking (time-tracking) - Triggered when time is logged on a task

User Stories

Webhooks for user story events:

User Story Events (user-stories) - Triggered when user stories are created, updated, or deleted

Sprints

Webhooks for sprint events:

Sprint Events (sprints) - Triggered when sprints are created, started, completed, or modified

Others

Webhooks for additional project events:

Discussions (discussions) - Triggered when discussions are created or updated
Comments (comments) - Triggered when comments are added to tasks
Attachments (attachments) - Triggered when files are attached
Videos (videos) - Triggered when videos are added

Configuring a Webhook

Expand the category containing the event you want to configure
Locate the event row in the table
Enter your endpoint URL in the input field
Press Enter or click outside the field to save
The status indicator turns green when saved successfully

The endpoint URL must be a valid HTTP or HTTPS URL. HTTPS is recommended for security.

Webhook Status Indicators

Each webhook displays a status indicator:

Green dot - Webhook is active with a configured endpoint
Gray dot - Webhook has no endpoint configured

The category header shows a count of active webhooks within that category (e.g., "2/7" means 2 of 7 webhooks have URLs configured).

Testing Webhooks

Test Individual Webhook

Configure an endpoint URL for the webhook
Click the test icon button (pulse icon) in the Actions column
A test payload is sent to your endpoint
Success or error message appears below the input field

Test All Webhooks

Click the Test All button in the header to send test requests to all configured webhooks simultaneously. This is useful for verifying your entire webhook configuration at once.

Removing a Webhook

Click the X icon in the Actions column
The endpoint URL is cleared
The status indicator turns gray
No further events are sent to that endpoint

Endpoint Requirements

Your webhook endpoint should:

Accept HTTP POST requests
Return a 2xx status code within 30 seconds
Be publicly accessible from GitScrum servers
Handle potential retries gracefully

Best Practices

The info section at the bottom of the page displays key recommendations:

Use HTTPS - Encrypt webhook data in transit
Return 2xx status - Acknowledge receipt immediately
Handle retries - Same event may be delivered multiple times

Integration Examples

Custom Automation: Configure webhooks to trigger your internal systems when tasks change status, enabling custom workflows.

External Dashboards: Send task and sprint events to update real-time dashboards outside GitScrum.

Notification Systems: Route events to your own notification infrastructure for custom alerting.

Workflow Tools: Use webhook URLs from automation platforms like Zapier, Make, or n8n to trigger multi-step workflows.

API Access - Generate API tokens for programmatic access
Integrations - Pre-built integrations with Slack, Discord, Teams, and Git providers