AI-native automation
Automate work across
GitLab and 
Jumpwith Caddi AI Agents.
Connect GitLab and Jump: Fetch meeting summary in Jump when new issue in GitLab. Teach Caddi the job once, the way you'd train someone new, and it runs end to end. No workflow builder.
Discover, automate and govern the work between GitLab and Jump
Caddi AI Agents find the repetitive handoffs between GitLab and Jump, learn them the way a new hire would, and run them for you, with every run on the record. No workflow builder, no code.
Discover repetitive work
across all your tools.
Train an AI agent to do the work
over a video call.
Search mailMatters / Whitmore HoldingsGovern every AI agent,
every decision.
Discover repetitive work
across all your tools.
Train an AI agent to do the work
over a video call.
Search mailMatters / Whitmore HoldingsGovern every AI agent,
every decision.
Discover repetitive work
across all your tools.
Train an AI agent to do the work
over a video call.
Search mailMatters / Whitmore HoldingsGovern every AI agent,
every decision.
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 Jump together
At an RIA the work between GitLab and Jump is organized by household: the right client, the right accounts, the right advisor. Caddi carries that context through every step, so records stay tied to the household they belong to.
- 01
Fetch meeting summary in Jump when new issue in GitLab.
Caddi watches GitLab for new issue and fetch meeting summary in Jump. No copy-paste, no missed records.
- 02
Create issue in GitLab when meeting summary ready in Jump.
Caddi watches Jump for meeting summary ready and create issue in GitLab so the two systems stay in lockstep.
- 03
Draft follow-up email in Jump from GitLab events.
When merge request merged happens in GitLab, Caddi draft follow-up email in Jump with the right context attached.
Actions Caddi can take across GitLab and Jump
- 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.
- Jump
Meeting summary ready
Triggers when Jump finishes a meeting summary.
- Jump
Action item created
Triggers when Jump captures a follow-up task.
- Jump
Client fact captured
Triggers when Jump records a new or changed client detail.
- Jump
Fetch meeting summary
Pull the summary, tasks and data points for a meeting.
- Jump
Draft follow-up email
Draft the client recap from the action items.
- Jump
Sync to CRM
Push notes and facts to the connected CRM record.
Common questions
How does Caddi connect GitLab and Jump?
GitLab and Jump 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 Jump 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 Jump to other tools too?
Yes. Most Caddi loops span 3–6 tools. Once the first GitLab + Jump 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.
Does this work for RIAs and financial advisors?
Yes. Caddi runs GitLab and Jump with the household as the unit of work, so plans, accounts, and activity stay tied to the right client and advisor. Firms most often start with onboarding, account maintenance, or reporting prep.
Ready to automate GitLab and Jump?
Drop your work email and we'll show you Caddi running end-to-end against GitLab, Jump, and the rest of your stack.
Or skip the demo: sign up free and build it yourself.