Troubleshoot scenario HubSpot

:bullseye: What is your goal?

if Hubspot ID doesn’t exist, then look for the real ID in the app and update Hubspot’s deal

:thinking: What is the problem & what have you tried?

I am building a bridge between Coperniq and HubSpot. The workflow is triggered by a Coperniq Webhook, but the Webhook often sends a “system-generated” or “Ghost ID” (e.g., 794201) that does not contain the project metadata I need.

To fix this, I am attempting to use an HTTP “Make a Request” module to Search for the “Real” project ID using a unique hubspot_deal_id.

Even though my search logic is correct, the Make module is failing to return the expected data (or returning an error), while the exact same request works perfectly in Postman.

:clipboard: Error messages or input/output bundles

in HubSpot module
Error
Validation failed for 1 parameter(s).

  • Missing value of required parameter ‘dealId’.

:camera_with_flash: Screenshots (scenario flow, module settings, errors)

Hey @Jhon_Sebastian !

The HubSpot error is happening because the update module is not receiving a deal ID at all.

So the real problem is not the HubSpot step itself. It’s the step before it. Your HTTP search is either not returning the record you expect, or the value is not being mapped correctly into the HubSpot dealId field.

Since the same request works in Postman, I would check three things in Make:

First, open the output of the HTTP search module and confirm that the real HubSpot deal ID is actually present in the response body for that run.

Second, make sure you are mapping the exact field that contains the deal ID into the HubSpot Update a Deal module. If the response is nested inside an array or object, Make may not be pulling the value you think it is.

Third, add a filter before the HubSpot module so it only runs when the searched deal ID exists. Right now the HubSpot step is still running even when the ID is empty, which is why you get the validation error.

So the flow should be:
webhook receives ghost ID
HTTP search looks up the real record using hubspot_deal_id
if a real deal ID is found, map that into HubSpot Update Deal
if no deal ID is found, stop the route or handle it separately

In short, the issue looks like an empty mapping after the search step, not a problem with the HubSpot module itself.

Dr. Tanvi Sachar
Monday Certified Partner, Tuesday Wizard