I am currently working on integrating data from HubSpot forms and emails specifically resume attachments into our third-party applications using Power Automate. There in power automate iam getting a json body that consists of the form submitted data .
Upon receiving form submissions through a webhook, I obtain a signed URL for the attached resumes. However, the signed URLs are limited to HubSpot login access, causing issues with integration into third-party applications that require public URLs.
I would appreciate your guidance on the following:
Is there any property of contact that stores the resumes that we got from the froms and emails.
If not, could you provide recommendations or best practices for converting the signed URLs into public URLs for seamless integration with third-party applications?
Is there any way when i am passing that data to an other app through webhook , i can get a public url of the submitted data(resumes attached) which doesn’t require any hubspot access or login? (in my case i am getting the json where the url of the resume attachement is signed and only allows access when the hubspot is signed in )
Hi, @vamshikonda Thanks for your questions. You are correct in noting the limitations of how these endpoints are set up and work. In this case, we are limited to the methods offered in the documentation.
To your questions:
The file (resume) is not stored as a property on an object record
for 2 and 3, there is not a documented method for converting a signed URL or coercing the endpoint to provide an unsigned version. This is for security purposes and not one we can manually avoid
We’ll definitely leave this thread open in case any of our community members have been down this road or have a workaround they want to share.
This sounds like something we’ve had to do before, but may be more complicated on your end.
By default those files are private, so you will need to process them to be “PUBLIC_NOT_INDEXABLE” in order to be able to access them outside of your HS instance. To do this you will need a private app token to update the file before passing it to your intgration.
It might also be an option to create a workflow with custom coded actions that does this for you, then passes the public URL to your integration via a webhook.