About Zapier Community
New to our Community? Get to know more about our space and how to make the most of your time here.

Code of Conduct Community FAQ's Zapier Common Questions What to Expect

Get Started With Zapier
New to Zapier? We have got you covered with our Zapier 101 Resources.

Zapier Essentials

Get Support
Have a question? Let's get you an answer!

How Do I...? Troubleshooting Code & Webhooks Developer Zone

Other Help Resources
Wait, there's more! Check out these Community sourced spaces for additional resources.

Zapier Help Center Hire an Expert

Zapier Products
Learn more about Zapier's new products.

Zapier Tables Zapier Interfaces Zapier Canvas Zapier Chatbots

Zapier Reading
All of our best learning resources can be found here.

Featured Articles Show & Tell AI Hub Zapier Tools Hub

Learning Groups
Excited to meet other builders? Check out our interest areas full of doers, dreamers, and in-betweeners.

User Groups

Other Learning Resources
Some of our favorite additional ways to upskill your Zapier knowledge.

Zapier Learn Zapier Blog Zapier Webinars

Product Updates
Check out what is new and upcoming with Zapier with our regular product updates.

Product Updates

Early Access Program
Want to join Early Access? Learn more here.

Best answer

Keller Williams command error: Email address already exists

  • 27 October 2022
  • 1 reply
  • 48 views
M

I am having the same issue. But MohSwellam’s explaination does not work for me. I know for a fact that the email addresses don’t already exist, because I am making them up to test the webhook. When I test the zap while in my Zapier account, it works. It creates the contact. But when I put the webhook on my PluginOps landing page that’s when I get the above mentioned error message. It doesn’t make sense.

icon

Best answer by Danvers 1 November 2022, 15:05

View original
This post has been closed for comments. Please create a new post if you need help or have a question about this topic.

1 reply

Danvers
Userlevel 7
Badge +12

Hi @mikepadlo!

I can see that you’ve been in touch with the Support team about this issue and they were able to help you out. In case anyone else is having the same issue, the problem was that the information was typed into the fields, meaning that the Zap will use the same information each time it runs. 

To resolve this, you need to retrieve sample data from your trigger, and use the fields to map the values in the Keller Williams step. 

Terms & Conditions