Win-loss survey to HubSpot deal notes | SurveyMonkey automation

PromptCreate

When someone completes my win-loss survey in SurveyMonkey, I want that feedback attached to the right deal in HubSpot instead of sitting in a results dashboard nobody opens. Trigger this workflow from a SurveyMonkey webhook for a completed survey response.

First, call SurveyMonkey Get Survey Details for the survey the response belongs to. This step is not optional: SurveyMonkey returns responses as answer and choice IDs only, with no wording attached, so use the survey details to build a map from question IDs to question text and from choice IDs to answer text. Without it the note will be full of opaque IDs.

Then call SurveyMonkey Get Survey Response Details for the response that triggered the workflow, and resolve every answer through the map from the previous step so you are working with real question and answer text. Keep any open-ended text answers exactly as the respondent typed them, including their wording and punctuation.

Take the respondent's email address from the response and look the person up with HubSpot Get Contact, passing the email address and using email as the idProperty. If no contact matches that email, stop: do not create a note and do not post to Slack.

With the contact found, use HubSpot Search Deals to find the deal they most recently closed. Filter to deals associated with that contact whose stage is closed won or closed lost, sort by close date descending, and take the first result. If the contact has no closed deal, stop.

Write the feedback onto that deal with HubSpot Create Note, associated with the deal you just found. The note should summarize why we won or lost, name any competitor the respondent mentioned, and call out any pricing objection. Keep it under roughly 150 words, skip any theme the response did not actually raise rather than padding it out, and always end the note with the respondent's verbatim comment quoted exactly as they wrote it.

Finally, send a short heads-up to our sales channel with Slack Bot Send a Message, but only when the deal was lost or a competitor was mentioned. If the deal was won and no competitor came up, write the note and stay silent, so the channel stays signal heavy. When you do post, name the company, say whether the deal was won or lost, name the competitor if there was one, give the one line reason, and link to the deal in HubSpot.

What does this prompt do?

Picks up every completed win-loss survey response as it arrives, and reads the real question and answer wording instead of the raw answer codes the survey sends back
Matches the respondent to their contact record in HubSpot and finds the deal they most recently closed
Files a short note on that deal covering why you won or lost, any competitor they named, and any pricing objection, ending with their comment word for word
Only pings your sales channel when the deal was lost or a competitor came up, so the channel stays worth reading

What do I need to use this?

A paid SurveyMonkey plan, since reading individual answers is not available on the free plan
A win-loss survey that asks respondents for their email address
A HubSpot account containing the contacts and deals your respondents belong to
A Slack workspace and a channel where sales alerts should land

How can I customize it?

Change when the sales channel gets pinged, for example on every response instead of only losses and competitor mentions
Adjust the note length and which themes it pulls out, such as timing, missing features, or the buying process alongside pricing
Point it at a different survey, or send the alerts to a different channel

FAQs

Does this work on a free SurveyMonkey plan?

No. Reading the actual answers someone gave requires a paid SurveyMonkey plan. On the free plan you can see that responses exist, but not their content, which is the whole point of this workflow.

What happens if the person who answered is not in HubSpot?

Nothing is written and no alert is sent. The workflow looks the respondent up by email address, and if there is no matching contact it stops quietly rather than creating a stray note or guessing at the wrong record.

What if the contact has no closed deal yet?

The workflow stops. It deliberately only attaches feedback to a deal that has actually been won or lost, so notes never land on live opportunities where they could confuse the rep working them.

Will this flood our sales channel?

No. The channel only hears about a response when the deal was lost or the respondent named a competitor. Straightforward wins are still written to the deal record, they just do not generate a message.

Why does the feedback go on the deal rather than the contact?

Because win-loss feedback is about a specific buying decision. Putting it on the deal means the next person reviewing that opportunity, or anyone reporting on why deals are lost, finds the reason attached to the thing it explains.

Related templates

Build a credential rotation checklist when someone leaves

When someone leaves, we check which shared passwords they used in their final months and post a ranked rotation list to your security channel.

+1

Agentic Task

Weekly Amazon S3 bucket security audit posted to Slack

Every Monday, check every S3 bucket for public exposure, missing encryption and weak backup settings, then get the risks ranked in Slack.

Agentic Task

Log Agorapulse social conversations to HubSpot contacts

Twice every weekday, the conversations from your social inbox land on the right HubSpot contact timelines, with a Slack recap for sales.

Agentic Task

Turn procurement portal tenders into CRM deals each morning

Every weekday at 7am, sign in to the tender portals you track, filter new notices against your bid criteria, and open a deal for the ones worth chasing.