web
You’re offline. This is a read only version of the page.
close
Skip to main content

Announcements

News and Announcements icon
Community site session details

Community site session details

Session Id :
Power Platform Community / Forums / Power Automate / Replacing Gitlab Incom...
Power Automate
Suggested Answer

Replacing Gitlab Incoming Webhook Integration

(4) ShareShare
ReportReport
Posted on by 6

My team had an integration between Gitlab and Microsoft Teams using the instructions here: https://docs.gitlab.com/ee/user/project/integrations/microsoft_teams.html

 

This utilized the the webhook connector in Teams. Yesterday a team member noticed the following message at the bottom of all our notifications:

Action Required: O365 connectors within Teams will be deprecated and notifications from this service will stop. Learn more about the timing and how the Workflows app provides a more flexible and secure experience. If you want to continue receiving these types of messages, you can use a workflow to post messages from a webhook request. Set up workflow 

 

I clicked the Set up workflow link, generated a new webhook URL, and replaced the URL in the Gitlab environment under our existing integration. Now everything is broken. Through random clicking in the Workflows interface I managed to find that I could click on "Run history" and then the Start time timestamp to get to a page with error messages. The message is:

 

Error
Action 'Send_each_adaptive_card' failed
 
Error Details
The execution of template action 'Send_each_adaptive_card' failed: the result of the evaluation of 'foreach' expression '@triggerOutputs()?['body']?['attachments']' is of type 'Null'. The result must be a valid array.
 
Has anyone had success integrating Gitlab notifications with the new Teams Workflows integration?
Categories:
I have the same question (0)
  • MatthieuT Profile Picture
    3 on at

    Hi,

     

    I have the same issu.

     

    If any one have informations 🙂

  • drkfhr Profile Picture
    2 on at

    Also having this issue, any luck so far?

  • lbendlin Profile Picture
    8,649 Super User 2026 Season 1 on at

    May I recommend you read through the comments section on that blog entry...

     

    Retirement of Office 365 connectors within Microsoft Teams

  • kbrucker Profile Picture
    7 on at

    I read through the comments on the MS retirement post but I didn't find anything helpful. Mostly people complaining about this change and that they are unable to get this working. There were 11 pages of comments when I looked... One big problem seems to be that it doesn't support private channels. That could be the problem I'm running into.

    Took me a bit to figure out how to see the errors. What a terrible interface.

  • kbrucker Profile Picture
    7 on at

    There's a gitlab issue open: https://gitlab.com/gitlab-org/gitlab/-/issues/471344

  • Suggested answer
    TL-30071746-0 Profile Picture
    on at
    YES! I have managed to do it.

    I am releasing a solution + steps to make it easier for everybody else who has to go through the same situation, and figure it out like I did. Please see https://gitlab.com/gitlab-org/gitlab/-/issues/471344#note_2022899536

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Introducing the 2026 Season 1 community Super Users

Congratulations to our 2026 Super Users!

Kudos to our 2025 Community Spotlight Honorees

Congratulations to our 2025 community superstars!

Congratulations to the March Top 10 Community Leaders!

These are the community rock stars!

Leaderboard > Power Automate

#1
Haque Profile Picture

Haque 592

#2
Valantis Profile Picture

Valantis 340

#3
11manish Profile Picture

11manish 284

Last 30 days Overall leaderboard