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

Select an assignee from your Cycle workspace. If you leave this field empty, a default assignee will be set.

Select a valid email address from the trigger or type one by hand. If you leave this field empty, a default customer will be set.

Select a valid http url from the trigger or type one by hand

Cycle connects customer feedback to product delivery workflows so you can close the feedback loop and wow your customers at each release.

Cycle

Do you have store feedback in Productboard? Use this Zapier template to add the feedback in new Productboard notes to your Cycle workspace. That way, you can link them to your product roadmap and close feedback loops.

Cycle + Productboard

Create feedback in Cycle from new Productboard notes

Supported triggers and actions

New Feature

Create Feature

API Request (Beta)

Create Feedback

New Note

Create Note

List Assignees

About Cycle

Related categories

About Productboard

Related categories

Related Zap Templates

Related Zap Templates