Hi @BezFin 

Try using this Zap action: Pardot - API Request

If you still need help, post screenshots with how your Zap step is configured to give us full context.

Thanks - I’ll try that, but my point was that it’s almost as if this app could never work, even for the most basic of events it provides.

I talked to Zapier support and after a lengthy session of back and forth, it seems that the problem in using Pardot V5 API via their app is a known issue with no workaround available or ETA on if/when it will be fixed.

Hope this saves other people the hassle.

Thanks so much for flagging this in the Community and for following up with that update here, @BezFin. It’s greatly appreciated! 

Hopefully that workaround Troy suggested of using the API Request action will help to get things working in the meantime. Do let us know if you run into any trouble using that action, happy to help further! 
 

Thanks Sam,

Unfotunately it doesn’t look like the workaround suggested by Troy would work since the App isn’t using the correct URL for it’s API calls. Perhaps you’re aware of someone else that did manage to get this to work?

Hi folks 

Sorry for missing your reply here previously @BezFin! Just circling back in here to share that the bug report has been closed. In case you’ve not seen the email notification that went out here’s what you need to know:

So to confirm, when connecting your Pardot account you’ll need to select v4​​​​​​ option (v3 if using an older Salesforce account) and that should allow you to ​use the app without running into any errors. 

If you reconnect your Pardot account and select v4 (or v3) and are still running into these errors please let us know. In the meantime, happy Zapping! 

Thanks Sam,

So essentially, the “fix” was to completely disable support for Pardot API Version 5, and the Pardot app was updated to remove V5 from the API version selection pull-down.

Are you aware of any plans to implement V5 at any time in the future?

Thank you for sharing the solution, @BezFin and thanks to SamB for pointing you in the right direction!

As for your question about V5, Unfortunately, there is currently no feature request open for supporting API Version 5.

My suggestion would be to get in touch with our Support Team, who can create a feature request on your behalf to support the V5 API version.

You can contact our Support Team through this link: https://zapier.com/app/get-help

Dear Community,

I wanted to reach out about this, because it seems that Salesforce OAuth is a thing now, also for versions 3 and 4. 

Source: https://developer.salesforce.com/docs/marketing/pardot/guide/version-3-4-overview.html

Interestingly, I can’t seem to use the custom api request action at all anymore. All my Custom Actions pardot-based are completely annihilated now and return a 403 at best:

An error occurred while running action 78084: Code runner error while running code: Got upstream error: status=403 body={"Message":"Forbidden"} Will retry... Got upstream error: status=403 body={"Message":"Forbidden"} Will retry... Got upstream error

How is it possible that pre-defined actions are working, and the custom isn’t? 

There has to be at least an explanation for that, or at best an instruction for making it work.

The connected account is of course enabled for v4 with the correct pardot business unit id, so nothing particular changed, except it stopped working.

Best,

Alex

Thank you so much for flagging this, @Alex Avesco! Hmm, if it’s no longer possible to use versions 3 or 4 then I’d recommend reaching out to our Support team directly to have this investigated further. They’ll be able to open up a bug report for this as necessary so that the developers of the Pardot app on Zapier can get this sorted.

Please do keep us updated on how you get on with them. If they’re able to suggest a workaround I’m sure folks coming across this thread would really appreciate it if you’d share that here!