---
title: "Product feedback into HubSpot notes"
description: "Every product feedback submission updates the HubSpot contact and adds a note, so customer-facing teams can see what users are asking for."
url: "https://www.formformform.com/automations/hubspot-product-feedback-notes"
type: static
generatedAt: "2026-08-23T18:56:58.727Z"
---
![HubSpot logo](/logos/integrations/hubspot.svg)

# Log product feedback on the customer's record

Product feedback updates the HubSpot contact and logs a note, putting requests where account teams already look.

When this happens

New Submission on your "Product feedback" form

Do this

Update the contact and add a note in HubSpot summarising the feedback

One-directional. A submission triggers the action — nothing is written back into your form.

Feedback usually ends up somewhere the product team can read and nobody else can. Writing it onto the HubSpot contact changes who sees it: the person handling the renewal, the rep answering a pricing question, and anyone else who opens that record before a call.

Product teams running an ongoing feedback form get a second benefit. The note sits beside the deal history, so a request from a large account reads differently from the same request arriving out of nowhere. The form stays short.

## Setting it up

1.  1
    
    Publish your Product feedback form and keep Email Address required, since the note has to attach to a known contact.
    
2.  2
    
    In HubSpot, add the custom contact properties this flow writes to — the product name and the recommendation answer — before you build the Zap.
    
3.  3
    
    Set the Zap trigger to New Submission and select the feedback form.
    
4.  4
    
    Add a HubSpot Create or Update Contact action keyed on Email Address, writing the rating answers into their custom properties.
    
5.  5
    
    Add a second HubSpot action to create a note, attached to the contact ID returned by the previous step.
    
6.  6
    
    Compose the note so the free-text answer about missing features leads, with the product name and rating underneath — that is the part an account manager will actually read.
    
7.  7
    
    Skip the fields that only matter to the product team. Design and appearance ratings belong in your responses export, not on a CRM timeline.
    
8.  8
    
    Submit a test response as an existing customer, check the note and the updated properties on that contact, then turn the Zap on.
    

## What maps where

Using the [Product Feedback Survey](https://www.formformform.com/templates/product-feedback-survey) as the starting point. These are its real fields — swap in your own and the mapping works the same way.

Form field

HubSpot

Email Address

The lookup key used to find or create the HubSpot contact

Product Name or Model

A custom contact property, and the first line of the note

What features are missing or need improvement?

Main body of the note

Would you recommend this product to a friend or colleague?

A custom contact property you can filter accounts on

Ease of use

A custom contact property, kept as a rating for reporting

## Variations worth knowing

Send the same feedback to the product backlog

Add a third action that creates an issue in Linear, Jira or wherever the roadmap lives, carrying the same free-text answer. HubSpot keeps the customer context, the tracker keeps the work item, and one submission feeds both.

Only log feedback from paying accounts

Put a Zapier filter before the HubSpot actions that checks the email domain, or look the contact up first and continue only when their lifecycle stage is Customer. Everything else still lands in formformform's responses for the product team to read.

## If something isn't arriving

Rating answers land in HubSpot as text and cannot be reported on.

A HubSpot number property rejects a label like "Very easy". Either create the property as a dropdown whose options match the form's scale exactly, or convert the answer to a number with a Zapier formatter step before the HubSpot action runs.

Notes pile up on the same contact and bury the useful ones.

Log a note only when the free-text answer is not empty — a Zapier filter on that field handles it. Ratings can still update contact properties on every submission, which keeps the timeline readable while the reporting stays complete.

## Frequently asked questions

Should feedback go into a note or a contact property?

Both, for different jobs. A note carries the sentence someone actually wrote and is meant to be read before a call. A property holds one value you can filter and report on. Sending free text to a property makes lists awkward to build.

Can I collect feedback anonymously and still use this?

Not for this flow. Without an email address there is no contact for the note to attach to. An anonymous form still works well in formformform and you read the responses there, but it cannot write to a CRM record.

Does the note change if the customer submits feedback again?

No. Each submission creates its own note, so the timeline shows how views shifted over time. Contact properties are overwritten with the latest answer, which is why the ratings show the current position and the notes show the history.

## Related automations

-   [Add webinar registrants to a HubSpot workflow](https://www.formformform.com/automations/hubspot-webinar-signup-workflow)
    
    Each webinar signup adds the contact to a HubSpot workflow and records which event they registered for.
    
-   [Create or update a contact from every demo request](https://www.formformform.com/automations/hubspot-demo-request-leads)
    
    Each demo request creates or updates a HubSpot contact with the requester's name, work email, company and phone.
    
-   [Log a support request as a note on the contact](https://www.formformform.com/automations/hubspot-support-request-notes)
    
    Each support submission finds the customer in HubSpot and adds a timestamped note with the issue details.
    
-   [Open a deal when a quote request arrives](https://www.formformform.com/automations/hubspot-quote-enquiry-deal)
    
    Every quote request opens a deal in your chosen HubSpot pipeline and stage, associated with the person who asked.
    
-   [Set lifecycle stage on every newsletter signup](https://www.formformform.com/automations/hubspot-newsletter-lifecycle-stage)
    
    Subscribers become HubSpot contacts with a lifecycle stage and topic preferences already set for the nurture campaign.
    
-   [Add newsletter signups to Zoho CRM as tagged contacts](https://www.formformform.com/automations/zoho-crm-newsletter-opt-ins-tagged)
    
    Every newsletter opt-in becomes a Zoho CRM contact carrying a tag you can build a campaign list from.
    

-   [All HubSpot integration details →](https://www.formformform.com/integrations/hubspot)
-   [Start from the Product Feedback Survey →](https://www.formformform.com/templates/product-feedback-survey)
-   [Browse every automation →](https://www.formformform.com/automations)

## Build the form first

The automation needs somewhere to fire from. Publish a form, connect it once, and every submission from then on runs this flow.

[Start free](https://app.formformform.com/register?utm_source=landing&utm_medium=bottom&utm_campaign=automations&utm_content=hubspot-product-feedback-notes)