Inspiration
I truly believe in a single source of truth environment Coda documents can offer. With packs that becomes a reality. Mailchimp is one of the big players in email marketing and should be another piece companies can add to their single source of truth.
What it does
The Mailchimp pack lets you
- manage your audience including member subscriptions, updates, ...
- create and manage campaigns
- send Coda doc pages as mails and much more...
How I built it
I started with a lite pack to get used to the API at first (it is available for free). I used the CLI as I already knew it will be a bigger pack and I prefer multiple files.
Challenges I ran into
Mailchimp requires to set an endpoint depending on the serverlocation of the account. So I've had to add a postsetup function, switch to oAuth and workaround some bugs to make this easy for the user.
The biggest challenge in solo-dev is decision making though. I often had to change parameter orders or naming later on because I realized it is better the other way around when finally testing/using the pack.
Accomplishments that I'm proud of
I used almost every aspect packs can offer, from dynamic sync tables, two way sync, varargs, table references, post setup, error handling to all available building blocks. As a hobby dev, I'm quite proud that I was able to do that.
What I learned
I learned so much, I don't know where to start at. But what I always remember is something Eric said about the functionality of packs. They should necessarily be a 1:1 wrapper for an API, but help the user to accomplish things. I tried to add buttons and features that fulfill that idea at least a bit.
What's next for Mailchimp Pack
At first, there is some time off :D After that, I'm thinking of implementing segment management. This is a bit clumsy in the Mailchimp UI, so it could be a cool addition to the pack.
Built With
- api
- cli
- mailchimp
- typescript


Log in or sign up for Devpost to join the conversation.