Hello dear Hubspot community and Staff,
I am working on a Hubspot integration using the CRM extension cards. For custom cards we receive the session information (user email, user id, portal id etc) along with specified associated object properties when the cards API initiates a data fetch to retrieve the information to be displayed. However, we would also like to receive the session information, especially the user email address, when the secondary actions are triggered. In the API documentation, there seems to only be a way to specify the properties in an “associatedObjectProperties” array (in our case the associated object is a deal) and no way to request session properties. Since session infomration is not a property of a deal I am not sure how to request this. If there is a way to pass the email of the user in session when an action is triggered I would appreciate your assistance on it.
Thank you in advance,
Cheers
@kaleemmolani 
Any chance you could help @SMirgadirova out here?
Thank you, no need for further assistance on this question.
I have found the solution to the issue. I’ll explain it here in case someone faces the same confusion I did in the past. One can pass query arguments to the IFRAME action links directly through the uri field in actions properties. My confusion stemmed from the fact that we had to pass base action URLs for all possible actions at the very beginning in the definition of the card extension. Hence, I thought these links must be immutable in the uri field of the action and that no other queries except for the requested ones can be added to the passed link. However, that is not the case and the query string can differ from call to call and the developer can pass whichever properties needed apart from the associated object along directly in the uri field without requesting anything from Hubspot.
Nonetheless, thanks @dennisedson for referring the question and @kaleemmolani can consider it closed or solved
@SMirgadirova you are right, query params will differ from object to object and URI for IFRAME can be programmatically changed in the response.