Skip to main content
Best answer

Zap failing because of "invalid data" after field mapping has been corrected

  • November 12, 2024
  • 7 replies
  • 59 views

Forum|alt.badge.img

I had a zap that was failing because the squarespace form was appending text onto the email field. I initially followed the advice to create a multi-stage zap but then corrected it at the squarespace end. 

The zap is now stuck - I think it thinks I’m still trying to map split data onto the email field but it’s actually mapped correctly, as far as I can see. Feels like some kind of cache issue or something? Would love some help fixing this!

 

Best answer by taketheheartBest answer by taketheheart

Troy Tessalone wrote:

Hi @taketheheart 

The variable mapped to the Email field is a dummy email address, which is likely why it resulted in an error.

 

Try turning the Zap ON and testing live.

Then check your Zap Runs history details to see the DATA IN/OUT for each Zap step to help you troubleshoot: https://zapier.com/app/history/

 

NOTE: You may need to instead use this Zap action: MailerLite - Create or Update Subscriber

You can set the desired Group.

 

This worked - I skipped the test, ignored the warning and published the zap, which then worked when I tested it live.

 

Thanks so much for the support!

View original
Did this topic help you find an answer to your question?

7 replies

JammerS
Forum|alt.badge.img+6
  • Zapier Staff
  • 2350 replies
  • November 13, 2024

Hi @taketheheart,

 

Welcome to the Community. 

 

Upon checking the error message, I see the issue here is with the email format. Mailerlite doesn't allow emails like admin@ or support@ to be imported. You can refer to this help link 

https://www.mailerlite.com/help/how-to-import-subscribers to resolve the error message.

 

Let us know if you need further assistance. Thank you.


Forum|alt.badge.img
  • Author
  • Beginner
  • 9 replies
  • November 13, 2024

Hi @JammerS 

Thanks for your reply, but I’m confused because the email in question was the one create in the Zapier test. See the first screenshot. The second one cuts off at the start of the email, which is the automatically-generated zapier-demo@squarespace.com. It isn’t admin@ or support@. Please can you explain how I can fix that in the zap set up? I’m not trying to import subscribers.

Thanks,

Emma


Troy Tessalone
Forum|alt.badge.img+14
  • Zapier Expert
  • 30974 replies
  • November 13, 2024

Hi @taketheheart 

The variable mapped to the Email field is a dummy email address, which is likely why it resulted in an error.

 

Try turning the Zap ON and testing live.

Then check your Zap Runs history details to see the DATA IN/OUT for each Zap step to help you troubleshoot: https://zapier.com/app/history/

 

NOTE: You may need to instead use this Zap action: MailerLite - Create or Update Subscriber

You can set the desired Group.

 


Forum|alt.badge.img
  • Author
  • Beginner
  • 9 replies
  • November 14, 2024

Hi @Troy Tessalone 

Ah thanks for explaining that - I’ll give that a try and let you know how it goes!


ken.a
Forum|alt.badge.img+6
  • Zapier Staff
  • 6395 replies
  • November 14, 2024

Hi @taketheheart,

Please keep us updated regarding this one. If you’re still stuck setting up the Zap we’re happy to troubleshoot further!

 


Forum|alt.badge.img
  • Author
  • Beginner
  • 9 replies
  • Answer
  • November 14, 2024
Troy Tessalone wrote:

Hi @taketheheart 

The variable mapped to the Email field is a dummy email address, which is likely why it resulted in an error.

 

Try turning the Zap ON and testing live.

Then check your Zap Runs history details to see the DATA IN/OUT for each Zap step to help you troubleshoot: https://zapier.com/app/history/

 

NOTE: You may need to instead use this Zap action: MailerLite - Create or Update Subscriber

You can set the desired Group.

 

This worked - I skipped the test, ignored the warning and published the zap, which then worked when I tested it live.

 

Thanks so much for the support!


JammerS
Forum|alt.badge.img+6
  • Zapier Staff
  • 2350 replies
  • November 15, 2024

Thanks ​@Troy Tessalone for pointing our member to the right direction. Also thank you for sharing the resolution that you did ​@taketheheart this will help our Community members regarding with the same issue.