WordPress error: Authentication failed, not well-formed (invalid token) line 1, column 107

@AndrewJDavison_Luhhu thank you !

@LourdesF - One other thing to try while you wait is to go to the link below and click "Reconnect" next to Wordpress. Can sometimes help.

https://zapier.com/app/connections

😪Unfortunately it does not help. I tried several times but still the same error appears.

thank you anyway

My only other question would be if you added, removed or updated any plugins on your site since first connecting it to Zapier?

No, I added some fields in the advance field pluggin, that's all. This morning I did a new zap with hootsuite and everything was working fine. started giving the error when I added another zap to pinterest and since then I can't reconnect it again.

I don't really know what happened.

Is anything you need to do in wordpress to allow to enter zapier?

@LourdesF - there shouldn't be, but the wording of your error makes it look like Zapier is getting a PHP error from your Wordpress site when it tries to connect.

Now, if it worked before, but doesn't now - and we see that the issue is with Wordpress - it makes sense to backtrack anything you've done in the interim.

What you could do is quickly deactivate every single plugin you've got - test again - and if it works, switch each plugin back on in turn, testing your Zapier connection after each.

I tried again and zapier connected with wordpress.🤗

Whatever happened is resolved.

technology sometimes goes crazy🤪

Thank you @AndrewJDavison_Luhhu

YAY! Glad to hear it.

Thanks for all you help with this one @AndrewJDavison_Luhhu!

Permissions are often a tricky one for connecting WordPress and Zapier @LourdesF, I'm glad that it's worked out now 😊

This help guide has a lot of troubleshooting tips for permission-related errors if it does come up again: https://zapier.com/apps/wordpress/help#common-problems-wordpress

Nobody should take any comfort in a SERIOUS issue that just solves itself.  Imagine if you were relying on this for a production website.  The community should understand how this happened and how it was resolved.  Otherwise, expect it to happen again and to be left hanging.