Agent Tools beta — custom workflow-action deploys cleanly but doesn't appear in Developer Tool Testi

Develop, Build & Integrate APIs & Integrations
1

I’m in the Breeze Agent Tools beta. My developer account got the “approved for new app features” banner. I’ve built a custom agent tool following the reference docs, but it never shows up in the Developer Tool Testing Agent → Add tool picker. Looking for what I’m missing.

Environment: new HubSpot Developer Platform, project on platformVersion: 2026.03, static-auth private app, deployed to a developer test account via hs project upload.

What works

  • Project builds and validates clean.
  • App is installed on the test portal.
  • The action appears under Integrated apps in the Workflows action picker and runs successfully end-to-end against my actionUrl.

What doesn’t work

  • The same component does not appear in the Developer Tool Testing Agent’s Add tool picker — empty search results, even unfiltered. Only HubSpot-built sample tools appear.
  • The project’s App Features page labels it as Workflow Action, never as an agent tool, regardless of supportedClients shape.

Configurations I’ve tried (all deploy cleanly, none surface in the picker):

  1. [{client: WORKFLOWS}, {client: AGENTS, toolType: GET_DATA, llmConfig: {actionDescription}}] — full per-docs.
  2. [{client: AGENTS, toolType: GET_DATA, llmConfig: {actionDescription}}] — AGENTS only.
  3. [{client: WORKFLOWS}, {client: AGENTS}] — exactly the form hs project add --features=workflow-action-tool scaffolds.

I also confirmed labels.en.appDisplayName, labels.en.actionName, populated outputFields, isPublished: true, and proper inputFields[].typeDefinition per the reference table.

Questions

  1. Is there a portal-level toggle or backend allowlist that controls whether developer-deployed tools appear in the testing agent’s picker, beyond the developer-account beta opt-in?
  2. Does the “approved for new app features” banner mean the feature is active, or is there a separate enablement step?
  3. Is there a component-level deploy log I can read to see why agent-tool registration is silently skipped while workflow-action registration succeeds?

Happy to share full hsmeta config if useful. Thanks.

2

Heya @CGlassmire9 Thanks for posting! :slightly_smiling_face: From what I could verify, it seems like you’re probably not missing a schema detail in supportedClients; your config variants line up with the public agent-tool docs, and seeing the feature labeled as a Workflow Action looks to be normal because agent tools are still implemented as workflow actions under the hood.

I’d love to hear from our Community contributors on this! @WesQ @Bortami @HubSpot_Corey - Are you able to help @CGlassmire9 with the questions above? :slightly_smiling_face: Thank you!

Jess

Community Manager

3

I have actually fixed it! I don’t know why, but deploying it the exact same just in a different portal caused it to work immediately.

4

Hi @CGlassmire9 Thanks for the update! I’m glad that worked! If you come across the issue again, let us know :slightly_smiling_face:

Jess

Community Manager