GitHub + Mailchimp: release-driven email campaigns.
Trigger Mailchimp campaigns from GitHub releases, send release notes to your subscriber list, or update Mailchimp tags based on customer GitHub activity (open-source projects).
Workflows fire when something happens in GitHub.
- New GitHub EventWebhook
Workflows do something in Mailchimp, instantly.
- Add List MemberAPI
- Create CampaignAPI
- Create TagAPI
- Delete CampaignAPI
- Permanently Delete MemberAPI
- Delete TagAPI
Pick the way that fits your stack.
Pair pages are mirrored. Each direction gets its own dedicated page.
When something happens in GitHub, do it in Mailchimp.
1 GitHub triggers wired to 16 Mailchimp actions. Most-used pairing: New GitHub Event → Add List Member.
Or fire it the other way around.
5 Mailchimp triggers wired to 23 GitHub actions downstream.
See Mailchimp → GitHub →Common GitHub → Mailchimp workflows.
Pick a pairing to set it up in two minutes. Each one is a fully editable recipe.
Fires when the selected events occur on a GitHub repository. One webhook is registered per workflow on the chosen repo, with the events list filtered server-side by GitHub. Pick from push, pull_request, issues, release, deployment, and many others.
Fires when the selected events occur on a GitHub repository. One webhook is registered per workflow on the chosen repo, with the events list filtered server-side by GitHub. Pick from push, pull_request, issues, release, deployment, and many others.
Fires when the selected events occur on a GitHub repository. One webhook is registered per workflow on the chosen repo, with the events list filtered server-side by GitHub. Pick from push, pull_request, issues, release, deployment, and many others.
Fires when the selected events occur on a GitHub repository. One webhook is registered per workflow on the chosen repo, with the events list filtered server-side by GitHub. Pick from push, pull_request, issues, release, deployment, and many others.
Connect GitHub and Mailchimp in five steps.
No code, no glue, no half-day setup. Each step is one click.
- 1ConnectAuthorize GitHub and Mailchimp
Open Tiny Command, authorize GitHub and Mailchimp once each. Both connections are available to every workflow on your account.
- 2TriggerPick a GitHub trigger
Drop the GitHub → New GitHub Event trigger onto the canvas. Tiny Command auto-registers the webhook.
POST /v1/webhooks/github.trigger-event - 3TransformAdd a filter or AI step
Optionally add a Filter node ("subject contains URGENT") or an AI step ("classify intent") between trigger and action.
- 4ActionAdd the Mailchimp action
Drop the Mailchimp → Add List Member action below it. Map fields from the GitHub payload into the Mailchimp inputs.
mailchimp.add-list-member - 5PublishPublish and forget
Hit Publish. Tiny Command runs it in production from second one. Watch the run-log fill up.
Questions about GitHub + Mailchimp.
How do I send a Mailchimp release announcement on every GitHub release?
Can I gate the Mailchimp send on a release tag?
How do I track GitHub user activity for Mailchimp segmentation?
Can I include GitHub contributor credits in the Mailchimp email?
How do I avoid spamming Mailchimp on every minor GitHub event?
Can I A/B test release announcement subject lines?
Other apps that pair well with GitHub.
Wire GitHub to Mailchimp in 2 minutes.
Free tier available. No credit card. No onboarding call.
