Integrations: GitLab, Slack and Claude Code

Help Centre
← All topics
Getting Started 3
KAMI for administrators KAMI for employees KAMI for managers
Employee Essentials 11
Checking in and out Correcting attendance: amendment requests My Learning: taking a course Performance for employees Requesting and amending leave Requesting and liquidating an advance Submitting an expense claim Tracking your performance Understanding your payslip Your employee profile Your loans and advances
My Team 40
Approving requests in My Team Guided walkthroughs Mel, your My Team AI assistant My Team for administrators My Team for managers The Team page: finding and working with employees
Employee Lifecycle 3
Adding and onboarding employees Deactivating, terminating and rehiring employees Logging and managing disciplinary actions
Tools 5
Bulk Documents Bulk data import and export Bulk-editing employees with Profile Manager Importing career progression data Policy Center
Reports 9
Audit Trail report Biometrics report and device settings Demographics report Disciplinary Actions report Invites & Activation report Key Dates report Missing Data report Team Insights Report Turnover report
Settings 17
Announcements Custom Policies Custom fields Discipline Types Document Templates Module activation and two-factor authentication Notification settings Onboarding Wizard Profile Automations
Approvals & Access 5
Approval chains and the approval matrix Bulk Assignments Profile Automations User rights and access control Workflow Automation
Organization 3
Company and subsidiary details Cost centres Setting up your organisation structure
Attendance 28
Getting started with Attendance The Attendance dashboard
Daily Attendance 8
Approving attendance and leave requests Checkpoints and geo-tracking Events: the attendance record How timekeeping is calculated KAMI ClockSmart Offline and remote check-ins Time logs Timesheet
Scheduling 5
Event templates Open shifts Shifts Standard and dynamic schedules The team calendar
Reports 3
Attendance reports Event tracker Leave balances and accrual
Settings 10
Activities and how they pay Attendance settings on an employee profile Attendance user rights Attendance validation rules Calendar rules and the attendance lock Emergency leave allowance and leave cycles Holiday rules Importing leave data Leave conversion and encashment Leave types and policies
Payroll 38
Daily-paid, monthly-paid and hourly-paid employees Getting started with Payroll How wages are calculated The payroll dashboard
Payments & Adjustments 10
13th month pay Bulk bonuses and bonus tax Final pay on termination Gross-up and nett tax Importing historical payslips Manual tax adjustments Other payments: allowances, bonuses and deductions Payroll bulk imports Payroll payment and disbursement Retroactive payments
Reports 5
Monthly tax and contribution reports Payroll reports Scheduling payroll reports The accounting journal Year-end payroll reports
Running Payroll 5
Calculating a single payslip Payslip tax details explained Prorated pay for joiners and leavers Running a payroll batch cycle Viewing and validating payslips
Settings 14
Batch cycles Contribution types Custom payroll policies Employee payroll settings Income tax types Non-taxable groups Number precision Other payment types and groups Payment settings Payroll automation rules Payroll user rights Payroll validation rules Termination settings Updating statutory contribution rates
Benefits 11
Benefit reports Getting started with Benefits
Advance Wages 2
KAMI QuickPay: advance wages Repaying advances
Loans 5
Disbursing loans Importing loan data Loan instalments and repayment Managing team loans Restructuring a loan
Settings 2
Benefits user rights Loan types
Expenses 10
Expense reports Getting started with Expenses The expense dashboard
Advances 2
Advance approvers Managing advances
Claims 2
Managing and approving expense claims Reimbursement and payment
Settings 3
Approved vendors Expense types: limits, receipts and rules Expense user rights
Invoicing 11
Getting started with Invoicing
Clients & Templates 4
Invoice fee components Invoice templates Invoicing clients Picking and skipping rules
Invoices 3
Creating and processing invoices Payments, deposits and transactions Reviewing, approving and issuing invoices
Settings 3
Currencies and FX rates Invoice numbering Invoicing user rights
Performance 17
Getting started with Performance Performance for administrators Performance for managers Performance scores and the talent grid Score cards: how the overall rating is built The analysis view: talent grid, placements and gaps The performance dashboard
Assessments 3
Creating an assessment cycle How assessment scores are calculated Reviewing team assessments
Goals 3
Creating a goal cycle Goals and KPIs: how progress is calculated Reviewing and tracking team goals
Settings 2
Performance user rights Recurring cycles and automations
Skills & Feedback 2
Giving and receiving feedback Skills and endorsements
Learning 6
Getting started with the LMS
Building Content 3
Building learning paths and courses Generating a learning path with AI Module content and assessments
Managing Learning 2
Enrolling learners and tracking progress LMS certificates
Tasks 21
Getting started with KAMI Tasks KAMI PM, your AI project manager My Work: your daily view Notifications in KAMI Tasks
Tickets 4
Creating and editing tickets Epics, subtasks and linked tickets Estimates and logging time Statuses, priorities and ticket types
Planning 5
List and Timeline views Projects and access Sprints The Kanban board Ticket templates
Reports 2
Sprint Insights Timelog
Settings 6
Activating Task users Automations Importing tickets from a spreadsheet Integrations: GitLab, Slack and Claude Code Ticket Standards Users and groups

Integrations: GitLab, Slack and Claude Code

Integrations connect KAMI Tasks with your development tools so tickets stay in sync automatically — code activity lands on tickets, ticket activity lands in Slack, and an AI assistant can work your backlog from the terminal.

Where: Settings › Integrations You need: project admin rights, plus admin access in the tool being connected

What each one gives you

IntegrationWhat it doesWho sets it up
GitLabBranches, MRs and pipeline status appear on the ticketA GitLab project admin
SlackTicket activity posts into channelsA Slack workspace admin
Claude CodeAn AI assistant reads and writes tickets from the terminalEach developer, individually

GitHub appears on this page marked coming soon.

GitLab — link merge requests to tickets

Connect GitLab and every ticket grows a Merge Requests panel: the branches and MRs for that ticket, with live pipeline status. Reviewers stop asking "where's the code for this?" — it is on the ticket.

Setup: in GitLab, open your project's Settings → Webhooks, add the webhook URL shown on the integrations page, paste the secret token into GitLab's Secret token field, and enable merge request events and pipeline events.

⚠️ The one convention that makes it work: branch names must start with the ticket key — KDV-123-anything-after. That prefix is how an MR finds its ticket. A branch named fix-emails links to nothing, silently — no error, just an empty panel. Make it a team habit, not a suggestion.

Slack — ticket activity where the team talks

Connect a Slack app's Bot User OAuth Token (from the app's OAuth & Permissions page, after installing it to the workspace), set a default channel, and save. Then:

  • Project channels — route each project's activity to its own channel; the default catches projects without one
  • Triggers — choose what gets posted and when
  • Send test message — confirm the wiring before trusting it

Be sparing with triggers. A channel that posts every ticket change is muted within a week, and then it is worse than not having it.

AI assistants — Claude Code

This connects Claude Code, Anthropic's AI coding assistant, to your KAMI Tasks account so it can read and write tickets from the terminal. The setup page walks through it: install Claude Code, run the install command, generate your personal API token, and add the config file to your project.

What you get once connected:

  • Create tickets from a brief — describe a feature and it becomes a properly-formed ticket
  • Handover specs posted automatically — dev handover docs and HTML designs posted as ticket comments
  • MR links posted back — when an MR is opened, the branch and link land on the ticket

The API token is personal. Claude acts as you, and its ticket activity is attributed to you — so treat the token like your password, and do not share one between people.

What Happens Next

  • GitLab: MRs and pipelines appear on tickets within moments of the webhook firing. Existing branches are not backfilled — linking starts from setup.
  • Slack: posts begin on the next matching event. Nothing historical is posted.
  • Claude Code: tickets it creates or comments on appear immediately, under your name.

Tips

  • Test the webhook before announcing it. GitLab shows recent deliveries and their responses; a misconfigured secret token fails quietly.
  • Agree the branch convention in writing the same day you connect GitLab. Retrofitting it means a period where some tickets link and others do not, and nobody trusts the panel.
  • One Slack channel per project, not one for everything. A single firehose channel gets muted; per-project channels stay readable.
  • Review who holds Claude Code tokens when someone leaves — the token acts as them.

Troubleshooting / FAQ

Q: No merge requests are appearing on any ticket. Check the webhook in GitLab: is it delivering, and are merge request and pipeline events enabled? Then check the secret token matches.

Q: MRs appear for some tickets but not others. Branch naming. Only branches starting with the ticket key link.

Q: Slack posts stopped. The bot token may have been revoked, or the app removed from the workspace. Use Send test message to confirm.

Related articles

Related articles

Activating Task users

Being in KAMI does not put someone in KAMI Tasks. Task access is granted separately, in your main KAMI account — which is why the KAMI Tasks Users page is read-only and why new joiners so often…

Read article →

Automations

Automations are the rules that chase things so a person does not have to: a ticket goes blocked and someone is told, a critical ticket sits unassigned and someone is told, a sprint's velocity drops…

Read article →

Importing tickets from a spreadsheet

Moving to KAMI Tasks from another tool — or from a planning spreadsheet — does not mean retyping the backlog. The import takes a spreadsheet and turns its rows into tickets.

Read article →