Linear Trigger

Overview

The Linear trigger fires your procedure when issues, comments, or projects change in your Linear workspace — for example when an issue is created, a label is applied, or a project status changes.

Setup

1. Go to Connections in the Rapidfolio dashboard and connect your Linear workspace.
2. Open the procedure you want to trigger and add a Linear trigger.
3. Select the resource types and actions you want to listen for, then save the trigger.
4. Copy the generated webhook URL and register it in your Linear workspace settings under API → Webhooks → Create webhook.

Webhook URL

https://run.rapidfolio.com/triggers/:triggerId/linear

Replace :triggerId with the trigger ID shown in the Rapidfolio dashboard.

Signature Verification

Rapidfolio verifies the Linear-Signature header on every inbound request using your Linear webhook signing secret. Requests with an invalid or missing signature are rejected with a 400 response.

Rapidfolio handles this automatically when you connect your Linear workspace — no additional configuration is required.

Configuration

Field	Description
Connection	The Linear workspace connection
Resource types	Filter by resource type — e.g. Issue, Comment (leave empty for all)
Actions	Filter by action — e.g. create, update (leave empty for all)
Teams	Filter to specific team IDs (optional)
Labels	Only trigger for issues with these label names (optional)

Supported Event Types

Issues

Resource type	Action	Description
Issue	create	A new issue was created
Issue	update	An issue was updated (title, description, status, assignee, priority, etc.)
Issue	remove	An issue was deleted

Comments

Resource type	Action	Description
Comment	create	A comment was posted on an issue
Comment	update	A comment was edited
Comment	remove	A comment was deleted

Projects

Resource type	Action	Description
Project	create	A new project was created
Project	update	A project was updated (name, status, lead, target date, etc.)
Project	remove	A project was deleted

Cycles

Resource type	Action	Description
Cycle	create	A new cycle was created
Cycle	update	A cycle was updated

Payload

The trigger payload is the Linear webhook event body. Access it via the trigger input in your procedure.

Issue created

{
  "action": "create",
  "type": "Issue",
  "createdAt": "2024-03-15T10:30:00.000Z",
  "organizationId": "org_abc123",
  "data": {
    "id": "abc123def456",
    "title": "Fix login bug",
    "description": "Users are unable to log in with SSO.",
    "priority": 2,
    "state": {
      "id": "state_abc",
      "name": "Todo",
      "type": "unstarted"
    },
    "assignee": {
      "id": "user_abc",
      "name": "Alice Johnson",
      "email": "alice@example.com"
    },
    "team": {
      "id": "team_abc",
      "name": "Engineering"
    },
    "labels": []
  }
}

Issue updated

{
  "action": "update",
  "type": "Issue",
  "createdAt": "2024-03-15T11:00:00.000Z",
  "organizationId": "org_abc123",
  "updatedFrom": {
    "stateId": "state_todo",
    "assigneeId": null
  },
  "data": {
    "id": "abc123def456",
    "title": "Fix login bug",
    "state": {
      "id": "state_inprogress",
      "name": "In Progress",
      "type": "started"
    },
    "assignee": {
      "id": "user_abc",
      "name": "Alice Johnson"
    }
  }
}

The updatedFrom field contains the previous values of changed fields — useful for detecting specific transitions (e.g. when an issue moves into a specific state).

Example Use Cases

• Trigger a KYC check procedure when a Linear issue with the label "customer-onboarding" is created.
• Notify a Slack channel when a high-priority (priority: 1) issue is created in the Engineering team.
• Start a compliance review workflow when an issue transitions to "In Review" status.
• Create a ticket in your internal system when a Comment.create event arrives on issues in a specific team.