Connect First AI Employee to GitLab.

Tasks1 routeRoute facts checked August 28, 2026

This page shows every cataloged route for this app and marks the most capable working path. The recommended route works through automation you configure and own.

You authorize and keep control of the provider account. No page view means an account is connected.

Recommended route

Downloadable n8n Cloud workflow starter

A completed call runs Create issue in GitLab after you configure and enable the destination node. This route receives completed calls only. The synthetic dashboard test stops before the destination, so it proves transport but not the provider write. Event-ID replay memory is bounded best effort, and one n8n webhook URL is stored per tenant.

Every available route

More than one route is shown when it adds a real capability or gives you a customer-owned alternative. Recommended means most capable today, not already connected.

n8n Cloud

Downloadable n8n Cloud workflow starter

Customer setup required

Recommended route

What it does

A completed call runs Create issue in GitLab after you configure and enable the destination node.

Before you start

Personal access token or OAuth2. Authorize GitLab and choose the project namespace and repository that receives follow-up issues.

What it does not do

This route receives completed calls only. The synthetic dashboard test stops before the destination, so it proves transport but not the provider write. Event-ID replay memory is bounded best effort, and one n8n webhook URL is stored per tenant.

Set it up

Download the app-specific starter from Integrations in your First AI Employee dashboard and import it into n8n Cloud.
Authorize GitLab, choose the customer-owned resource, and complete this requirement: Authorize GitLab and choose the project namespace and repository that receives follow-up issues.
Configure and enable the destination node, then activate the workflow.
Copy the production /webhook/ URL into the dashboard automation connection. Test URLs and self-hosted n8n hosts are rejected.
Send the dashboard transport test, then run a real non-production completed call and confirm the destination record yourself.

Provider documentation

Set it up: Downloadable n8n Cloud workflow starter

Personal access token or OAuth2. Authorize GitLab and choose the project namespace and repository that receives follow-up issues.

Download the app-specific starter from Integrations in your First AI Employee dashboard and import it into n8n Cloud.

Authorize GitLab, choose the customer-owned resource, and complete this requirement: Authorize GitLab and choose the project namespace and repository that receives follow-up issues.

Configure and enable the destination node, then activate the workflow.

Copy the production /webhook/ URL into the dashboard automation connection. Test URLs and self-hosted n8n hosts are rejected.

Send the dashboard transport test, then run a real non-production completed call and confirm the destination record yourself.

Verify the complete result

After the transport test succeeds, complete a non-production call and verify Create issue happened once in GitLab.

Account ownership and data boundaries

The route sends only the event fields needed for the action you configure. Provider credentials stay in the approved connection or are sealed by First AI Employee where the guide explicitly says so.

Your provider and automation accounts remain yours.
A successful transport test is not the same as a verified provider write.
The pages never claim a native or two-way sync unless that exact capability exists.

Ready to connect it?

Use the dashboard to authorize your account, select the customer-owned destination, and test the complete downstream result.

Open Integrations in your dashboard Browse all app guides