Start free
Per-pair page

Connect GitLab to HubSpot in two minutes.

Real-time triggers from GitLab, ready-made actions in HubSpot. Filter, transform, and route without writing a line of code.

Connect GitLab to HubSpot — start free See reverse direction
Trigger app
GitLab as the trigger

Workflows fire when something happens in GitLab.

Action app
HubSpot as the action

Workflows do something in HubSpot, instantly.

See all 23 actions →
Connect GitLab to HubSpot — start free
Both directions

Pick the way that fits your stack.

Pair pages are mirrored. Each direction gets its own dedicated page.

GitLab → HubSpot

When something happens in GitLab, do it in HubSpot.

5 GitLab triggers wired to 23 HubSpot actions. Most-used pairing: GitLab Issue Created → Create Company.

HubSpot → GitLab

Or fire it the other way around.

18 HubSpot triggers wired to 10 GitLab actions downstream.

See HubSpot → GitLab →
Popular pairings

Common GitLab → HubSpot workflows.

Pick a pairing to set it up in two minutes. Each one is a fully editable recipe.

Showing 9 of 115 combinations
When gitlab issue created in GitLab, create company in HubSpot.

Fires when a new issue is created in a GitLab project. Payload includes title, description, labels, assignees. Useful for "auto-route to team channel based on labels" or "create cross-tracker copy" sync workflows.

When gitlab issue created in GitLab, create contact in HubSpot.

Fires when a new issue is created in a GitLab project. Payload includes title, description, labels, assignees. Useful for "auto-route to team channel based on labels" or "create cross-tracker copy" sync workflows.

When gitlab issue created in GitLab, create deal in HubSpot.

Fires when a new issue is created in a GitLab project. Payload includes title, description, labels, assignees. Useful for "auto-route to team channel based on labels" or "create cross-tracker copy" sync workflows.

When gitlab issue created in GitLab, create note in HubSpot.

Fires when a new issue is created in a GitLab project. Payload includes title, description, labels, assignees. Useful for "auto-route to team channel based on labels" or "create cross-tracker copy" sync workflows.

When gitlab merge request in GitLab, create company in HubSpot.

Fires on MR events — opened, updated, closed, merged. The hook for "auto-assign reviewer", "post to review channel", "trigger downstream CI" workflows.

When gitlab merge request in GitLab, create contact in HubSpot.

Fires on MR events — opened, updated, closed, merged. The hook for "auto-assign reviewer", "post to review channel", "trigger downstream CI" workflows.

When gitlab merge request in GitLab, create deal in HubSpot.

Fires on MR events — opened, updated, closed, merged. The hook for "auto-assign reviewer", "post to review channel", "trigger downstream CI" workflows.

When gitlab merge request in GitLab, create note in HubSpot.

Fires on MR events — opened, updated, closed, merged. The hook for "auto-assign reviewer", "post to review channel", "trigger downstream CI" workflows.

When gitlab pipeline completed in GitLab, create company in HubSpot.

Fires when a CI/CD pipeline completes with final status (passed, failed, canceled). For "post deploy result to engineering Slack" or "alert on consecutive failures" workflows.

How it works

Connect GitLab and HubSpot in five steps.

No code, no glue, no half-day setup. Each step is one click.

  1. 1
    Connect
    Authorize GitLab and HubSpot

    Open TinyCommand, authorize GitLab and HubSpot once each. Both connections are available to every workflow on your account.

  2. 2
    Trigger
    Pick a GitLab trigger

    Drop the GitLab → GitLab Issue Created trigger onto the canvas. TinyCommand auto-registers the webhook.

    POST /v1/webhooks/gitlab.trigger-issue-created
  3. 3
    Transform
    Add a filter or AI step

    Optionally add a Filter node ("subject contains URGENT") or an AI step ("classify intent") between trigger and action.

  4. 4
    Action
    Add the HubSpot action

    Drop the HubSpot → Create Company action below it. Map fields from the GitLab payload into the HubSpot inputs.

    hubspot.create-company
  5. 5
    Publish
    Publish and forget

    Hit Publish. TinyCommand runs it in production from second one. Watch the run-log fill up.

FAQ

Questions about GitLab + HubSpot.

How long does it take to connect GitLab and HubSpot on TinyCommand?
Under two minutes. Authorize GitLab and HubSpot once each, drop the GitLab trigger and HubSpot action onto a workflow canvas, map a couple of fields, and publish. No code, no glue.
Is the GitLab ↔ HubSpot integration real-time?
Yes. Both GitLab and HubSpot expose webhooks, so events from one fire workflows in the other within seconds rather than on a polling interval.
Can I filter or transform data between GitLab and HubSpot?
Yes. Add a Filter node to only pass through matching events, a Switch node to branch by value, or an AI / Code node to transform payloads before they hit HubSpot.
What GitLab events can trigger a HubSpot workflow?
Any of the 5 GitLab triggers, including "GitLab Issue Created". Each fires in real time when the matching event happens in GitLab.
Do I need a paid plan to use GitLab with HubSpot?
No. Both integrations come on every plan, including Free, which includes 1,000 credits a month with no credit card. Each workflow step uses 1 credit, and paid plans include more credits and team seats when you need them.
What if I want HubSpot → GitLab instead?
Build it the same way, in reverse. There's a dedicated /integrations/hubspot/with/gitlab page with the reverse-direction triggers and actions.
Related

Other apps that pair well with GitLab.

+
GitLab + Gmail
Email
+
GitLab + Slack
Communication
+
GitLab + Google Sheets
Spreadsheets & Databases
+
GitLab + Stripe
Payments
+
GitLab + Notion
Productivity
+
GitLab + Airtable
Spreadsheets & Databases
Connect GitLab to HubSpot — start free