How to add a real backend to any app with the Zapier SDK
Corbin Brown
3 min read
A backend is the part of your app that runs on a server instead of in the browser: where real data comes in, where secrets stay hidden, and where things happen on a schedule whether or not anyone has the page open. Most vibe-coded prototypes stop before this point. The screen looks finished but the numbers are placeholders. The video takes a morning-brief dashboard exactly like that and wires it to real Gmail, real GitHub issues, and a real calendar through the Zapier SDK, then has AI turn all of it into a task list and a briefing email that sends itself every weekday at 7 AM.
Why the connection step is the hard part
Each real service has its own sign-in dance, its own permissions, its own way of handing you data. Doing Gmail, GitHub, and Google Calendar by hand means three different authorization flows before you've written any feature. The Zapier SDK (a code library that gives your app one consistent, already-authorized way to talk to thousands of apps) collapses that to a single pattern. You authorize once, and each service becomes a function call. For a beginner, this is the difference between a weekend project and a month of reading documentation.
The build, in order
- 1Connect the sources. Gmail, GitHub issues, and calendar events come in through the SDK. Keep the keys and tokens in a .env file on the server; the browser never sees them.
- 2Let AI do the one job that needs it. Turning a pile of emails, issues, and meetings into a prioritized task list is judgment work, so that's the model's step. Fetching and sorting the raw data is not, so that stays plain code (the 87% cost rule).
- 3Put it on a schedule. The briefing runs at 7 AM on weekdays, which means the code has to live somewhere that's awake at 7 AM: a hosted platform's scheduled job, not your laptop.
- 4Send the result. The brief goes out as an email, so the last piece is a sending service with delivery tracking, and a way to tell when a send failed.
Where the data should live
The video's dashboard reads live from the sources each morning, which is the simplest correct version. The moment you want history (what did yesterday's brief say, how many issues closed this week) you need a database, and Supabase is the usual answer for the same reason the SDK is: it removes a category of setup work. Add it when you have the question, not before.
FAQ
Is Zapier the backend?
No. Zapier is the connection layer; your backend is still your own server code that calls it, runs the AI step, and sends the email. That distinction matters because it means you own the logic and can swap any connection later.
Can I run the schedule on my own computer?
You can for testing, and it will silently fail the first morning the laptop is asleep. Scheduled work belongs on a hosted platform or an always-on machine, the same rule as any AI agent that works while you don't.