Gitlab Integration

What can I see with Webhooks on Gitlab?

You can use a webhook as a trigger of events. When you want a trigger or update sent from Gitlab after an issue event occurs, use a webhook. For example:

• You can trigger a webhook when you push to a repository.
• You can create a webhook when a new issue is created or an existing issue was updated/closed/reopened.

You can see a list of events you can enable in the picture bellow.

Getting Started – Setup Gitlab integration at Blendo.

1. Login to your Gitlab dashboard from a browser tab

2. Go to your project. Click on the gear icon in the top right side of your dashboard and click on Integrations.

3. You will see a box URL and list of checkboxes with the events that can be triggered e.g. Push events, Comments, Issues events, Merge Request events, Build events and more. Check any of these you want to push to your data warehouse.

Setup Gitlab and Blendo integration

In Blendo, for every separate webhook that you create, another different table will be created in your output database. For example:

a) You may create a webhook in Blendo that you will send all the Issue events.

b) Create another webhook in Blendo that you will send all the Push events.

6. Open Blendo in a new browser tab.

7. Add a webhook (in our example we will use this to receive only the Push events)

8. In the new page, you will setup the Webhook. Add a table prefix if you like. It will help better separate your tables. Click Save.

9. Then you will return back to the home dashboard. Click on your new Webhook data source.

10. Let’s change the name to reflect its use. Hover over the name Webhook and click on it and rename it if you like.

10. In the same page you may see the Webhook address we are going to use to send our Gitlab data.

11. Copy the URL.

12. Go to your browser tab with Gitlab.

13. In URL box, paste the URL we copied from step #11 above. Click Add Webhook.