we are in the process of migrating apps connect → forge however We would like to know if we create forge manifest with connect webhooks and select in developer console that we are now on forge will those webhooks be disabled?
The ideal solution would be to just use your script to transfer descriptor to manifest and don’t worry about any issues like disabling webhooks (which is mentioned in docs) until Q4 2026.
We would also like to be certain that we will be able use those webhooks and JWT authentication still after saing we support forge manifest.
And third “just to be sure” question, will we be able to modify connectModules section after march and you will only stop reading connect descriptors?
Once an app is Connect on Forge, it will appear in the developer console and can be delivered as a newer version for customers on the marketplace.
Once in this state, apps can continue to use and update Connect modules just as they otherwise would, however there are a few key things to keep in mind:
Connect will be End of Support at the end of 2026. Moving at least some of these modules to Forge earlier will ensure you are familiar the process and the Forge platform.
If you are a paid marketplace app, the utilisation of Connect modules or scopes will result in an increased take rate from April 1st, 2026.