Test Addon in Pumble

Developer portal
,
1

Hi Pumble team,

I’ve developed a meeting scheduler add-on with slash commands, CalDAV integration, and ICS email invites. Everything is ready:

Add-on manifest with slash commands configured
Incoming webhooks working
All backend functionality tested

Problem: I can’t find a way to test the add-on in my workspace without marketplace submission. The marketplace requires images and privacy policy, but I just want to test the slash commands locally first.

Questions:

  1. Can I install a custom add-on in development/test mode?

  2. How do I obtain a Bot Token or API Key for testing?

  3. Does /api-keys generate work? (I tried but got no response)

  4. What’s the recommended workflow for testing add-ons during development?

I’m the workspace administrator with the manifest ready at: https://[my-ngrok-url]/pumble-manifest.json

Any guidance would be greatly appreciated!

Thank you!
Luca

2

Hi Luca,

Could you send me your add-on ID and ID of the workspace where you want to test it? We can whitelist the add-on and after the whitespace is whitelisted, you can go to Workspace settings → Configure apps and they will see your addon there.

Another option is to Publish a Private add-on in the Marketplace developer portal, enter your workspace ID and you’ll get an email where you can install it in the same way your users will when you create a Public one.

I hope this would do.

Kind regards,
Uroš

3

Hi Uroš,

Thank you for your help!

Here are the details for whitelisting:

Add-on ID: #removed

Workspace ID: #removed

I’d prefer the whitelisting approach for testing. Could you please whitelist the add-on for my workspace?

Issues we’re experiencing with the manifest:

We’ve been trying to validate our manifest.json file but we’re encountering some errors:

  1. Initially we got “non-existent api scope” errors - we fixed this by using the correct scopes from the pumble-node-sdk documentation (messages:read, messages:write, etc.)

  2. We’re still getting “Manifest is not in the correct form” errors even after:

    • Using eventSubscriptions instead of events

    • Following the exact structure from the example schema

    • Ensuring all required fields are present

    • Creating placeholder HTML pages for all endpoints to avoid 404 errors

Could you help us understand:

  • Is there a manifest validation tool we can use?

  • Are there specific requirements for GitHub Pages hosted manifests?

  • Could you check if our manifest structure is correct?

Thank you for your assistance!

Best regards,
Luca

4

Thank you Luca,

I forwarded the information to our team and removed some information from your post so that it’s not visible to everyone. I’ll let you know when I get more information.

Kind regards,
Uroš

5

Hi Luca,

We have whitelisted the add-on on your workspaces. Could you please check if you can install it there now, through the ‘Apps’ page?

Regarding the manifest validation issues, the manifest you provided is missing dynamicMenus field, so if your addon is not using dynamic menus, you can just add “dynamicMenus”: [] to the manifest.
We recommend using the latest pumble-sdk version, which is currently v1.0.0. We also recommend using pumble-cli tool during the development mode, which makes add-on creation and manifest updates easier.

Once your add-on is up and running, you can view the generated manifest on ${addon_host_url}/manifest.

Kind regards,
Milica