AI-native automation
Automate work across
Docusign and 
Filevinewith Caddi AI Agents.
Automate anything you do across Docusign, Filevine, 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 Docusign and Filevine
Connect Docusign to Caddi
Allow1Sign in to Docusign
One click with your own Docusign login. No API keys.
Connect Filevine to Caddi
Allow2Sign in to Filevine
The same click again. Both tools are connected.
Create project in Filevine when envelope completed in Docusign.
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 Docusign and Filevine together
In a law firm the work between Docusign and Filevine is organized by matter: the right client, the right matter, the right people on it. Caddi carries that context through every step, so nothing is filed against the wrong case.
- 01
Create project in Filevine when envelope completed in Docusign.
Caddi watches Docusign for envelope completed and create project in Filevine. No copy-paste, no missed records.
- 02
Send envelope from template in Docusign when new project in Filevine.
Caddi watches Filevine for new project and send envelope from template in Docusign so the two systems stay in lockstep.
- 03
Create contact in Filevine from Docusign events.
When envelope sent happens in Docusign, Caddi create contact in Filevine with the right context attached.
Actions Caddi can take across Docusign and Filevine
- 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.
- Filevine
New project
Triggers when a new project (matter) is created.
- Filevine
Phase changed
Triggers when a project advances to a new phase.
- Filevine
New activity
Triggers when a note, task, or call is added.
- Filevine
Document uploaded
Triggers when a document is added to a project.
- Filevine
Create project
Open a new Filevine project with intake, contacts, and section data.
- Filevine
Create contact
Add a contact to a project with role and relationship data.
- Filevine
Upload document
Add a document to a project with optional metadata.
- Filevine
Create task
Schedule a follow-up task against a project or team member.
- Filevine
Add note
Append a timestamped note to a project's activity feed.
Common questions
How does Caddi connect Docusign and Filevine?
Docusign and Filevine 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 Docusign and Filevine 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 Docusign and Filevine to other tools too?
Yes. Most Caddi loops span 3–6 tools. Once the first Docusign + Filevine 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 law firms?
Yes. Caddi runs Docusign and Filevine with the matter as the unit of work, so documents, time, and communications land against the right client and matter rather than in a general folder. Firms most often start with intake, document filing, or billing prep.
Ready to automate Docusign and Filevine?
Drop your work email and we'll show you Caddi running end-to-end against Docusign, Filevine, and the rest of your stack.
Or skip the demo: sign up free and build it yourself.