Unanswered

Replacing Gitlab Incoming Webhook Integration

Like (4) Share

Report

Posted on 9 Jul 2024 13:12:59 by spriley_msts

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?

All responses (6)

Answers (0)

Suggested answer

TL-30071746-0 on 30 Jul 2024 at 17:47:28

Like (1)

Report

Replacing Gitlab Incoming Webhook Integration

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
kbrucker 7 on 10 Jul 2024 at 22:12:30

Like (2)

Report

Re: Replacing Gitlab Incoming Webhook Integration

There's a gitlab issue open: https://gitlab.com/gitlab-org/gitlab/-/issues/471344
kbrucker 7 on 10 Jul 2024 at 21:51:20

Like (0)

Report

Re: Replacing Gitlab Incoming Webhook Integration

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.
lbendlin 7,906 Super User 2025 Season 1 on 10 Jul 2024 at 17:42:02

Like (0)

Report

Re: Replacing Gitlab Incoming Webhook Integration

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

Retirement of Office 365 connectors within Microsoft Teams
drkfhr 2 on 10 Jul 2024 at 17:33:57

Like (0)

Report

Re: Replacing Gitlab Incoming Webhook Integration

Also having this issue, any luck so far?
MatthieuT 3 on 10 Jul 2024 at 09:03:52

Like (0)

Report

Re: Replacing Gitlab Incoming Webhook Integration

Hi,

I have the same issu.

If any one have informations 🙂

Community site session details

Replacing Gitlab Incoming Webhook Integration

Helpful resources

News and Announcements

Quick Links

Announcing the Engage with the Community forum!

🌸 Community Spring Festival 2025 Challenge Winners! 🌸

Warren Belz – Community Spotlight

Leaderboard > Power Automate - Using Connectors

Featured topics

Product updates

Community site session details

Replacing Gitlab Incoming Webhook Integration

Helpful resources

News and Announcements

Quick Links

Announcing the Engage with the Community forum!

🌸 Community Spring Festival 2025 Challenge Winners! 🌸

Warren Belz – Community Spotlight

Subscribe to this forum!

Select categories

Leaderboard > Power Automate - Using Connectors

Featured topics

Product updates