Policy clarification: companion Chrome extension on HubSpot workflow pages

Develop, Build & Integrate APIs & Integrations
,
1

Hi everyone,

I’m looking for guidance on whether a companion Chrome extension architecture is compatible with HubSpot’s developer and Marketplace policies.

We’re building a read-only application that connects to HubSpot through OAuth and retrieves workflow information through documented HubSpot APIs. The application does not create, edit, activate, deactivate or delete workflows.

The Chrome extension is currently a private prototype. It has not been distributed to external users or submitted to the Chrome Web Store or HubSpot App Marketplace.

Its proposed purpose is to provide contextual information while an authorised user is viewing a workflow in HubSpot.

The proposed behaviour is:

  • It runs only on relevant app.hubspot.com workflow pages.

  • It reads the current URL to identify the HubSpot account and workflow being viewed.

  • It does not extract workflow definitions or other HubSpot data from the page DOM.

  • It does not intercept network traffic or automate clicks or other user actions.

  • It displays the external application’s information in Chrome’s browser-owned Side Panel.

  • Any workflow refresh is performed by the application’s backend through the documented HubSpot API and the customer’s authorised OAuth connection.

  • HubSpot access and refresh tokens remain on the backend.

  • The extension and Side Panel are clearly branded as an independent product.

We are also considering adding a small, clearly branded floating button at the right edge of the workflow editor. Its only purpose would be to open the Chrome Side Panel after the user clicks it.

The button would not imitate, replace or obscure any HubSpot controls. It would not read workflow content from the DOM or perform any action within HubSpot.

Could anyone from HubSpot’s Developer Platform, Developer Advocacy or Ecosystem team clarify:

  1. Is the URL-only, browser-owned Side Panel architecture described above permitted?

  2. Is adding the small launcher button through a Chrome content script permitted, or should the Side Panel only be opened through Chrome’s toolbar/action button?

  3. Can this extension be offered as a companion feature to an eventual HubSpot Marketplace application once it has been reviewed and approved through the Chrome Web Store?

  4. Are there any additional Marketplace disclosures or review steps required for an application with a companion browser extension?

I’ve reviewed the Developer Terms, Developer Policy, Acceptable Use Policy, Marketplace listing requirements and Chrome Web Store policies, but I haven’t found an explicit answer concerning a small launcher added to an otherwise unsupported HubSpot surface such as the workflow editor.

We want to clarify this before distributing or publicly promoting the extension, rather than assuming that technical feasibility means the architecture is permitted.

I’d really appreciate either an official clarification or guidance on the appropriate private channel where this architecture can be reviewed.

Thank you!

3

Hey @LorenzoS,

Welcome to the community!! :raising_hands: :glowing_star:

While we wait for some other folks to chime in here are a few resources that may be relevant as a starting point:

  1. App listing requirements
  2. App certification requirements
  3. Developer Terms
  4. Workflows v4 API
  5. OAuth documentation
  6. Marketplace listing process

Tagging a few contributors who may be able to help here!

Hey @Alex_Boissonneault, @SteveHTM, @GRajput – do you have any suggestions for @LorenzoS on this?

Thank you!

Sam, Community Manager

4

Hey @LorenzoS, I woul suggest you, not official, just experience from shipping a few of these.

Your URL-only side panel setup is fine. That’s the cleanest version of this pattern i’ve seen. Data via OAuth on the backend, nothing read from the page, nobody’s going to flag that.

The injected launcher button is the only grey bit, and it’s a very common one. Loads of listed apps (dialers, enrichment tools) drop a small branded button on app.hubspot.com. You’re already avoiding the stuff that actually causes problems. So now copying HubSpot UI, covering their controls, scraping the DOM. Keep it clearly yours and dismissible and you’re good.

Yes, it can sit alongside a Marketplace app. HubSpot reviews the app, Chrome reviews the extension. Just mention the extension in your listing and in the notes when you submit, reviewers hate surprises, they’re fine with what you tell them.

And yes, Also go through Developer Support from your dev account and ask for the App Partner team. Get it in writing before you promote it..

5

Thanks, really appreciate the detailed response, this is very helpful.

Good to know that the URL-only side panel approach is a sensible pattern, and your point about the injected launcher being the main grey area is exactly what I was trying to clarify.

I’ve followed your suggestion and reached out directly to HubSpot’s Technology Partner team with the exact implementation details to get their guidance in writing before promoting the extension more widely.

Thanks again for taking the time to help!