365 emails, routed
by calendar date.
A date-aware 365-email ActiveCampaign automation and a Python Flask webhook connecting Stripe directly to the CRM.
The problem.
Daily Pearls is a membership whose emails refer to real calendar dates. A subscriber joining in May should enter at the appropriate point in the year, rather than receiving January’s first message.
Alongside that date logic, the payment-to-CRM connection needed attention, and the welcome and re-engagement sequences needed to work as part of the same system.
The system.
- PaymentStripe event
- ContactPython → CRM
- RouteJoin date + conditions
- DeliverCalendar-aligned email
What I changed.
Model the calendar inside the automation
I used a multi-automation architecture with Goals and If/Else branching in ActiveCampaign so members could enter the 365-email sequence according to their join date.
Replace the intermediary with owned code
A Python Flask webhook replaced the Zapier payment connection. Stripe events created and tagged ActiveCampaign contacts directly.
Maintain the surrounding experience
I rebuilt welcome and re-engagement sequences, added booking-triggered contact migration, and maintained newsletter formatting and calls to action.
The result.
The system connects membership payment, CRM tagging, and calendar-aware delivery. The client’s voice remains in the messages while the logic handles where each member should enter.
From the client.
Let’s take
a look.
Tell me what you’re trying to do, which tools you use, and where you’re getting stuck.
Book a conversation adedoyin.bakared@gmail.com