I’m setting up an addon (App ID: 926077) as an “External Integration” to use the API with Make.com. I’ve set the Callback URL to https://www.make.com/oauth/callback and the Addon Activation URL to https://frasercoastplumbing.com/activation (and tried https://example.com/activation), but I keep getting the error “Please supply an Addon Activation URL” when saving. My addon is in Draft status. Is the Addon Activation URL required for External Integration? If so, what format should it be? Can you help me resolve this?
Hi Takunda, I notice that servicm8 never actually answer any decent question like this one. I don’t know the exact answer to your question but think that the activation url should be like https://frasercoastplumbing.com/manifest.json because I got the same until I made sure of two things. 1) put the manifest in the root folder 2) include the file name and extension in the activation url. Also you apparently have to contact support and get them to change your addon from ‘Draft’ to ‘Private’
For an External Integration, the Activation URL is where ServiceM8 sends the user after they click Connect, and it should point to an endpoint in your system that begins the OAuth flow so your app can obtain an OAuth token.
So it’s typically not a manifest.json URL. A manifest file is only a requirement when you’re building an Add-on SDK add-on (where the add-on is described by a Manifest file).
If you’re building an Add-on SDK add-on and want ServiceM8 to manage the OAuth connection (Serverless Authentication), the Activation URL should be left blank.
One other item to double-check when wiring this up to Make: the redirect_uri you send to ServiceM8 during OAuth must be on the same host as the Return URL configured in your Store Connect settings.
If you’re still seeing “Please supply an Addon Activation URL” when saving even though the field contains a valid HTTPS URL, email support@servicem8.com with App ID 926077 and a screenshot of the Store Connect screen so we can investigate.