Skip to content

svhawks/serverless-microsoft-teams-gitlab-connector

Repository files navigation

Serverless Microsoft Teams Gitlab Connector

serverless

Easy integration to notify GitLab Merge Request and Issues to Microsoft Teams.




How to use

Microsoft Teams Side

Step 1️⃣

In Microsoft Teams, choose the More options (⋯) button next to the channel name in the list of channels and then choose Connectors.


Step 2️⃣

In the list, click Add for the Incoming Webhook. enter image description here


Step 3️⃣

Enter the connector name as GitLab and upload an icon. Save and copy your connector url (channel_incoming_webhook_url).

GitLab Side

Step 1️⃣

Go to your repo settings on GitLab and click Integrations section from left bar. Copy this link: https://0xjjw6j039.execute-api.us-east-1.amazonaws.com/prod/events?url=channel_incoming_webhook_url and change channel_incoming_webhook_url part with your teams url. Then paste it to url input area on GitLab.


Step 2️⃣

Enable Issues events, Merge Request events and SSL Verification then save it.

GitLab Webhook



Deploy to your aws acount

git clone git@github.com:svtek/serverless-microsoft-teams-gitlab-connector.git
cd serverless-microsoft-teams-gitlab-connector
npm install

If you don't want to add the channel_incoming_webhook_url as params to your function endpoint url: Follow Microsoft Teams steps, copy the url and add it to you env variables. export channel_incoming_webhook_url=https://outlook.office.com/webhook/...

Deploy: serverless deploy

Then follow the GitLab steps and add https://your-function-endpoint-url/events to url input area on GitLab.

Testing Locally:

serverles offline start
./ngrok http 3000
# add `/events` path to output url and paste (https://123456.ngrok.io/events) to GitLab url input.

Features

  • Merge Request
  • Issues
  • Push
  • Comments
  • Jobs

Authors

Sahin Boydas

Founder @ Remoteteam.com
LinkedIn
Muhammet

Developer @ MojiLaLa
Github
Sadik

Developer @ MojiLaLa
Github

Releases

No releases published

Packages

No packages published

Contributors 3

  •  
  •  
  •