Workflow extension not showing up in Hubspot application

Other Questions HubSpot
1

I’m attempting to create a workflow extension within Hubspot based on the provided guidelines. I made a POST request to establish the extension and received a positive confirmation, yet it doesn’t appear in my workflow configuration in Hubspot.

Here’s the API request I executed:

{
    "integrationAppId": 456789,
    "extensionName": "booking_handler_v2",
    "webhookUrl": "https://mywebhook.example.com/handle-booking",
    "fieldMetadata": [
        {
            "label": "Meeting Title",
            "key": "meeting_title",
            "fieldType": "TEXT",
            "values": [
                {
                    "type": "STATIC_VALUE",
                    "allowsMergeTags": true
                }
            ]
        },
        {
            "label": "Scheduled Date",
            "key": "scheduled_date",
            "fieldType": "DATE",
            "values": [
                {
                    "type": "OBJECT_PROPERTY"
                }
            ]
        },
        {
            "label": "Additional Details",
            "key": "extra_info",
            "fieldType": "TEXTAREA",
            "values": [
                {
                    "type": "STATIC_VALUE",
                    "allowsMergeTags": true
                }
            ]
        }
    ]
}

The API sent back a response indicating ID 283 with all relevant field information, but I’ve noticed that the fieldMetadata is shown multiple times in the response. When I look for my extension in the Hubspot workflow editor, I can’t locate it at all. Has anyone else experienced this problem? What could explain why the extension isn’t visible despite the API response appearing to be successful?

2

The duplicate fieldMetadata is normal - HubSpot returns the processed schema with internal references. Your real issue is probably scope permissions on your private app. I’ve seen this before where extensions register fine through the API but don’t show up in workflows because of missing scopes. Go to your app settings and make sure you’ve got the automation scope enabled, not just basic workflow permissions. Also check that your webhook URL is publicly accessible and actually responds to HubSpot’s validation pings. I’ve seen extensions fail to appear when the webhook endpoint isn’t set up properly for the initial handshake.

3

Had this exact issue last month with a custom workflow extension. The API lies to you - getting a success response doesn’t mean your extension actually shows up in the UI.

My problem was integrationAppId validation. POST request worked fine, but HubSpot was quietly rejecting it during backend validation. Check your dev console logs and make sure your app ID matches your registered app exactly.

Also, workflow extensions can take 15-20 minutes to show up, especially on shared instances. That duplicate fieldMetadata you’re seeing? Dead giveaway the registration failed on HubSpot’s end.

4

Been through this nightmare with HubSpot workflow extensions so many times. API says success but the extension never shows up in the UI.

Skip HubSpot’s custom extension headache entirely - use Latenode instead. Build the same booking workflow automation without their broken registration process.

Create a Latenode scenario that catches your booking triggers, grabs the meeting data (title, date, details), and pushes it straight to HubSpot via their regular API. Takes 30 minutes and actually works.

I moved all our HubSpot extensions to Latenode after getting burned by this too many times. No more guessing if extensions will appear or fighting their validation issues.

Bonus: way more flexibility than HubSpot’s restrictive workflow format. Add logic, transform data, connect other tools - no API hoops to jump through.

5

check if ur webhook endpoint returns the right response codes when hubspot hits it during validation. mine looked fine in the logs but was throwing 404s on specific paths hubspot expected. also double-check you’re creating the extension under the correct portal - sounds obvious but i wasted hours deploying to the wrong account lol

6

yea, hubspot can act slow at times. try loggin out n back in or maybe clear ur cache. also, double check that ur app permissions r set correctly for the extension to show up.