AI-native automation
Automate work across
GitHub and 
Microsoft 365with Caddi AI Agents.
Automate anything you do across GitHub, Microsoft 365, 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 GitHub and Microsoft 365
Connect GitHub to Caddi
Allow1Sign in to GitHub
One click with your own GitHub login. No API keys.
Connect Microsoft 365 to Caddi
Allow2Sign in to Microsoft 365
The same click again. Both tools are connected.
Send email in Microsoft 365 when new issue in GitHub.
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 GitHub and Microsoft 365 together
- 01
Send email in Microsoft 365 when new issue in GitHub.
Caddi watches GitHub for new issue and send email in Microsoft 365. No copy-paste, no missed records.
- 02
Create issue in GitHub when new email in outlook in Microsoft 365.
Caddi watches Microsoft 365 for new email in outlook and create issue in GitHub so the two systems stay in lockstep.
- 03
Create event in Microsoft 365 from GitHub events.
When pull request merged happens in GitHub, Caddi create event in Microsoft 365 with the right context attached.
Actions Caddi can take across GitHub and Microsoft 365
- 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.
- Microsoft 365
New email in Outlook
Triggers when a new email arrives in Outlook.
- Microsoft 365
New calendar event
Triggers when a new event is added to a calendar.
- Microsoft 365
New file in OneDrive
Triggers when a file is added to OneDrive.
- Microsoft 365
Send email
Send a new email from your Outlook account.
- Microsoft 365
Create event
Add a new event with attendees and reminders.
- Microsoft 365
Upload file to OneDrive
Add a file to a OneDrive folder.
- Microsoft 365
Create document in Word
Create a Word document with starter content.
Common questions
How does Caddi connect GitHub and Microsoft 365?
GitHub and Microsoft 365 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 GitHub and Microsoft 365 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 GitHub and Microsoft 365 to other tools too?
Yes. Most Caddi loops span 3–6 tools. Once the first GitHub + Microsoft 365 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 GitHub and Microsoft 365?
Drop your work email and we'll show you Caddi running end-to-end against GitHub, Microsoft 365, and the rest of your stack.
Or skip the demo: sign up free and build it yourself.