Hey @knightmar!
I expect you’ve already seen the email about this but I wanted to leave a quick update here to confirm that this issue should be resolved now.
That said, if you find that you’re still seeing this error in your Zaps please do contact our Support team. They’ll be able to take a look at your Zaps and reopen the bug report if necessary.
ok thank you very much for spending time on my problem
Hey @knightmar! :)
I’m so sorry that you’re running into this error in your Discord Zap. I’ve been looking into this and it seems that this is a known bug with the Discord integration which is also being discussed in another thread:
I’ve added you as an affected user on that bug report as well, so we’ll be in touch by email as soon as it’s been resolved. And we’ll also put out an update here once it’s been fixed.
In the meantime, it was mentioned in the other thread that it should be possible to select the user by its User ID, when selected as a Custom value. So if you ignore that error and test that step with a User ID, it should go through to Discord successfully. Hope that helps!