Hi @King Wu ,

Thanks for stopping by!

Am I understanding correctly that your Zap is triggering but then you’re receiving the above error? Or can you get it to trigger at all?

If you can share some screenshots of your configuration (minus personal info) we can try to help further.

I suspect our Support team may the best folks to identify the issue here as they can take a look into your specific Zap & its history!

Hi Liz,

I just config the zap as the following setting. But, i get the email fail in this action.
 

@King Wu, thanks for the extra details!

It might be the case that the group selected for the GitLab trigger does not exist anymore hence causing the 404 Not found error.

I suggest clearing the current group that is selected then re-selecting a group based on whatever populates in the dropdown. That should ensure that a currently existing group is selected.

Can you give that a try and let me know if you run into issues?

@Paolo Thanks for your reply. I tried to switch different groups. Still get the 404 error. Does any config on Gitlab side for group merge request event?

Hi there @King Wu!

I don’t know if there’s any config on Gitlab side for group merge request events that needs to be tweaked to fix this. But I wonder if it’s a permissions related issue as I know that can sometimes cause problems.

Does the connected Gitlab account have “Maintainer” permissions for the project? 

If not, try changing the permissions in GitLab for that account to “Maintainer”, reconnect the GitLab account so the Zap can connect using the updated permissions and to see if that sorts it. Please do let us know if that does the trick! 

@SamB My account already is “Owner”. Should be no access permission issue?