Skip to main content

Sync Productboard features to Linear issues with Telegram notifications

Workflow preview

Workflow preview
100%
Sync Productboard features to Linear issues with Telegram notifications preview
Open on n8n.io

Important notice

This workflow is provided as-is. Please review and test before using in production.

1. Workflow Overview

How it works This workflow automatically syncs new Productboard features into Linear as issues and notifies the team via Telegram. It starts on a schedule, fetches Productboard features through API...

Best for

  • Project Management automation workflows
  • intermediate n8n builders looking for reusable templates

Tools used

n8n-nodes-base.scheduletrigger, n8n-nodes-base.httprequest, n8n-nodes-base.code, n8n-nodes-base.if, n8n-nodes-base.linear, n8n-nodes-base.telegram, n8n-nodes-base.stickynote

Source and attribution

This workflow is cataloged by N8N Workflows and links back to its original n8n.io source page by Avkash Kakdiya.

Original n8n.io source

1.1 Workflow description

Title
Sync Productboard features to Linear issues with Telegram notifications
Workflow name
Sync Productboard features to Linear issues with Telegram notifications

How it works

This workflow automatically syncs new Productboard features into Linear as issues and notifies the team via Telegram. It starts on a schedule, fetches Productboard features through API requests, and transforms the raw data into clean, structured fields. Newly created features are filtered, then inserted into Linear, and a success message is sent to Telegram for confirmation.

Step-by-step

1. Trigger and fetch data

  • Schedule Trigger – Starts the workflow at predefined intervals.
  • HTTP Request to Productboard – Pulls the latest features from the Productboard API.

2. Transform and clean data

  • Code (Transform Features) – Strips HTML, formats dates, and extracts clean fields like name, description, status, owner, and link.

3. Filter for new items

  • If (Filter New Features) – Compares createdAt with today’s date, allowing only new features to proceed.

4. Create issues in Linear

  • Create Linear Issue – Opens a new Linear issue using the feature’s name and description.

5. Notify via Telegram

  • Success Notification (Telegram) – Sends a confirmation message once the sync is successful.

Why use this?

  • Automates the sync of Productboard features into Linear without manual copying.
  • Ensures only new features are captured, preventing duplicates.
  • Keeps your team updated instantly through Telegram notifications.
  • Saves time by standardizing data and formatting before inserting into Linear.
  • Creates a smooth handoff from product planning to engineering execution.

1.2 Logical Blocks

This catalog entry is organized from the workflow JSON. The node-level section below shows the executable blocks available for review before importing the template.

2. Block-by-Block Analysis

Block 1 - 📅 Schedule Trigger

Type / Role
n8n-nodes-base.scheduleTrigger - scheduleTrigger
Config choices
Version 1.2

Block 2 - 🌐 HTTP Request to ProductBoard

Type / Role
n8n-nodes-base.httpRequest - httpRequest
Config choices
Version 4.2

Block 3 - 💻 Code (Transform Features)

Type / Role
n8n-nodes-base.code - code
Config choices
Version 2

Block 4 - ⚖️ If (Filter New Features)

Type / Role
n8n-nodes-base.if - if
Config choices
Version 2.2

Block 5 - 📝 Create Linear Issue

Type / Role
n8n-nodes-base.linear - linear
Config choices
Version 1.1

Block 6 - 📢 Success Notification (Telegram)

Type / Role
n8n-nodes-base.telegram - telegram
Config choices
Version 1

Block 7 - Sticky Note

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 8 - Sticky Note1

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 9 - Sticky Note2

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 10 - Sticky Note3

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

3. Summary Table

Workflow Sync Productboard features to Linear issues with Telegram notifications
Complexity intermediate
Nodes 10
Categories Project Management
Author Avkash Kakdiya
Published 24 Sept 2025

4. Reproducing the Workflow from Scratch

  1. 1. Download the workflow JSON

    Use the JSON export at /data/workflows/8891/8891.json as the source template for this automation.

  2. 2. Import the template into n8n

    Open n8n, import the downloaded JSON, and review each node before activating the workflow.

  3. 3. Configure credentials and variables

    Replace placeholder credentials, API keys, webhook URLs, account IDs, and environment-specific values with your own settings.

  4. 4. Test with sample data

    Run the workflow manually or in a staging workspace, inspect node output, and confirm downstream systems receive the expected data.

  5. 5. Activate and monitor

    Enable the workflow only after testing, then monitor executions, errors, and rate limits during the first production runs.

5. General Notes & Resources

Review imported nodes carefully before activation. This catalog entry is intended to help you inspect the workflow structure, understand required services, and find related templates faster.

Node names, credentials, schedules, webhook paths, and external service limits may need adjustment for your workspace.

Frequently asked questions

What does Sync Productboard features to Linear issues with Telegram notifications do?

How it works This workflow automatically syncs new Productboard features into Linear as issues and notifies the team via Telegram. It starts on a schedule, fetches Productboard features through API...

What do I need before importing this workflow?

Review the workflow JSON, configure any required credentials in n8n, and test the automation in a safe workspace before using it in production.

Can I customize this workflow?

Yes. Use the block-by-block analysis and the downloadable JSON to inspect each node, then adjust credentials, prompts, schedules, filters, or destinations for your Project Management use case.