portalId missing from "IFRAME" action outbound request

Develop, Build & Integrate APIs & Integrations
1

Hi,
When the action in the card is “ACTION_HOOK”, on click the request that goes out to the endpoint contains the following properties: portalId, associatedObjectType, associatedObjectId, but when the action is “IFRAME”, those fields are missing.
My entire flow is based on that, because those portal ids are mapped to the refresh tokens from the installation of the app on those portals.
Is this a bug? if not, how can I get that portal ID and other fields to be sent out as part of the GET request for the IFRAME?
Thank you.

2

Hey, @ISlonim :waving_hand: Do you have a specific API document you are looking at? I want to make sure I start with what you are working with. This is the most direct way to try to track down if it’s working as designed or if there is another issue.

Thanks! — Jaycee

3

Hi Jaycee,
The API being called when you return an “IFRAME” action button in a card - Accounts Dashboard | HubSpot

4

Hey @Jaycee_Lewis ,

Just wanted to confirm I am also seeing this. In the action deffinition for the type IFRAME, I have some associatedObjectProperties that I would expect per the docs to be uri query params:

Accounts Dashboard | HubSpot (scroll down to iFrame actions)

  • associatedObjectProperties: A list of properties on the associated contact, company, deal, or ticket. The values of the properties for the current object will be appended to the uri as query parameters when opening the iframe.

Here’s an example:

{'results': [{'actions': [{'associatedObjectProperties': [],
 'cancelButtonText': 'No',
 'confirmButtonText': 'Yes',
 'confirmationMessage': 'Are you sure you want to '
 'Cancel this Member?',
 'httpMethod': 'DELETE',
 'label': 'Cancel Member',
 'type': 'CONFIRMATION_ACTION_HOOK',
 'uri': 'https://redacted'},
 {'associatedObjectProperties': ['associatedObjectId',
 'portalId',
 'userId',
 'userEmail',
 'domain'],
 'height': 748,
 'label': 'Change Linked Members',
 'type': 'IFRAME',
 'uri': 'https://redacted/linked',
 'width': 890}],
 'link': 'https://redacted',
 'title': 'Redacted'}],
 'settingsAction': {'height': 748,
 'label': 'Settings',
 'type': 'IFRAME',
 'uri': 'https://redacted',
 'width': 890}}

I would expect https://redacted/linked to get something like https://redacted/linked?userId=123&userEmail=user@example.com&associatedObjectId=321&associatedObjectType=CONTACT&portalId=123456789

Oddly enough, this works on the CONFIRMATION_ACTION_HOOK.

Would love to know if I missed something.

Thanks!

5

@Jaycee_Lewis
I managed to somehow get around it by getting the portal id from the header “referer”, but for some customers (in EU, don’t know if that is relevant) the “referer” header only contains the base url without the rest of the portal id. Do you have any updates regarding my question? thank you.

6

@Jaycee_Lewis , @ISlonim ,

Just checking in, either of you learn any more about this issue?

7

Crickets so far..
@Jaycee_Lewis

8

@Jaycee_Lewis @hubspot Anything? this is causing major issues for us and preventing us from integrating with Hubspot.