Unexpected Workflow Enrollments Triggered by Webhook Events Without Object Match

Hi @LFDias and thanks @BérangèreL for the tag,

Here is the relevant help doc that specifically addresses Enrolling an object in a workflow based on a third-party incoming webhook

Your screenshot show what looks to be a list of Deals that were enrolled in a workflow, and you have a column called “HubSpot ID” but I am not sure what that column is. It cannot be the object ID of the deal, as that cannot be blank on deals that exist.

You must nominate which data property in the third-party Webhook is to be used to identify the unique existing deal. Then the workflow can only be triggered if the selected third-party webhook property has a non-empty value in the incoming webhook data.

I suggest:

  • If you are sure that the property you nominated as the object ID is sometimes blank, if possible, stop the third-party from sending webhooks that have no unique ID for the workflow to use.
  • Check the workflow logs for deals that you think should not have enrolled, to see why the object enrolled
  • If you are sure that the mapped third-party property was blank, yet the workflow triggered and enrolled an object, that’s a topic for HubSpot support to take a closer look.

best

Pete