Skip to main content

I have been working with this for 2 days, and its still not working even using Copilot. Please help me

 

Hi ​@MariaJimenez 

Help us have more info about the Zap step error by posting screenshots showing how Zap step 2 is configured in the CONFIGURE tab while in EDIT mode so we can see the field types and field mappings.

 


 


@MariaJimenez 

Looks like you might be testing with bad data or dummy data.

For the selected Zap trigger step example record...

e.g. Variable “Profile Email” has a value of “Info Requested”, which is not a valid email address.

 

This is related to the data returned from Eventbrite.

Review these related Zapier Community topics for Eventbrite to have context: https://community.zapier.com/search?q=eventbrite%20info%20requested&tags%5B0%5D=Eventbrite&content_type%5B0%5D=question

Help links for using Eventbrite in Zapier: https://zapier.com/apps/eventbrite/integrations#help

 

 

 

 


Hey ​@MariaJimenez,

Here is a helpful article about modifying trigger test data in Zap- https://help.zapier.com/hc/en-us/articles/33561391372429-Modify-test-records-in-Zaps

You can also look into KvCORE create API documentation to see what fields types it expects- https://apidocs.kvcore.com/#860b0127-8228-44e9-afde-2cc0ca5f3fdb.

Try with valid test data and see if it fixes it. Hope it helps!


I've been having the same issue for 5 days now. My Zap has been working fine and it just started getting this error. 

 

This post has been edited by a moderator to remove personally identifiable information (PII). Please remember that this is a public forum and avoid sharing personal or potentially sensitive details.


Hi ​@MariaJimenez 👋 Just came across this and it looks like you’re running into the same bug that ​@rileywalters was being affected by over here:

So I’ve gone ahead and added you to the list of folks being impacted by that bug as well. I can’t make any promises as to when kvCORE’s developers will be able to get it fixed by but you’ll get an email notification as soon as it is. 

Since there’s already one topic discussing this bug, we’re going to close this topic now so that folks can follow along with any updates on it in a single place.

For anyone that comes across this post and wants to be added to the bug report please reach out on the main topic here and we’ll take care of that.