AI-native automation
Automate work across
Adobe Sign and 
GitHubwith Caddi AI Agents.
Automate anything you do across Adobe Sign, GitHub, 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 Adobe Sign and GitHub
Connect Adobe Sign to Caddi
Allow1Sign in to Adobe Sign
One click with your own Adobe Sign login. No API keys.
Connect GitHub to Caddi
Allow2Sign in to GitHub
The same click again. Both tools are connected.
Create issue in GitHub when agreement completed in Adobe Sign.
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 Adobe Sign and GitHub together
- 01
Create issue in GitHub when agreement completed in Adobe Sign.
Caddi watches Adobe Sign for agreement completed and create issue in GitHub. No copy-paste, no missed records.
- 02
Send agreement for signature in Adobe Sign when new issue in GitHub.
Caddi watches GitHub for new issue and send agreement for signature in Adobe Sign so the two systems stay in lockstep.
- 03
Comment on issue in GitHub from Adobe Sign events.
When agreement sent happens in Adobe Sign, Caddi comment on issue in GitHub with the right context attached.
Actions Caddi can take across Adobe Sign and GitHub
- Adobe Sign
Agreement completed
Triggers when all signers have completed an agreement.
- Adobe Sign
Agreement sent
Triggers when an agreement is sent for signature.
- Adobe Sign
Agreement declined
Triggers when a signer declines an agreement.
- Adobe Sign
Send agreement for signature
Send a document or template out for e-signature.
- Adobe Sign
Use template
Send an agreement built from a reusable widget or template.
- Adobe Sign
Download signed PDF
Download the executed PDF and certificate of completion.
- Adobe Sign
Send reminder
Nudge signers who haven't completed yet.
- GitHub
New issue
Triggers when an issue is opened in a repository.
- GitHub
Pull request merged
Triggers when a pull request is merged.
- GitHub
New release
Triggers when a release is published.
- GitHub
Create issue
Open an issue with labels and assignees.
- GitHub
Comment on issue
Add a comment to an issue or pull request.
- GitHub
Update labels
Add or remove labels on an issue.
Common questions
How does Caddi connect Adobe Sign and GitHub?
Adobe Sign and GitHub 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 Adobe Sign and GitHub 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 Adobe Sign and GitHub to other tools too?
Yes. Most Caddi loops span 3–6 tools. Once the first Adobe Sign + GitHub 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.
Ready to automate Adobe Sign and GitHub?
Drop your work email and we'll show you Caddi running end-to-end against Adobe Sign, GitHub, and the rest of your stack.
Or skip the demo: sign up free and build it yourself.