Best answer

Failed to create an email in Pardot: Cannot read properties of undefined (reading '@attributes') ​

  • 10 July 2024
  • 6 replies
  • 24 views

I'm attempting to build and send pardot list Emails with HTML content via zapier. if i truncate the HTML content it will schedule at around 2800 characters. I'm assuming this is an api request size limitation? 

 

I get an "Cannot read properties of undefined (reading '@attributes')" error. but it will work if i gradually reduce the character count of the html to below 2880.

 

is there any way around this? can i reference a public html document in the request or compress or split the request? this is such a frustrating error, and makes the send list email function worthless.

 

icon

Best answer by ken.a 17 July 2024, 07:23

View original

6 replies

Userlevel 7
Badge +14

Hi @trent warrick 

For us to have more context, post screenshots with how your Zap steps are outlined and configured in EDIT mode so we can see the app/event in each step along with the field types and field descriptions.

 

Help articles for using Pardot: https://zapier.com/apps/pardot/help

attached images

normally i’d pass this html via airtable, but in testing im using static HTML

Userlevel 7
Badge +14

@trent warrick 

One thing to try is sending this same HTML in Pardot to see if the same error happens.

 

Check for documented limits in the Pardot API for List Email: https://developer.salesforce.com/docs/marketing/pardot/guide/list-email-v5.html

 

So i have tried that, and the same exact HTML does send when pasted in pardot manually. just not when passed by zapier. i really think its a character limit bug.

Userlevel 7
Badge +6

Hi @trent warrick,

It looks like our Support Team discovered that the issue you’re running into with the Pardot app is a known bug. I’ll be including their reply here:

I did some digging into the error message you've received, and I've discovered that the problem is a known issue that's come up for a few of our users when trying to send out longer emails in Pardot, as you mentioned.
 
Your notification is helpful, and we've proactively added your email to our bug report. I'm afraid I can’t provide an ETA for when this issue might be resolved because prioritization is largely dependent on the number of customers affected. You'll be the first to know via email when there's a resolution.
 
As for a workaround for this, it appears that the body of the email is sent as part of the URL and since that creates a very long URL, a "URI Request Too Long" error is presented. Ideally, the body would not be sent as a part of the URL, but it's my understanding that this is default behavior for Pardot: https://developer.salesforce.com/docs/marketing/pardot/guide/emails-v4.html
 
That being said, it may be worth trying out a Webhooks or Code by Zapier action to see if this can be adjusted. 
 
Just to be upfront, these are considered advanced features, so our support for it may be more limited. Not because we don't want to help, but because APIs can be tricky to troubleshoot since we can't see what's happening on the other side. Every API that you send a request to is going to have slightly different structures that are required.
 
This makes it hard for us to know why the request may be receiving errors or not working as expected, beyond taking a general look at what's showing in Zapier.
 
Here are some resources that may be helpful:

 
If you are running into feature limitations, you could take a look at our blog post here: 
https://zapier.com/blog/advanced-webhooks-with-the-zapier-platform-interface/
 
For anything that I may not be able to answer, here are some other options:

 
I wish I had better news here! Please let me know if you have any other questions.

I appreciate your patience and understanding.

Reply