Connect GitLab

If your team uses GitLab, connect it here so Andy can read code and open merge requests. If your team uses GitHub, see Connect GitHub instead. You only need to connect one Git host.

GitLab setup is more involved than GitHub because GitLab needs a dedicated bot user account. Plan on 10–15 minutes. This is an admin-only step.

What you'll need

Before you start, have these on hand:

• Admin access to MeetAndy
• Admin access to your GitLab instance (or admin access to your group on GitLab.com)
• An email address you can use for a bot account (e.g., meetandyai@yourcompany.com)

Open the GitLab setup wizard

1. Open Company settings → Integrations from the sidebar.
2. Find the GitLab card and click Connect.

The setup is a 5-step wizard. Each step has copy buttons for values you need to paste into GitLab.

Step 1: Pick your GitLab type

Choose where your GitLab lives:

• GitLab.com — the hosted service at gitlab.com
• Self-hosted — your own GitLab instance. Enter the full URL (for example, https://gitlab.acme.com)

Click Next.

Step 2: Create the bot user

GitLab works best when MeetAndy connects as a dedicated bot user instead of a personal account. This avoids self-approval issues on merge requests and keeps the audit trail clean.

On GitLab.com:

1. Sign out of your personal GitLab account.
2. Go to gitlab.com/users/sign_up.
3. Create the account with:
   • Name: MeetAndyAI
   • Username: meetandyai
   • Email: meetandyai@yourcompany.com (or any address you control)
4. Verify the email and sign in as the bot.
5. Add the bot to the groups or projects you want Andy to access, with the Developer or Maintainer role.

On self-hosted GitLab:

1. Sign in as a GitLab admin.
2. Go to Admin Area → Users → New user and create the bot with the same name/username/email as above. You can use the Impersonate button later instead of setting a password.
3. Add the bot to the relevant groups/projects with Developer or Maintainer role.

Tick the confirmation checkbox in MeetAndy and click Next.

Step 3: Set up the webhook (optional)

Webhooks let Andy react to events like new merge requests in real time. You can skip this step and add webhooks later from integration settings.

The wizard shows two values:

• Webhook URL — copy this
• Secret token — copy this (it's only shown the first time; regenerate from MeetAndy if you lose it)

In GitLab:

1. Go to your group's Settings → Webhooks (or a project's webhooks settings).
2. Click Add new webhook.
3. Paste the URL and secret token.
4. Tick the trigger events: Push events, Issues events, Merge request events, Pipeline events, Comments.
5. Make sure Enable SSL verification is checked.
6. Click Add webhook.

Click Next in MeetAndy.

Step 4: Create the OAuth application

This is how MeetAndy authenticates as the bot user. The location differs slightly:

• GitLab.com: avatar menu → Edit profile → Applications
• Self-hosted: Admin Area → Applications

Create a new application with:

• Name: MeetAndyAI (copy from MeetAndy)
• Redirect URI: copy from MeetAndy
• Scopes: tick all five — api, read_api, read_user, read_repository, write_repository

GitLab shows the Application ID and Application Secret once. Copy both immediately — the secret cannot be retrieved later. Paste them into the MeetAndy wizard and click Next.

Step 5: Connect

The final step authorizes MeetAndy on behalf of the bot user.

1. Switch your GitLab session to the bot user.
2. Tick the confirmation checkbox.
3. Click Connect to GitLab. You'll be redirected to GitLab to authorize, then back to MeetAndy.
4. The success page shows the connected bot account. The GitLab card on Manage → Integrations now shows Connected.

Self-hosted: proxy / IP allowlist setup

If your self-hosted GitLab is behind a firewall, MeetAndy needs to come from a known IP. After connecting, you'll see an extra option on the GitLab card:

☐ GitLab instance requires IP allowlisting

Tick this box if your firewall blocks unknown IPs. Click Learn more for the full instructions. The short version:

1. Add this IP to your GitLab firewall / security group:

   34.223.170.213

2. Allow connections from that IP on port 443 (HTTPS).

3. Save and apply your firewall rules.

4. Back in MeetAndy, ask Andy to fetch something (e.g., @MeetAndy what's in the repo?) to test the connection.

When the box is ticked, all GitLab API calls from MeetAndy route through a dedicated proxy at this IP, so your firewall only needs to allow this one address.

Verify the connection

Back on Company settings → Integrations, the GitLab card shows Connected to: @meetandyai (or your bot's username). Click Test connection to confirm Andy can reach GitLab.

If the test connection fails on a self-hosted instance, the most common cause is the IP allowlist — double-check that 34.223.170.213 is allowed inbound.

What Andy uses GitLab for

Once connected, Andy can:

• Read code in your projects to answer questions and plan work
• Open and update merge requests when you hand off a task to the Coding Agent
• React to merge request and pipeline events (if you set up the webhook)

You'll choose which projects Andy follows on a per-Space basis when you configure each Space.

Disconnecting

To remove the GitLab integration:

1. Open Company settings → Integrations → GitLab in MeetAndy.
2. Click Disconnect. MeetAndy drops the connection.

The OAuth application and the bot user's group/project access remain in place on GitLab. If you want to fully remove MeetAndy's footprint, also:

• Delete the OAuth application (avatar menu → Edit profile → Applications, or Admin Area → Applications on self-hosted)
• Remove the bot user from the groups and projects you added it to, or delete the bot account if you only used it for MeetAndy

What's next

Connect Slack →