AI-native automation
Automate work across
GitLab and 
Microsoft Teamswith Caddi AI Agents.
Automate anything you do across GitLab, Microsoft Teams, and the rest of your tools. Sign in, show or tell Caddi what you want, and it runs end to end. No workflow builder.
How to connect GitLab and Microsoft Teams
Connect GitLab to Caddi
Allow1Sign in to GitLab
One click with your own GitLab login. No API keys.
Connect Microsoft Teams to Caddi
Allow2Sign in to Microsoft Teams
The same click again. Both tools are connected.
Send channel message in Microsoft Teams when new issue in GitLab.
ScreenshareType it3Show or tell it
Screenshare the job, or type it in chat. Change it any time.
- Running
14 done1 for review
4Watch it run
Caddi does the work and flags anything unsure for review.
What Caddi is and how it works
An AI teammate that runs your back-office loops.
- Doesn't break. Caddi reads intent, so when fields move or UIs change, your loop keeps running.
- Taught like a new hire. Walk Caddi through the work once. Tweak it later by chat, with no workflow builder to re-architect.
SOC 2 attested · Human-in-the-loop · Full audit trail · 150+ tools across legal, finance, and operations
Practical ways to use GitLab and Microsoft Teams together
- 01
Send channel message in Microsoft Teams when new issue in GitLab.
Caddi watches GitLab for new issue and send channel message in Microsoft Teams. No copy-paste, no missed records.
- 02
Create issue in GitLab when new channel message in Microsoft Teams.
Caddi watches Microsoft Teams for new channel message and create issue in GitLab so the two systems stay in lockstep.
- 03
Send chat message in Microsoft Teams from GitLab events.
When merge request merged happens in GitLab, Caddi send chat message in Microsoft Teams with the right context attached.
Actions Caddi can take across GitLab and Microsoft Teams
- GitLab
New issue
Triggers when an issue is opened in a project.
- GitLab
Merge request merged
Triggers when a merge request is merged.
- GitLab
Pipeline finished
Triggers when a CI pipeline succeeds or fails.
- GitLab
Create issue
Open an issue with labels and assignee.
- GitLab
Comment
Add a note to an issue or merge request.
- GitLab
Update issue
Change labels, milestone or state.
- Microsoft Teams
New channel message
Triggers when a new message is posted to a channel.
- Microsoft Teams
New chat message
Triggers when a new direct or group chat arrives.
- Microsoft Teams
Send channel message
Post a message to a Teams channel.
- Microsoft Teams
Send chat message
Send a direct or group chat message.
- Microsoft Teams
Create channel
Spin up a new channel within a team.
Common questions
How does Caddi connect GitLab and Microsoft Teams?
GitLab and Microsoft Teams just run together. You teach Caddi the way you'd teach a new hire: walk it through how you use them today, with no workflow builder to wire up. Caddi turns that walkthrough into a verified loop and runs it against GitLab and Microsoft Teams end-to-end.
Do I need engineering help?
No. Whoever does the work today walks Caddi through it on a call, the same way they'd train a new hire. Caddi builds the loop. No code, no IT ticket.
Is my data safe?
Yes. Caddi is SOC 2 attested. The AI watches and builds the automation, and once the loop ships it runs as deterministic code, repeatable and logged, with any model step scoped and reviewable.
Can Caddi connect GitLab and Microsoft Teams to other tools too?
Yes. Most Caddi loops span 3–6 tools. Once the first GitLab + Microsoft Teams loop is live, Caddi suggests other tools and other workflows to fold in.
How fast can it go live?
Typical first loops ship within a week of that first walkthrough. The Caddi team reviews every loop before it runs in production.
Ready to automate GitLab and Microsoft Teams?
Drop your work email and we'll show you Caddi running end-to-end against GitLab, Microsoft Teams, and the rest of your stack.
Or skip the demo: sign up free and build it yourself.