- Automations
- Adobe Sign + Harvey
AI-native automation
Connect Adobe Sign and Harvey 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 Adobe Sign and Harvey together
- 01
Redline document in Harvey when agreement completed in Adobe Sign.
Caddi watches Adobe Sign for agreement completed and redline document in Harvey — no copy-paste, no missed records.
- 02
Send agreement for signature in Adobe Sign when document ready in Harvey.
Caddi watches Harvey for document ready and send agreement for signature in Adobe Sign so the two systems stay in lockstep.
- 03
Summarize document in Harvey from Adobe Sign events.
When agreement sent happens in Adobe Sign, Caddi summarize document in Harvey 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 Adobe Sign and Harvey
Adobe SignAgreement completed
Triggers when all signers have completed an agreement.
Adobe SignAgreement sent
Triggers when an agreement is sent for signature.
Adobe SignAgreement declined
Triggers when a signer declines an agreement.
Adobe SignSend agreement for signature
Send a document or template out for e-signature.
Adobe SignUse template
Send an agreement built from a reusable widget or template.
Adobe SignDownload signed PDF
Download the executed PDF and certificate of completion.
Adobe SignSend reminder
Nudge signers who haven't completed yet.
HarveyDocument ready
Triggers when a document is queued for Harvey to process.
HarveyReview requested
Triggers when a redline or review is requested on a draft.
HarveyAnalysis complete
Triggers when Harvey finishes a summary, redline, or extraction.
HarveyRedline document
Send a draft to Harvey for AI redlining and markup.
HarveySummarize document
Generate a summary of a document or document set.
HarveyExtract clauses
Pull key clauses, terms, or issues from a document.
HarveyAnswer question
Run a research or document question against Harvey.
Common questions
How does Caddi connect Adobe Sign and Harvey?
Adobe Sign and Harvey 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 Adobe Sign and Harvey 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 Adobe Sign and Harvey to other tools too?
Yes. Most Caddi loops span 3–6 tools. Once the first Adobe Sign + Harvey 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 Adobe Sign and Harvey?
Drop your work email and we'll show you Caddi running end-to-end against Adobe Sign, Harvey, and the rest of your stack.




