Skip to main content
Question

GitLab to Mural Zap is not triggering despite successful test

  • 17 July 2024
  • 7 replies
  • 16 views

Hello,

I am automating the workflow between Gitlab and Mural. It works very well to create a sticky in Mural and get an issue in Gitlab.
From gitlab to Mural, it works fine during editing and testing. However, the zap does not create a sticky in Mural after a new issue is created (or updated). From my impression Zapier is not triggered.

Any ideas how to solve that?

7 replies

Troy Tessalone
Userlevel 7
Badge +14

Hi @tom_assmann 

Help links for using GitLab in Zaps: https://zapier.com/apps/gitlab/help

 

I'm getting the error message "Unexpected Status Code 403" when I try to turn on my Zap!

Please ensure that the account you've connected to your Zap has Maintainer permission on the projects you wish to use with your Zap.

⚡ Troy Tessalone - AutomationAce.com | Premier Certified Zapier Expert | #1 Zapier Community Contributor
T

Hi,
thanks for the reply. However this is not the problem. I am working with the maintainer status.
When setting up the automation rule, the test of the rule works fine and I am getting the sticky in mural. But, no event is triggered when I create a new issue and want the corresponding sticky.

What I want:

  • An issue created in Gitlab shall become a sticky in Murla
  • An issue closed shall get a black (new) stick
  • Test instance:
    - Gitlab connected, Event: New Project Issue Event → Event All
    create sticky in Mural.
     
  • did is miss something obvious?
Troy Tessalone
Userlevel 7
Badge +14

@tom_assmann 

If the Zap is not being triggered to run, then the issue likely involves one or a combo of these:

 

You can try opening a ticket with Zapier Support: https://zapier.com/app/get-help

 

⚡ Troy Tessalone - AutomationAce.com | Premier Certified Zapier Expert | #1 Zapier Community Contributor
ken.a
Userlevel 7
Badge +6

Hi @tom_assmann,

I’m jumping in to see if I can help!

I did some digging in our notes, and it seems like this could be that issue is a confidential issues. This seems to be the case especially for issues that are created through GitLab's service desk.

You can try to update the webhook to trigger on confidential issues. You can navigate to Settings > Webhooks and there should be an option to also trigger on confidential issue events.

Kindly give it a try and let me know how it goes? I'll keep an eye out for your response!

T

Hi Ken, Thanks for the reply.
I checked with gitlab, our issues there are not confidential. I tried to modify my Zap, however I am puzzled where to find the settings for confidential trigger. I do not find it in the Zap overview, Zap editor, zap history, personal settings.
I let Zapier check the connections. It is telling me, that everything is fine.
 

ken.a
Userlevel 7
Badge +6

Hi @tom_assmann,

Thanks for the update here.

Unfortunately, I have exhausted my available resources. However, I suggest reaching out to our Support Team regarding this issue since they have the correct tools to look closer at the Zap and its logs and determine what’s happening with the Zap.

You can reach our Support Team here: https://zapier.com/app/get-help

Hopefully, this helps and I appreciate your patience and understanding.

A

gitlab issue doest trigger automatically for me as well where its working while test

Reply


Terms & Conditions