Skip to main content

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

Learning Resources
All of our best learning resources can be found here.

Featured Articles Show & Tell Zapier's products AI Hub Zapier Tools Hub

Share your knowledge
Give back to the Community by sharing your automation wins and helping to answer questions.

Share your success See unanswered questions 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.

Question

New Group Merge Request Event in GitLab An error occured: 404 Not Found

  • December 22, 2022
  • 6 replies
  • 211 views
K

Hello, I am using zapier to build with Gitlab and Notion.

i tried to create a trigger with `New Group Merge Request Event` . But, i recieved an email to tell an error -  New Group Merge Request Event in GitLab  An error occured: 404 Not Found. 

Not sure how to resolve the issue. What i tried, i was sucessful to build with `New Project Merge Request Event in GitLab`. Replace by Group. Then fail.

Any advice with it?

Thanks.

 

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

6 replies

Liz_Roberts
Forum|alt.badge.img+8
  • Liz_RobertsZapier Staff
  • Zapier Staff
  • 1366 replies
  • December 23, 2022

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!

K
  • King WuBeginner
  • Author
  • Beginner
  • 3 replies
  • December 29, 2022

Hi Liz,

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

 

Paolo
Forum|alt.badge.img+5
  • PaoloZapier Staff
  • Zapier Staff
  • 98 replies
  • January 4, 2023

@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?

K
  • King WuBeginner
  • Author
  • Beginner
  • 3 replies
  • January 4, 2023

@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?

 

 

SamB
Community Manager
Forum|alt.badge.img+11
  • SamBCommunity Manager
  • Community Manager
  • 9652 replies
  • January 5, 2023

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! 

K
  • King WuBeginner
  • Author
  • Beginner
  • 3 replies
  • January 18, 2023

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?

Terms & ConditionsAccessibility statement