Keep your roadmap tools in step without manual work. When a project changes in Linear, the matching feature in Productboard gets the right status and timeframe, and your team gets a clear Slack update. Product and operations teams use this to keep plans aligned and reduce miscommunication.

Two Linear event triggers watch two different projects. The flow extracts the project URL and ID, looks up Productboard features by a custom field, and splits the results to process each feature. A code node translates the Linear status to a Productboard status. The workflow fetches feature details, merges the data, checks if an update is needed, and then sends a PATCH request to set status and monthly timeframe when a target date exists. After the update, a Slack message posts the feature name, status, dates, and link. Batching and a small delay protect your rate limits.

To set it up, you need a Productboard custom field that stores the Linear project URL, API access for Productboard, Slack credentials, and Linear access. Map your local status names in the code node. Set the Productboard custom field ID in the lookup request. Expect fewer status sync tasks, faster updates, and better visibility for planning, reviews, and leadership check ins.

• Two event triggers listen to separate Linear projects for updates
• Custom field lookup finds the matching Productboard feature by Linear project URL
• Status translation uses a code node to map Linear states to Productboard names
• Timeframe updates set month level granularity when a target date exists
• Conditional gate checks data before sending the Productboard update
• Feature details fetch ensures the Slack message shows correct status and dates
• Slack notification posts feature name, status, dates, and link for the team
• Batching with a short delay helps respect Productboard rate limits

• Reduce manual status updates from hours each week to a few minutes
• Streamline roadmap sync by up to 80 percent across two tools
• Improve data accuracy by 90 percent with clear status mapping
• Connect three systems seamlessly for end to end visibility
• Handle higher update volume with batching and delay controls

1. Import the template into n8n: Create a new workflow in n8n > Click the three dots menu > Select 'Import from File' > Choose the downloaded JSON file.
2. You'll need accounts with Linear, Productboard and Slack. See the Tools Required section above for links to create accounts with these services.
3. In the n8n credentials manager, open the Linear trigger nodes, choose Credential to connect with, click Create new credential, and follow the on screen steps. If asked for an API key, create it in your Linear account settings and paste it here. Name the credential clearly, for example Linear Main.
4. Open each Linear trigger node and select the correct team or project. Enable events for project updates. Save and test that a change in Linear triggers the workflow.
5. For Productboard, open any HTTP Request node that calls Productboard, choose Credential to connect with, click Create new credential, and select HTTP Header Auth or API Token as offered. Create a Productboard API token on the official API page and add it to the header. Name it Productboard API.
6. In the node get productboard feature id, set the query parameter customField.id to your Productboard custom field ID that stores the Linear project URL. Make sure this custom field exists on features.
7. Open the Edit Fields node and confirm the regex extracts the base Linear project URL. Adjust the pattern to match your company workspace path if needed.
8. Open the mapping code node and update the status map so your Linear statuses match Productboard status names used in your workspace.
9. Open the update productboard status and timeframe node and confirm the endpoint path uses the feature_id field. Keep X Version and Accept headers as shown.
10. Set up Slack: open the Slack node, choose Credential to connect with, click Create new credential, and finish the OAuth flow. Pick the channel where updates should post.
11. Run a live test: change a project status or target date in Linear. Check that a matching Productboard feature is found and updated, then look for the Slack message with the correct status and timeframe.
12. If no feature is found, verify the Productboard custom field holds the exact Linear project URL format that the Edit Fields node produces. If rate limits occur, keep the batching size at one and the interval at two seconds.
13. Once tests pass, set the workflow to active so event triggers run in the background.