Integration · Code

Ovenbird for GitLab

Merge requests, pipelines and issues in GitLab. Ovenbird follows your release and change processes across them and tells the engineer the next step.

Start free · 14 days, no card Ask for early access

In development · designed as described here, not yet connected. Ask for early access; everything else on this page works today with your documents.

GitLabCode

MR !884 has one approval. What's next?

Ovenbird reads the record, its history and the thread around it, then applies your document.

Asks firstDoes this touch payment code (two approvals required)?Has the pipeline passed on the release branch?

NextRequest the second approval from the payments owner and wait for the release-branch pipeline; record the QA evidence on the issue.

📘 From your process

The step comes from your own document, quoted.

Why teams connect it

Merge requests as release evidenceApprovals, pipelines and target branch read with the issue.
Rules from your documentTwo approvals for payment code, pipeline green on the release branch: as next steps.
Read onlyMerges stay with the team.

What flows, and what doesn't

GitLabThe record and its history

Reads

OvenbirdYour process, applied

Nothing

GitLabNever written to

What it reads

Merge requests: state, approvals, pipelines, linked issues, labels
Discussions and the MR activity
Issues and epics used for releases and changes
Commits and target branches

What it writes

Nothing. Merges and approvals stay with the team

Processes teams run on it

How it connects

Designed, not yet connectedOAuth (GitLab application) with read access to the projects you choose.
Least accessRead scopes for the objects you choose; write access limited to one note or comment, or none.
Per workspace, encryptedEach workspace connects its own account. Credentials are encrypted with a separate key and never shared between workspaces.

Questions buyers ask

Does it write to customers or change records?

No. It writes nothing at all. Statuses, replies and approvals stay with your team in GitLab.

What does it need access to?

OAuth (GitLab application) with read access to the projects you choose. Each workspace connects its own account; nothing is shared between workspaces, and credentials are stored encrypted.

Does it work before the integration is connected?

Yes. Paste a link to a process document and describe the situation; the next step and the course exist the same minute. The integration adds the record's own history as evidence.

See it on one of your own documents

Paste a link to a procedure. The next step and the course exist the same minute; connect GitLab when you are ready.

Start free · 14 days, no card Ask for early access

All integrations · How to create a process