Hi @jshurtleff33 

Good question.

Perhaps try this approach…

Add a Zap step to find the contact by email to get the Contact ID, then use the Contact ID.

Hey @Troy Tessalone 

Assuming I did that and had the VID to work with I then just tested the extension with a sample Record ID from an existing contact got the same response. I even tried setting the contactId data type on the extension set up as string, text, integer, and number and all of them returned an error during execution.

Were you able to test and reproduce my problem and get it to work on your end?  

@jshurtleff33 

Another option to try would be to use this Zap action: HubSpot - API Request

Update - I was able to get the extension to work when using the contact VID and having {{contactId}} in the URL instead of {contactId} (single vs double curly brackets). I’ll use this for now but for some reason when I add the "idProperty": "email" query or body param it returns invalid URL so it appears something about the URL encoding from zapier that is going on is not working or the hubspot API is broken at the "idProperty": "email"

query param variation of the /crm/v3/objects/contacts/{contactId} end point  endpoint.

That’s great news @jshurtleff33! Thanks so much for sharing details of how you were able to resolve the issue with the contactID being incorrectly referenced in the URL. 

With the second issue, judging by the examples in the HubSpot API documentation it seems to expect to receive the idProperty within the body of the request, not appended to the URL as a query parameter. When you remove the idProperty settings from the Query Parameters section and just have it included as a body parameter do you get the exact same error about the URL being invalid?

If you get a different error could you share a screenshot of that here? Thinking that error might contain details that help us to better identify what changes you might need to make to fix it. Thanks, looking forward to hearing from you!

@SamB I get the following error when I use "idProperty": "email" as body parameter in the json block which to me inplies that it’s not picking it up in the body as an alert to the API to use an email as the idProperty. The only other option is to then use it as a url query param which isn’t working either. Quite the conundrum. I’ve presented this information to hubspot support and am waiting to hear back.

If you or someone could try to recreate either of these errors or get it to work as a query or body parameter please update this thread, it would go a long way to helping the community and myself understand this issue. 

Thanks for sending over those helpful screenshots @jshurtleff33!

I’ve been doing some further digging and came across this thread in the HubSpot community here which seems to suggest that adding the email address and the idProperty directly into the URL of the request should work:

/crm/v3/objects/contacts/tstemail@gmail.com?idProperty=email

So can you try removing the reference to the idProperty in the Body field and instead of adding it into the Query Parameters fields, just update the URL to:

https://api.hubapi.com/crm/v3/objects/contacts/{contactId}?idProperty=email

Just thinking that maybe adding it into the Query Parameters fields was partly causing it to not be added to the URL in the exact way that HubSpot was expecting. 

And also, can you try updating the Body of the request to something more like this:

{
    "inputs": {
        {
            "id": "{{contactId}}",
            "properties": {
                "lender_lead_status": "{{lender_lead_status}}"
            }
        }
    ]
}

I can’t guarantee these changes will work but thought it worth exploring just in case that does the trick. Please keep us updated on how that goes, I’m very keen to know whether or not that solves it!