AI-native automation
Connect CASEpeer and Docusign with AI
Pick any two tools and Caddi runs the loop between them end-to-end — no complicated workflow builder, no IT ticket.
- Doesn't break. Caddi reads intent, so when fields move or UIs change, your loop keeps running.
- Screenshare to set up, chat to improve. Show Caddi once on a screenshare. Tweak it later by chat — no workflow builder to re-architect.
SOC 2 attested · Human-in-the-loop · Full audit trail · 70+ tools across legal, finance, and operations
Practical ways to use CASEpeer and Docusign together
- 01
Send envelope from template in Docusign when new case in CASEpeer.
Caddi watches CASEpeer for new case and send envelope from template in Docusign — no copy-paste, no missed records.
- 02
Create case in CASEpeer when envelope completed in Docusign.
Caddi watches Docusign for envelope completed and create case in CASEpeer so the two systems stay in lockstep.
- 03
Send envelope from document in Docusign from CASEpeer events.
When case stage changed happens in CASEpeer, Caddi send envelope from document in Docusign with the right context attached.
One continuous loop.
- 01Measure
Caddi watches how the work gets done today.
- 02Create
You screenshare it once. The loop ships.
- 03Improve
Caddi flags upgrades to existing loops and new automations to deploy.
Actions Caddi can take across CASEpeer and Docusign
- CASEpeer
New case
Triggers when a new case is created in CasePeer.
- CASEpeer
Case stage changed
Triggers when a case advances to a new stage.
- CASEpeer
New intake
Triggers when a new lead enters the intake pipeline.
- CASEpeer
Create case
Open a new CasePeer case with client, incident, and intake fields.
- CASEpeer
Create contact
Add a contact (client, witness, opposing party) to a case.
- CASEpeer
Add note
Log a timestamped note against a case.
- CASEpeer
Update case stage
Advance a case to the next stage with optional owner change.
- Docusign
Envelope completed
Triggers when all signers complete an envelope.
- Docusign
Envelope sent
Triggers when an envelope is sent for signature.
- Docusign
Recipient signed
Triggers when a single recipient completes signing.
- Docusign
Envelope declined
Triggers when a recipient declines an envelope.
- Docusign
Send envelope from template
Send a pre-built template out for signature with merged fields.
- Docusign
Send envelope from document
Send an arbitrary document out for signature.
- Docusign
Void envelope
Cancel an in-flight envelope with a reason.
- Docusign
Download signed PDF
Pull the executed PDF and certificate from a completed envelope.
- Docusign
Move envelope
Move a completed envelope to a specified folder.
Common questions
How does Caddi connect CASEpeer and Docusign?
CASEpeer and Docusign just run together. All it takes is showing us how you use them — one screenshare, no workflow builder to wire up. Caddi turns the demo into a verified loop and runs it against CASEpeer and Docusign end-to-end.
Do I need engineering help?
No. Whoever does the work today shows it once on a call. 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, but once the loop ships it runs deterministically — no model in the loop at runtime.
Can Caddi connect CASEpeer and Docusign to other tools too?
Yes. Most Caddi loops span 3–6 tools. Once the first CASEpeer + Docusign 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 the screenshare. The Caddi team reviews every loop before it runs in production.
Ready to automate CASEpeer and Docusign?
Drop your work email and we'll show you Caddi running end-to-end against CASEpeer, Docusign, and the rest of your stack.