Hey everyone,
I have a question regarding DataHub/APIs and Workflows. I have a custom app where I’m hoping to leverage DataHub’s webhooks/workflows to get me what I need but I’m struggling.
I have a custom app where individuals can be a memeber of. A person can be a member of an infinite number of workspaces in the app as well as an app’s workspace can have an infininte number of members. (Just trying to illustrate the many-to-many relationship).
I am trying to associate the Contact to the Workspace. I am successful when the workspace and contact are created at the same time (so when a new contact creates a new workspace) however, I’m stuck when I have a preexisting workspace and we invite a new user to it.
I have a webhook that pushes a workspace membership change (boolean T/F) value when a preexisting workspace invites a new user. However in HubSpot it keeps displaying an error - but I don’t undestand because the value I’m pushing over is “true”. So how could that be creating an error.
Hey there @TLarson5
Thank you for your post!
I found two resources that are helpful for your case:
Troubleshoot common workflow errors
Webhook error in Workflows: “The webhook server didn’t execute the request”
I also want to tag a few Community Experts who can help you find a solution. Hey @HubDoPete @zach_threadint @GRajput How’s your week going? Do you have any thoughts or ideas for this issue?
Thanks
Victor
Hi @TLarson5 ,
Ah, this one trips up a lot of people working with custom events and webhooks. The error “Incorrect property value type” almost always means theres a mismatch between what your webhook is sending and how the property is defined in HubSpot, not necessarily that the value itself is wrong.
Looking at your screenshot, the property value in your occurrence doesnt match the type on the event definition. Even though you’re sending “true”, the question is how you’re sending it. If your webhook payload has the value as a string like “true” instead of an actual boolean true (no quotes), HubSpot will reject it when the property is defined as a boolean type. Same thing happens the other way around, if the property is defined as an enumeration or single checkbox in HubSpot but you send a raw boolean.
First thing I’d check is your custom event definition in HubSpot under Data Management > Custom Events. Look at how that membership property is configured and what type it expects. Then compare that against the actual JSON payload your app is sending. You can usually see the raw payload in your app’s logs or by testing with something like Postman. The HubSpot docs on custom event properties cover the expected formats pretty well (https://developers.hubspot.com/docs/api-reference/event-analytics/guide).
Also worth noting, if this worked fine when contact and workspace were created together but fails on the invite flow, your app might be constructing the payload differently in those two scenarios. Could be a code path thing where one uses proper boolean and the other stringifies it.
For what its worth, these kind of data type inconsistencies across systems are exactly why some teams prefer syncing everything to a central database with tools like Stacksync rather than managing webhooks directly, but for your specific case fixing the payload format should solve it. Let me know if checking the property definition helps narrow it down! Disclosure: This answer comes from my own experience and was lightly rephrased with AI to improve readability.
Hope this helps.
@RubenBurdin - Follow up question here. Because I have that many-to-many relationship (where workspaces can have many members and members can be part of many workspaces) I was planning on creating an association between the 2 via a workspace ID.
I have attempted a “workspace ID” property (multi-line text field type) on the contact and seeing if that could match the custom object workspace ID. However, when we’ve tested this, HS pushes back an error - that it cannot find the workspace ID, especially when we have a test contact with multiple workspace IDs in the “workspace ID” contact property.
It looks like HS cannont parse out the multiple IDs in that multi-line text field. Any ideas on a work around here? Thanks!