Hubspot FDW requires API Keys which are deprecated

[kylewill]

Bug report

• I confirm this is a bug with Supabase, not with my own application.
• I confirm I have searched the Docs, GitHub Discussions, and Discord.

Describe the bug

The Wrapper for Hubspot requires (and directs to) setting up a Hubspot API Key.

To Reproduce

Steps to reproduce the behavior, please provide code snippets or a repository:

1. Go to 'Wrappers' under 'Database'
2. Click on 'Hubspot'
3. Attempt to set up and click to get API key (Screenshot)
4. See 404

Expected behavior

the help tooltip should lead to a better spot

app Tokens work, but should have options for oauth and the private app tokens.

[burmecia]

Thanks for reporting this issue! PR is raised to fix this issue: supabase/supabase#35791

[ogulcantumdogan]

Still not fixed. Would love to easily integrate hubspot.

[burmecia]

@ogulcantumdogan can you give more details? I can see the link is already fixed on Supabase platform.

[JohnCari]

This issue has been addressed by two PRs:

1. Broken link fix: fix: broken link for HubSpot API key helper supabase#35791 (merged) - Fixed the 404 link in the Supabase dashboard

2. Documentation clarity: feat(hubspot): add api_key_name support for Vault secret lookup by name #545 (pending) - Adds a note to the docs clarifying that:

   • HubSpot deprecated their legacy API Keys in November 2022
   • The api_key option accepts Private App Access Tokens (HubSpot's recommended auth method)
   • Links to HubSpot Private Apps documentation

The HubSpot FDW has always worked with Private App tokens - they function identically to the old API keys (Bearer token auth). The confusion was in the terminology and the broken link.

Once #545 is merged, this issue should be fully resolved.