Pardot Zap - Unable to update Prospect job_title using V4 API Request - title remains null

Hi ​@Benson 

TIP: Try sharing your screenshots with ChatGPT and asking for help fixing the issue.

Troy, once again, thanks for your assistance!  Your suggestion worked perfectly.  I have been basing my attempts to perform the update on the success I had when using your previously (successful) suggestion to create a prospect.  I was assuming I needed to rely on JSON to provide the field/value pairs.  It didn’t occur to me to rely on setting query String parameters (as opposed to URL parameters and the Body JSON string) when configuring the request.

Appreciate your (timely) help once again !!    (I’ll  give that ChatGPT suggestion a try next time!)

Thanks !

​@Troy Tessalone - Thanks for your continued assistance. I’ve submitted two requests to this community and both times your timely suggestions addressed my issues, saving me a great deal of time and anxiety.

😦 As an aside - regarding use of AI for problem solving 😦 - I was taken off-guard by an unexpected AI action…  BRIEFLY: I regularly use GROK for AI assistance.  I wanted a record of the successful Zapier/Pardot API Request “Update Prospect” response.  I inspected the Zapier response web page, clipped the raw HTML for the element containing the response content, and submitted it to GROK asking it to generate a viewable web page containing the Request URL, some Request name/val pairs, and specific response name/val pairs - all embedded in the Zapier response HTML. After a couple of request iterations, the page was generated - HOWEVER - in the final iteration, the Prospect job_title field I had originally updated containing “Product Manager”, now contained ALTERED content “Sales Product Manager” (not an item in the picklist), with an updated timestamp corresponding with the final iteration of my request to GROK (!)  It appears GROK resubmitted the ZAP (having modified the field data) and generated the HTML page which now included altered field content.  I reviewed the Prospect to confirm that the job_title field had indeed been altered.  This is extremely unsettling.  Without time for further sleuthing, I suggest folks be cautious when including content in requests (e.g. URLs) that can potentially be acted upon by AI. If I learn more, I’ll post it. 

​@Benson 

AI would only be able to attempt an API request if it has the authentication. (e.g. API key)

General rule of thumb is to not share your API key publicly.

​@Troy Tessalone Appreciate your reply…  We make use of a PARDOT connection between Zapier and Pardot (SF Account Engagement) relying on the secure embedded OAuth2 interaction within that connection, so I believe we’re not relying on an exposed API key.  Reconsidering this, it seems more plausible that somehow GROK re-executed the particular Zapier step’s test action.  I don’t think I’ll pursue this further at the moment, but will exercise caution moving forward and will investigate further when time allows…  I welcome your thoughts.  Thanks!

​@Benson 

Without screenshots or a Loom.com video for true context, we are not really sure what/where you are referring to.

FYI...GROK is not listed as a Zapier Subprocessor: https://zapier.com/legal/subprocessors

​@Troy Tessalone  Grok (.com) is Elon Musk’s AI app.  I have recently found it to return the most definitive responses (and code samples) in response to my software-related AI queries, especially when selecting its “Think harder” mode - which invokes a more powerful secondary model (as compared to Copilot & ChatGPT).  I’ve been experimenting with its capabilities - which is what I was doing when I submitted the raw PARDOT html response content to it and asked it to generate a viewable web page (described earlier).  I was merely looking for a viewable reference to include in my personal docs for later use.  I should say I have confidence in the Zapier Pardot Connection’s security implementation.  I need to become more familiar with do’s and don’ts when relying on AI.