AI-native automation
Automate work across
Jump and 
PagerDutywith Caddi AI Agents.
Connect Jump and PagerDuty: Create incident in PagerDuty when meeting summary ready in Jump. 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 Jump and PagerDuty
Caddi AI Agents find the repetitive handoffs between Jump and PagerDuty, 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 Jump and PagerDuty together
At an RIA the work between Jump and PagerDuty 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
Create incident in PagerDuty when meeting summary ready in Jump.
Caddi watches Jump for meeting summary ready and create incident in PagerDuty. No copy-paste, no missed records.
- 02
Fetch meeting summary in Jump when incident triggered in PagerDuty.
Caddi watches PagerDuty for incident triggered and fetch meeting summary in Jump so the two systems stay in lockstep.
- 03
Add note in PagerDuty from Jump events.
When action item created happens in Jump, Caddi add note in PagerDuty with the right context attached.
Actions Caddi can take across Jump and PagerDuty
- 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.
- PagerDuty
Incident triggered
Triggers when a new incident opens.
- PagerDuty
Incident acknowledged
Triggers when a responder acknowledges.
- PagerDuty
Incident resolved
Triggers when an incident is resolved.
- PagerDuty
Create incident
Open an incident on a service.
- PagerDuty
Add note
Post a note to an incident timeline.
- PagerDuty
Resolve incident
Close an incident with a resolution.
Common questions
How does Caddi connect Jump and PagerDuty?
Jump and PagerDuty 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 Jump and PagerDuty 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 Jump and PagerDuty to other tools too?
Yes. Most Caddi loops span 3–6 tools. Once the first Jump + PagerDuty 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 Jump and PagerDuty 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 Jump and PagerDuty?
Drop your work email and we'll show you Caddi running end-to-end against Jump, PagerDuty, and the rest of your stack.
Or skip the demo: sign up free and build it yourself.