Linear Project Status and Date Sync to Productboard Feature - n8n Workflow

Product Managers needing real-time feature roadmapping based on engineering progress in Linear.
Engineering Teams looking to automatically update product visibility without manual double-entry.
Automation Specialists seeking advanced examples of using the n8n node for data transformation (status mapping and complex date handling).
Teams requiring robust integration between project tracking (Linear) and product management (Productboard).

Maintaining consistency between development progress tracked in Linear and feature roadmaps in Productboard is a common challenge for scaling product teams. This n8n workflow solves this by providing a highly efficient, automated pipeline. Whenever a Linear Project is updated (status, target date), the n8n trigger fires. The subsequent steps find the corresponding feature in Productboard (using a custom field containing the Linear URL), translate the status using custom logic, calculate the correct Productboard timeframe, and apply the update. If the data has genuinely changed, the update is executed, and a confirmation is sent via Slack. This n8n template ensures your Productboard roadmap always reflects the latest reality from engineering, saving significant manual overhead.

The synchronization process starts with the Linear n8n trigger, which listens for project changes (Your Linear Project 1 / 2).

1. Data Extraction: The initial Linear payload is processed by the 'linear project id' Set n8n node, extracting key fields like project URL, status, and target dates, setting the stage for the rest of the n8n workflow.


2. Productboard Lookup: The 'get productboard feature id' HTTP Request n8n node queries Productboard using a specific custom field value (which must contain the Linear project URL) to retrieve the unique feature_id.


3. ID and URL Mapping: The data is split and the 'Edit Fields' Set n8n node isolates the feature ID and the Linear URL found within the Productboard custom field data.


4. Status Transformation: The 'mapping' Code n8n node executes custom JavaScript logic to translate Linear statuses (e.g., 'In Progress', 'Completed') into the appropriate Productboard status equivalents (e.g., 'In progress', 'Released'). This is a critical customisation within this n8n workflow template.


5. Comparison and Conditional Update: The n8n workflow retrieves the current Productboard feature details and uses the 'If' n8n node to check if the new status or calculated timeframe differs from the existing Productboard data.


6. API Update: If a difference is detected, the 'update productboard status & timeframe' HTTP Request n8n node performs a PATCH request, using advanced expressions to dynamically set the status and calculate monthly start/end dates for the Productboard timeframe, handling scenarios where the Linear targetDate might be null.


7. Notification: Finally, the 'Slack' n8n node sends a formatted notification confirming the successful synchronization to the specified channel. This completes the end-to-end n8n workflow.

To deploy this powerful n8n workflow, follow these steps:

1. Import: Copy the provided JSON and import it into your n8n instance using the 'New' -> 'Import from JSON' option.


2. Credentials: Set up credentials for the services used:

1. Linear Trigger Setup: Configure the 'Your Linear Project 1' and 'Your Linear Project 2' Linear n8n trigger nodes with the correct teamId and activate the webhooks. Remember to create the webhook endpoints in Linear.


2. Productboard Custom Field: In the 'get productboard feature id' n8n node, replace customfielduuid> with the actual UUID of the custom field in Productboard that stores the Linear project URL/ID.


3. Activation: Once credentials and necessary IDs are configured, activate the entire n8n workflow to enable automatic synchronizations.

Your Linear Project 1 / 2 (Linear Trigger n8n node):
Function: Starts the n8n workflow execution upon a project change event in Linear. This acts as the entry n8n trigger point.
Key Configuration: Configured to watch the project resource for specific Linear teams.
linear project id (Set n8n node):
Function: Extracts and cleanses initial data points, using an expression ($json.url.split()) to derive the project ID from the incoming Linear URL.
get productboard feature id (HTTP Request n8n node):
Function: Queries Productboard's API to find the feature ID matching the Linear project identifier stored in a custom field.
Key Configuration: Uses genericCredentialType for API key authorization and requires specifying customField.id in query parameters.
mapping (Code n8n node):
Function: Contains the core translation logic, using a JavaScript switch statement to map six different Linear statuses to their corresponding Productboard feature statuses.
If (If n8n node):
Function: Prevents unnecessary updates to Productboard by checking if the mapped status or calculated end date is different from the current values fetched from Productboard.
update productboard status & timeframe (HTTP Request n8n node):
Function: Patches the Productboard feature with the new status and timeframe.
Key Configuration: The JSON body contains complex ternary expressions to calculate end-of-month dates and set granularity based on the existence of a Linear targetDate.
Slack (Slack n8n node):
Function: Sends a confirmation message containing project details, status, and a direct link to the updated Productboard feature.
Key Configuration: Uses a structured block message for clear readability, leveraging data from the successful update action of the previous n8n node.