If none are listed, please create one [here](https://app.appbot.co/sources/manual).

The date the comment was submitted. Will default to the current date and time if left blank.

The [ISO 3166-1 Alpha-2](https://en.wikipedia.org/wiki/ISO_3166-1_alpha-2#Officially_assigned_code_elements) country code where the comment originated.

If your comment relates to an App Version (e.g. 1.2.0) you can include it here.

If you know the device (e.g. iPad) the user submitted the comment from, you can include it here.

If you know the OS (e.g. iOS 12.1) the user submitted the comment from, you can include it here.

Appbot offers App review monitoring, sentiment, text analysis & reply tools for product, tech & support teams. Also supports Amazon products.

Appbot

Productboard user who will be the owner of your new feature.

The name of your new feature in productboard.

A product which will be the parent of the Feature.

Description of your new feature in productboard.

Status of your new feature in productboard.

The content of your note in productboard.

Productboard user who will be the author and owner of the note.

Who told you the information in your note. This is typically a user or customer giving you feedback. It can be someone from within your company as well.

Email address of the person who told you the information in your note.

User External ID of the person who told you the information in your note. Learn more about external IDs  in [this help article](https://support.productboard.com/hc/en-us/articles/7184018643859).

The status of your new note in productboard. Unprocessed/Processed/Archived. It is typical to mark new notes as Unprocessed.

**Full** domain (eg. `productboard.com`) of a company the note (and possibly a user) should be linked to. This is useful mostly in cases where you send `User External ID` but no `User E-Mail` to make Productboard still try to link the note to a company.

To learn more, read the [Productboard API Documentation](https://developer.productboard.com/)

Select “Yes” to [stop this Zap step](https://help.zapier.com/hc/en-us/articles/20505304170637-Review-Zap-run-statuses#h_01HD20969HPZ01ENM30NQR79X5) if the app returns an error and enable automatic authentication refresh. Select “No” to run the Zap step regardless of errors. Learn more about [API Request action error handling](https://help.zapier.com/hc/en-us/articles/12899473501453#h_01JKRBY68EDXBB1V817DSTRZ0N).

Requests can only be made to domains associated by this application. Read more about [API Request Setup](https://help.zapier.com/hc/en-us/articles/12899607716493).

Any parameters added to a URL will be URL-encoded and appended to the request URL to pass additional data to the API request.

These headers and values will be applied to the request in addition to any headers created as part of authentication. Authentication headers are added automatically.

Zapier will pass this along raw. If you would like to provide complex JSON, try a "Code by Zapier" step to build the structure and pass it along here. For example, `{"foo": "bar"}` is perfectly valid.

Productboard is beautiful, simple, and powerful product management. Product leaders can easily centralize user and market research, capture and organize feature ideas, prioritize against clear strategic objectives and keep everyone on the same page thanks to delightful, interactive roadmaps.

Productboard

Manage your user reviews more efficiently with this efficient workflow. When a new review appears in Appbot, a corresponding note is immediately created in Productboard. This automation streamlines the review management process, ensuring critical feedback is swiftly captured and addressed in your product development.

Appbot + Productboard

Create notes in Productboard from new reviews in Appbot

Supported triggers and actions

New Review

New Feature

Create Feature

API Request (Beta)

Create Comment

New Note

Create Note

About Appbot

Related categories

About Productboard

Related categories