GitLab webhook setup

GitViber adds and repairs its webhook on every project used by an enabled route, including each project in a group route. Groups are rechecked every 15 minutes for new projects. Manual setup below is only needed if automatic setup reports a failure.

In GitLab

1. Open the project, then Settings → Webhooks → Add new webhook.
2. Paste the Webhook URL into URL and the Secret token into Secret token.
3. Select the triggers used by your routes: Push events for commits, Tag push events for tags, Merge request events for merged requests, and Release events for releases. GitViber ignores unmerged merge requests.
4. Keep SSL verification enabled and add the webhook.
5. In GitViber, create a target and an enabled route for that project, with the desired events and branches.
6. Optionally, a GitLab administrator can add a system hook (Admin → System hooks) with this URL and secret instead of per-project webhooks.

GitLab sends events as they happen. GitViber checks its queue every 2 seconds and posts matching summaries automatically. A GitLab webhook test can also send a real summary if it matches an enabled route. Check delivery status under Workflows.

Manage users

Grant access using an existing FabricLab username.

Everyone with access can use all configured projects and routes. Removal takes effect on their next request. The mnantel owner account is protected.

Saved destinations can be used by multiple routes.