How to Set Up Linear Webhook Notifications with Webhookify

Published Feb 21 202610 min read
Linear webhook setup with Webhookify

Linear is the modern issue tracking and project management tool built for high-performance software teams. Known for its speed, keyboard-first design, and streamlined workflows, Linear helps engineering teams plan sprints, track bugs, and ship products efficiently. While Linear has its own built-in notification system, many teams need webhook notifications delivered outside of Linear -- to Telegram for personal alerts, Discord for community updates, Slack for cross-functional visibility, or mobile push for on-call engineers. Webhookify bridges this gap by capturing Linear webhook events and forwarding them as AI-powered, human-readable notifications to any channel you choose. No custom server, no webhook handler code, no infrastructure to manage.

This guide walks you through connecting Linear webhooks to Webhookify so you can stay on top of issue changes, comments, project updates, and more, wherever you prefer to receive notifications.

Why Monitor Linear Webhooks with Webhookify?

  • Cross-Platform Issue Tracking: Not everyone on your team lives in Linear. Product managers may prefer Slack, executives may want email summaries, and on-call engineers need mobile push notifications. Webhookify routes Linear events to any channel, keeping everyone informed.

  • Priority Issue Alerts: Get instant notifications when high-priority or urgent issues are created or updated. Instead of checking Linear periodically, receive a push notification on your phone the moment a P0 bug is filed.

  • Comment and Discussion Tracking: Stay on top of issue discussions without keeping Linear open. Webhookify notifies you when someone comments on issues you care about, so you can respond quickly from any device.

  • AI-Powered Summaries: Linear webhook payloads contain detailed JSON with issue metadata, state changes, label arrays, and assignee information. Webhookify's AI converts this into clear messages like "Issue ENG-142 moved to In Progress, assigned to Sarah" so you get the key information instantly.

  • External Stakeholder Updates: Use Webhookify to forward issue updates to a Discord channel for your open-source community or a Telegram group for external contractors who do not have Linear access. Keep stakeholders informed without granting them seats.

Prerequisites

  1. A Linear workspace. Sign up at linear.app if you do not have one.
  2. Admin or Settings access in your Linear workspace to create webhooks.
  3. A Webhookify account. Sign up for free at webhookify.app.
  4. A notification channel configured in Webhookify (Telegram bot, Discord webhook, Slack workspace, or Email address).
  5. At least one team and project set up in Linear.

Step-by-Step Setup Guide

1

Create a Webhookify Endpoint

Log in to your Webhookify dashboard at webhookify.app and click "Create Endpoint." Give it a name like "Linear Issue Alerts" or "Linear Project Updates."

Webhookify generates your unique HTTPS endpoint URL:

https://hook.webhookify.app/w/your-unique-endpoint-id

Copy this URL. The endpoint is live immediately and ready to receive webhook payloads from Linear. All incoming data is logged in real time on your dashboard.

2

Configure Your Notification Channel

Navigate to Settings in your Webhookify dashboard and configure your preferred notification channels:

  • Telegram: Connect the Webhookify bot for personal issue alerts. Perfect for engineering leads who want to know about critical issues even when they are away from their desk.
  • Discord: Add a Discord webhook URL for team or community channels. Great for open-source projects where contributors need visibility into issue changes.
  • Slack: Connect your Slack workspace for professional team notifications. Ideal for cross-functional teams where product, design, and engineering need to see issue updates.
  • Email: Enter your email for a permanent log of all Linear changes.
  • Mobile Push: Install the Webhookify app for iOS or Android for on-the-go alerts.

For engineering teams, Slack is often the primary channel for issue updates, with Telegram or mobile push as a backup for urgent issues.

3

Set Up Webhooks in Linear

Configure Linear to send webhook events to your Webhookify endpoint:

  1. Log in to Linear.
  2. Click on your workspace name in the top-left corner and select Settings.
  3. Navigate to API in the Settings sidebar.
  4. Scroll down to the Webhooks section.
  5. Click "New webhook".
  6. In the URL field, paste your Webhookify endpoint URL.
  7. Add a Label for the webhook, such as "Webhookify Notifications."
  8. Under Resource types, select the types of events you want to receive:
    • Issues -- Issue created, updated, removed
    • Issue Comments -- Comment created, updated, removed
    • Projects -- Project created, updated
    • Cycles -- Cycle created, updated
    • Issue Labels -- Label created, updated
  9. Click Create webhook.

Linear will immediately start sending webhook events for the selected resource types to your Webhookify endpoint. Each event is signed with a secret that Linear generates, which is included in the webhook headers.

4

Select Events to Monitor

Linear webhooks are organized by resource type. Each resource type triggers events when that resource is created, updated, or removed:

Issue Events:

  • Issue.create -- A new issue is created in any team.
  • Issue.update -- An issue is modified (status change, assignee change, priority change, label change, title edit, description edit, etc.).
  • Issue.remove -- An issue is deleted or archived.

Comment Events:

  • Comment.create -- A new comment is added to an issue.
  • Comment.update -- A comment is edited.
  • Comment.remove -- A comment is deleted.

Project Events:

  • Project.create -- A new project is created.
  • Project.update -- A project is modified (name, description, status, lead, etc.).

Cycle Events:

  • Cycle.create -- A new cycle (sprint) is created.
  • Cycle.update -- A cycle is modified (scope change, dates, etc.).

Label Events:

  • IssueLabel.create -- A new label is created.
  • IssueLabel.update -- A label is modified.

For most teams, monitoring Issues and Comments is the most valuable starting point. Add Projects and Cycles if you want broader project-level visibility.

5

Test Your Configuration

Verify the setup by creating a test event in Linear:

  1. Open your Linear workspace and navigate to any team.
  2. Create a new issue with a descriptive title like "Test Webhookify Integration."
  3. Within seconds, check your Webhookify dashboard for the incoming webhook payload.
  4. Verify that your notification channel received the alert.
  5. Try additional actions: assign the issue, change its status, add a comment, or update the priority. Each action should trigger a new notification.

If notifications are arriving correctly, your integration is complete. Delete the test issue when you are done.

Linear Webhook Events You Can Monitor

Here is a detailed reference of Linear webhook events that Webhookify captures:

Issue Events:

  • Issue + create action -- New issue created with title, description, priority, team, and assignee
  • Issue + update action -- Issue modified (any field change triggers this)
  • Issue + remove action -- Issue deleted or permanently archived

Comment Events:

  • Comment + create action -- New comment posted on an issue
  • Comment + update action -- Existing comment edited
  • Comment + remove action -- Comment deleted

Project Events:

  • Project + create action -- New project created in the workspace
  • Project + update action -- Project details modified

Cycle Events:

  • Cycle + create action -- New cycle (sprint) created
  • Cycle + update action -- Cycle scope or dates modified

Payload Data: Each Issue event payload includes:

  • Issue ID and identifier (e.g., ENG-142)
  • Title and description
  • State/status (Backlog, Todo, In Progress, Done, Cancelled)
  • Priority (Urgent, High, Medium, Low, No Priority)
  • Assignee information
  • Label names
  • Team name
  • Created and updated timestamps

Real-World Use Cases

  • On-Call Engineer Alerts: Route high-priority issue creation events to mobile push notifications. When a P0 or Urgent bug is filed in Linear, the on-call engineer gets an immediate alert on their phone, even outside business hours.

  • Product Manager Updates: Forward issue status changes to a Slack channel. When an engineer moves an issue from "In Progress" to "Done," the PM sees it in real time without needing to check Linear.

  • Open-Source Community Feed: Send issue and comment events to a public Discord channel. Contributors and community members can follow development progress and see when their reported bugs are being worked on, fostering transparency.

  • Sprint Progress Tracking: Monitor cycle update events to track sprint progress. When issues are added or removed from the current cycle, the team lead gets a Telegram notification, helping them stay on top of scope changes.

Example Notification

When a new issue is created in Linear, Webhookify delivers a notification like this:

{
  "action": "create",
  "type": "Issue",
  "data": {
    "id": "a1b2c3d4-e5f6-7890-abcd-ef1234567890",
    "identifier": "ENG-247",
    "title": "Fix login redirect loop on Safari",
    "description": "Users on Safari are experiencing an infinite redirect loop after OAuth login. Affects version 2.4.1+.",
    "priority": 1,
    "priorityLabel": "Urgent",
    "state": {
      "name": "Todo",
      "type": "unstarted"
    },
    "assignee": {
      "name": "Sarah Chen",
      "email": "sarah@company.com"
    },
    "team": {
      "name": "Engineering",
      "key": "ENG"
    },
    "labels": [
      { "name": "Bug" },
      { "name": "Safari" }
    ],
    "createdAt": "2026-02-21T09:15:00.000Z"
  },
  "url": "https://linear.app/company/issue/ENG-247"
}

Webhookify's AI summary would display:

New Linear Issue ENG-247 (Urgent): "Fix login redirect loop on Safari" -- Assigned to Sarah Chen. Team: Engineering. Labels: Bug, Safari. Status: Todo.

This lets you immediately assess the issue's urgency and context without clicking through to Linear.

Troubleshooting

  1. No events received after creating the webhook: Verify that you selected at least one resource type (e.g., Issues) when creating the webhook in Linear Settings > API > Webhooks. If no resource types are selected, no events will be sent.

  2. Events are received for all teams, but you only want specific teams: Linear webhooks fire for all teams in the workspace by default. You cannot filter by team at the webhook level. However, you can use multiple Webhookify endpoints and check the team field in the payload to route notifications appropriately.

  3. Comment events are missing the issue context: Linear Comment webhooks include a reference to the parent issue, but the full issue details may not always be embedded. The payload includes the issueId and issue URL so you can quickly navigate to the full context.

  4. Too many update events for minor changes: Issue update events fire for every field change, including minor edits like description formatting. If the notification volume is too high, consider monitoring only create events initially and adding update events later for specific use cases.

  5. Webhook stops working after changing workspace settings: If you regenerate API keys or change workspace security settings in Linear, existing webhooks may be affected. Re-verify the webhook configuration in Linear Settings > API > Webhooks and recreate it if necessary.

Linear's webhook payloads include the url field with a direct link to the issue or resource. Webhookify preserves this in the notification, so you can click directly from your Telegram, Slack, or Discord notification to open the issue in Linear. This creates a seamless flow from notification to action.

Stay on Top of Linear Issues in Real Time

Create a free Webhookify endpoint and get instant Linear issue, comment, and project notifications on Telegram, Discord, Slack, or your phone.

Get Started Free

Related Articles

Frequently Asked Questions

How to Set Up Linear Webhook Notifications with Webhookify - Webhookify | Webhookify