AI-native automation
Automate work across
GitHub and 
Klaviyowith Caddi AI Agents.
Automate anything you do across GitHub, Klaviyo, 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 Klaviyo
Connect GitHub to Caddi
Allow1Sign in to GitHub
One click with your own GitHub login. No API keys.
Connect Klaviyo to Caddi
Allow2Sign in to Klaviyo
The same click again. Both tools are connected.
Create or update profile in Klaviyo 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 Klaviyo together
- 01
Create or update profile in Klaviyo when new issue in GitHub.
Caddi watches GitHub for new issue and create or update profile in Klaviyo. No copy-paste, no missed records.
- 02
Create issue in GitHub when profile created in Klaviyo.
Caddi watches Klaviyo for profile created and create issue in GitHub so the two systems stay in lockstep.
- 03
Add to list in Klaviyo from GitHub events.
When pull request merged happens in GitHub, Caddi add to list in Klaviyo with the right context attached.
Actions Caddi can take across GitHub and Klaviyo
- 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.
- Klaviyo
Profile created
Triggers when a new profile is added.
- Klaviyo
Added to list
Triggers when a profile joins a list.
- Klaviyo
Campaign sent
Triggers when a campaign goes out.
- Klaviyo
Create or update profile
Upsert a profile with properties.
- Klaviyo
Add to list
Subscribe a profile to a list.
- Klaviyo
Track event
Record a custom event on a profile.
Common questions
How does Caddi connect GitHub and Klaviyo?
GitHub and Klaviyo 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 Klaviyo 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 Klaviyo to other tools too?
Yes. Most Caddi loops span 3–6 tools. Once the first GitHub + Klaviyo 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 Klaviyo?
Drop your work email and we'll show you Caddi running end-to-end against GitHub, Klaviyo, and the rest of your stack.
Or skip the demo: sign up free and build it yourself.