# Unable to Enable Add-on (NodeJS)

**URL:** <https://community.servicem8.com/t/unable-to-enable-add-on-nodejs/1170>\
**Category:** General\
**Created:** [August 26, 2026, 9:22am UTC](https://community.servicem8.com/t/unable-to-enable-add-on-nodejs/1170 "2026-08-26T09:22:51Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![nicholas\_roland](https://avatars.discourse-cdn.com/v4/letter/n/cdc98d/32.png) [@nicholas\_roland](https://community.servicem8.com/u/nicholas_roland)\
**Post date:** [August 26, 2026, 9:22am UTC](https://community.servicem8.com/t/unable-to-enable-add-on-nodejs/1170/1 "2026-08-26T09:22:51Z")

</div>

Hey All

Have a small issue affecting clients trying to enable a new Simple NodeJS Addon, when thye click the **Private Add-on Install URL** they are fowarded to the addon store page, insted of the traditonal Approved Unverified Addon Screen

I have tried to recreate the addon by uploding the Manafest and the Function to a fresh addon, and it affects the new addon too.

Anybody else experiencing this issue?

---

<div class="post-metadata">

**Author:** ![franco\_paul](https://sea2.discourse-cdn.com/flex002/user_avatar/community.servicem8.com/franco_paul/32/53_2.png) [@franco\_paul](https://community.servicem8.com/u/franco_paul)\
**Post date:** [August 26, 2026, 9:57pm UTC](https://community.servicem8.com/t/unable-to-enable-add-on-nodejs/1170/2 "2026-08-26T21:57:21Z")

</div>

Yup, exact same issue. It seems to depend on the target system it is attempted to be installed on; on some the install URL works fine, on others it presents the addon store page.

---

<div class="post-metadata">

**Author:** ![Cody](https://sea2.discourse-cdn.com/flex002/user_avatar/community.servicem8.com/cody/32/52_2.png) [@Cody](https://community.servicem8.com/u/Cody)\
**Post date:** [August 27, 2026, 2:10am UTC](https://community.servicem8.com/t/unable-to-enable-add-on-nodejs/1170/3 "2026-08-27T02:10:28Z")

</div>

Hi Nick and Franco,

Thanks for flagging this. We found the affected accounts were running an older ServiceM8 version and have now upgraded them.

Please retry the Private Add-on Install URL. It should now open the expected approval screen.

Cheers,  
Cody

---

<div class="post-metadata">

**Author:** ![franco\_paul](https://sea2.discourse-cdn.com/flex002/user_avatar/community.servicem8.com/franco_paul/32/53_2.png) [@franco\_paul](https://community.servicem8.com/u/franco_paul)\
**Post date:** [August 27, 2026, 3:03am UTC](https://community.servicem8.com/t/unable-to-enable-add-on-nodejs/1170/4 "2026-08-27T03:03:10Z")

</div>

Hi there Cody

I’m still seeing the same behaviour for an account based in the AWS region us-west-1

---

<div class="post-metadata">

**Author:** ![nicholas\_roland](https://avatars.discourse-cdn.com/v4/letter/n/cdc98d/32.png) [@nicholas\_roland](https://community.servicem8.com/u/nicholas_roland)\
**Post date:** [August 27, 2026, 3:46am UTC](https://community.servicem8.com/t/unable-to-enable-add-on-nodejs/1170/5 "2026-08-27T03:46:05Z")

</div>

Thanks for the update, logged out and back in and now it is working on the accounts i was experiencing issues with.

---

<div class="post-metadata">

**Author:** ![franco\_paul](https://sea2.discourse-cdn.com/flex002/user_avatar/community.servicem8.com/franco_paul/32/53_2.png) [@franco\_paul](https://community.servicem8.com/u/franco_paul)\
**Post date:** [August 28, 2026, 1:14pm UTC](https://community.servicem8.com/t/unable-to-enable-add-on-nodejs/1170/6 "2026-08-28T13:14:52Z")

</div>

Likewise; it’s back to normal now

---

<div class="post-metadata">

**Author:** ![Cody](https://sea2.discourse-cdn.com/flex002/user_avatar/community.servicem8.com/cody/32/52_2.png) [@Cody](https://community.servicem8.com/u/Cody)\
**Post date:** [August 29, 2026, 9:25am UTC](https://community.servicem8.com/t/unable-to-enable-add-on-nodejs/1170/7 "2026-08-29T09:25:22Z")

</div>

Hi Nicholas,

For a Simple Function Add-on (NodeJS), the documented development/testing path is to set the add-on type, upload the manifest, save it, then connect it from Settings \> ServiceM8 Addons in the Custom Addons section. The developer docs also say the Private Add-on Install URL is used to share an add-on pre-approval during testing.

If the Private Add-on Install URL is redirecting client/test accounts to the Add-on Store page instead of allowing the install/connect flow, that’ll need an add-on-specific check rather than troubleshooting the private URL publicly. Product help can be raised through the Help menu in the Online Dashboard.

Send the add-on name or developer add-on UUID, plus a screenshot of the redirect, to ServiceM8 Support via the Help menu so we can review it privately.

Thanks,  
Cody