Apps to Projects Migration webhook issue

Develop, Build & Integrate APIs & Integrations
1

We do contact syncing between Hubspot and our platform when the user integrates their Hubspot account. We create a webhook for propertyChange events on mapped properties.

After migrating the legacy app to a project we started receiving:

This app was created by a project `x` and it’s webhook configuration can’t be edited through the API or UI. To edit this app’s webhook configuration, update the app’s ‘webhook.json’ config file locally, then redeploy the project.

Users map fields between Hubspot Contacts and our contacts, this includes custom fields. To track property changes we create webhooks on all of these fields after the user integrates and saves their field mapping.

If we can no longer create webhooks for properties not named in webhook.json then how do we receive events for custom fields where we will obviously not have the property names of all potential custom fields at the time of project creation?

2

Hi @DThomas09,

Welcome to the Community and sharing the details on this!

To start it could be worth checking the HubSpot Developer Docs on project webhooks, however, I couldn’t locate an existing community post that highlights a similar error.

I’d like to tag in some of our top contributors who may have hands-on experience with this:

Hey @Anton, @Josh, @SteveHTM

Do you have any suggestions for @DThomas09 on this?

Thank you!

Sam, Community Manager

3

Thanks, looking forward to their responses.

4

Here’s the config for the supposed catch-all.

"subscriptions": {
 "crmObjects": [
 {
 "subscriptionType": "object.creation",
 "objectType": "contact",
 "active": true
 },
 {
 "subscriptionType": "object.propertyChange",
 "objectType": "contact",
 "active": true
 }
 ]
 }

It gives me this error:

- The subscription type object.propertyChange requires a propertyName field. Please add this field to your subscription configuration and try again.

Would really appreciate some help here.

5

Any update on this? I see one other that says to use polling for the journal, but you seriously don’t offer webhooks anymore? You realize this cuts off everyone with a platform that serves more than one person, right? We can’t regenerate the project for every new customer that has custom fields and who creates something with polling in 2026?

6

Hey @DThomas09,

Thanks for reaching back out here!

Based on the current project webhook documentation, this behavior is still expected: once webhook subscriptions are created through a project, they become project-managed and must be updated in the local webhook configuration and redeployed.

Also, object.propertyChange isn’t a catch-all subscription. Each property-change subscription requires an explicit propertyName, including custom properties. This means that if users choose arbitrary fields after installation, a project-based app can’t create those webhook subscriptions dynamically today. You would need to predefine the properties in the project configuration or use a different sync approach or app model.

More details are available in the webhook configuration documentation.

Hope this helps!

Sam, Community Manager