Palfred + GitLab.
Check merge request status, monitor CI/CD pipelines, and manage issues from any Slack channel — no tab switching required.
@Palfred any open MRs on the billing-service repo?
4 open merge requests:
!317 has 2 approvals but needs 1 more before merge. Want me to request a review?
Yeah, ping @sofia for the final review
Done ✓ Requested review from @sofia on !317
🔴 Pipeline #48291 failed on billing-service/main
@Palfred show me the failure details
Looks like the new retry logic is causing a timeout in the integration tests. Want me to retry the pipeline or notify the committer?
Notify the committer, this needs a fix first
@Palfred create a GitLab issue for the auth-service — users are reporting slow login on mobile
Created ✓ Assigned to the auth-service maintainers
Great, link it in #mobile-bugs too
Why connect GitLab to Palfred?
GitLab combines source control, CI/CD, and project management in a single platform. That breadth is powerful, but it also means your team has a lot of information spread across merge requests, pipelines, issues, and epics. When the conversation about what to build next happens in Slack, Palfred brings the GitLab data your team needs right into the discussion.
With the Palfred GitLab integration, developers can check the status of any merge request, see pipeline results, and get a summary of open issues assigned to them — all from a quick Slack message. When someone reports a bug in a channel, Palfred can create a GitLab issue with the thread context, assign it to the right person, and set the appropriate labels. Pipeline failures surface in Slack instantly, so nobody wastes time waiting for a build they don't know has already failed.
Teams that run their entire DevOps lifecycle in GitLab benefit most from this integration because it keeps the feedback loop tight. Engineering leads can ask for weekly merge activity, blocked pipelines, or upcoming milestone progress without logging into GitLab. The result is fewer meetings, faster decisions, and an engineering team that stays in flow.
What you can do.
One minute. That's it.
No onboarding calls. No configuration wizards. Just install and go.
Add to Slack
One click install. Palfred joins your workspace in under a minute.
Connect GitLab
Authorize GitLab in the Palfred settings. One click.
Just ask
Mention @Palfred in any channel and ask about your GitLab data.
Works great with.
FAQ: Palfred + GitLab
What GitLab permissions does Palfred need?
Palfred needs read access to projects, merge requests, and issues through a personal access token or OAuth. Write access is only required if you want to create issues or comment on merge requests from Slack.
Does Palfred work with self-hosted GitLab?
Yes. Palfred supports both GitLab.com and self-managed GitLab instances. Enter your instance URL during setup and Palfred connects through the GitLab API.
Can I get merge request updates in Slack?
Yes. Ask Palfred about any merge request by name or number and it returns the current status, reviewers, CI pipeline results, and recent comments.
Does Palfred have access to my source code?
No. Palfred reads metadata such as merge request titles, issue descriptions, and pipeline statuses. It does not clone repositories or store any source code.
Pay for what you use.
No per-seat pricing. One workspace, one bill.
Free
5,000 credits (~100 conversations)
Includes:
- AI assistant that works right in your Slack threads
- References your team's context in channels it's added to
- Connects to the tools you already use (Jira, GitHub, and more)
- Automates recurring work like reports and check-ins
- Drafts updates, tickets, and docs on your behalf
Team
Most popularper Slack workspace
Everything in Free, plus:
- Monthly credits refresh automatically
- Higher capacity for heavier workflows + more scheduled automation
- Priority support
Enterprise
For organizations with specific needs
Everything in Team, plus:
- SSO & SAML
- Dedicated account manager
- Custom SLA
- Audit logs