Elastic Email Content Parameter Error

Status: Closed · Asked by rommel on · 0 views

rommel — Question ·

Hello,

I'm employing Elastic Email to dispatch transactional emails containing pre-populated information to our form. However, I'm encountering an "Incorrect Format" error.

I've checked the code in HTML viewer and it is working fine. Any thoughts?. Thank you

Arshita — Reply ·

Hey @rommel

Kindly provide us with the workflow URL in which you are getting an issue.

So we can check on it and guide you further.

Arshita — Reply ·

You can change the content type from HTML to Plaintext. Please refer to the 2nd part of the below video tutorial and try again:

youtube.com/watch?v=r0PjuP8mQyc

rommel — Reply ·

@Arshita i changed it to Plain text and still the same error occurs.


I noticed that if i remove the button with css style and hyperlink the email works.


The sample video only uses only plain text and without custom style. I want to add design in my email template just like what i can do in zapier.

Hope you can help us for this. thank you.

rommel — Reply ·

In addition,

I've also checked our Old flow with elastic email on it and they are working fine but deprecated.
Here's the screenshot

Arshita — Reply ·

As I can check now your "Brunetti Site Support Widget" workflow, it appears that you have successfully entered the message in HTML format, and your action step is functioning properly.

rommel — Reply ·

@Arshita It displays a parameter error when I attempt to add this button along with its styles.

The previous version of Elastic Email functioned flawlessly, but it appears to have encountered issues following the recent update.

Arshita — Reply ·

As per my observation, when you are passing the message in HTML format, you have selected plain text, which means in plain text, you need to keep your message body without HTML.

Additionally, in the workflow, I am unable to find this email format, so I am unable to test it.

Arshita — Reply ·

Hey @rommel

We have added the "Replace Text" action step to replace the (") with (') and it is working fine.

Please try this approach from your end and test it out.

rommel — Reply ·

Thank you @Arshita. It works.

Back to all forum threads · Log in to reply