Integrate with Zapier

Jake Sawyer

Updated July 07, 2026 15:19

Zapier connects Productboard to over 1,000 other apps without any coding. You choose a trigger in one app and Zapier performs an action in another app automatically, no engineering time required.

For example, you could use Zapier to integrate Productboard with tools like Slack, HubSpot CRM, Drift, GitHub, Asana, SatisMeter, Front, Evernote, or Google Sheets.

Note: Zapier builds and maintains all of its app integrations, including the one for Productboard. Productboard supports only the underlying APIs that Zapier accesses for the triggers and actions described below. For anything related to another app's interface or account setup, check out that app's support resources.

This article covers the triggers and actions Productboard makes available in Zapier, how to set up a Zap, and a couple of the most common use cases.

Triggers for sending data from Productboard

A trigger fires when something happens in Productboard, and Zapier passes that event on to another app. Productboard offers four triggers:

New note: Fires when someone creates a new feedback item in Productboard.
Updated note: Triggers when a feedback item is updated.
New feature: Fires when someone creates a new feature in Productboard.
Updated feature: Triggers when a feature is updated.

For example, use the New note trigger to send a Slack message to your team whenever a new note lands in Productboard.

Note: You cannot further qualify these triggers, for example, to only send notes with a specific tag or features of a given status. A Zap built on these triggers mirrors every note or feature created in Productboard.

Actions for creating notes and features in Productboard

An action creates something in Productboard in response to a trigger in another app. Productboard offers two entity creation actions (create note and create feature), as well as a few other actions.

Create note fields

A create note action can map the following fields:

Name. The title of the note.
Content. The body text of the note.
Owner. The Productboard member responsible for the note. Required.
Tags. Labels for finding the note later.
Processed/unprocessed status. Whether the note starts as processed or unprocessed on the Insights board. Required.

Create feature fields

A create feature action can map the following fields:

Name. The title of the feature. Required.
Description. Text describing the feature.
Owner. The Productboard member responsible for the feature. Required.
Status. The feature's current development status, such as New idea, Candidate, Planned, In progress, Released, or Archived. Required.
Tags. Labels for finding the feature later.

You can customize feature status values. If an incoming status doesn't match a status in your workspace, Productboard assigns the feature to the first available status instead.

Other actions

Other supported actions include:

Find note.
List note relationships.
Update note.
Get feature by ID.

Importing data from a spreadsheet

One of the most common ways teams use Zapier with Productboard is to import new spreadsheet rows automatically, like survey results or feature requests logged in a Google Sheet.

Tip: If you only need to import data once, use Productboard's built-in feedback importer or feature importer.

Whichever you're importing, format your spreadsheet with clear column headers so Zapier can map them to Productboard fields. Expect up to a 15-minute delay between updating your spreadsheet and seeing the new data appear in Productboard.

Importing features from a spreadsheet

Required headers:

Owner. The person on your team who owns the feature.
Name. The title of the feature.
Status. The feature's current development status.

Optional (but recommended) headers:

Description. Text describing the feature.
Tags. Labels for finding the feature later.

Importing notes and feedback from a spreadsheet

Required headers:

Feedback owner. The person on your team who logged the feedback, or the product manager responsible for that area of the product.
Feedback status. The default status of imported feedback. We recommend loading feedback in as unprocessed so you can review and categorize it on the Insights board.

Optional (but recommended) headers:

Title. The name of the note.
Content. The body text of the note.
Said by (User name). The name of the customer or stakeholder the feedback is from.
Said by (User email). The email address of the customer or stakeholder the feedback is from.
Feedback tags. Tags for retrieving certain feedback later.

Tip: It's possible to configure Zapier to route feedback to specific owners based on content, but it's easier to do so with Productboard's built-in insights automations.

Setting up a Zap

For the most up-to-date instructions for creating and managing Zaps, see Zapier's documentation.

Limitations

Zaps sync data in one direction only. Changes made in Productboard after an item is created don't sync back to the source app, and vice versa. You may be able to create a second Zap to handle the return trip.
If a tool has a native, two-way Productboard integration, such as GitHub issues, use that instead where you need items to stay in sync.
If you later push an item into a tool using a native integration after already importing it via Zapier, Productboard creates a duplicate rather than merging it with the original.

Troubleshooting

A 422 error means the Owner field is empty or contains an invalid member ID. Enter a valid Productboard member ID in the owner field to resolve it.

Best practices

It's often a good idea to add a "Zapier" tag feedback or features that you import via Zapier This makes it easy to filter for them and confirm they're fully filled in once they land in Productboard. Learn more about how tags work in Productboard.