← All essays

    Excerpted from 55 and Out, AI Automation

    Replacing Zapier With a 40-Line Script

    ·3 min read

    Zapier is wonderful. Until it isn't. Mine isn't was when a critical Zap stopped firing for nine days without telling me, and I missed something I shouldn't have missed.

    I had three active Zaps:

    1. New Stripe charge → row in a Google Sheet
    2. New form submission → email to me + row in a different sheet
    3. Daily summary of those two sheets → posted to a Slack channel

    Total: $49/month. About $588/yr. Plus the silent failure, which cost me real time to untangle.

    I rewrote all three in a single Python script. About 40 lines. Runs on a small server I already have for $5/month. Total time to write and test: a Saturday morning, maybe four hours. Total time to deploy: ten minutes.

    What it does:

    • Polls the Stripe API every 5 minutes for new charges, appends to the sheet via the Google Sheets API
    • Receives form posts at a webhook endpoint, sends an email via a transactional service, appends to the sheet
    • Runs at 9 AM daily, queries both sheets, posts the summary to Slack

    What broke during the build: my own assumptions. I thought reading the Stripe API would be hard. It wasn't. I thought authenticating to Google Sheets would be straightforward. It wasn't — the OAuth dance ate an hour. The Slack post was three lines.

    What I gained beyond the $44/month savings: visibility. The script logs every run to a file I can grep. If anything fails, I know within 24 hours from a daily health-check email I added in line 41 (so much for 40 lines). With Zapier I had no idea what was happening inside the box.

    What I lost: the GUI. If a non-technical person needed to add a Zap, they'd be lost in my script. Zapier is genuinely better for that case.

    What I'd do again: rewrite anything that's costing me more than $20/month and that I understand well enough to maintain. What I wouldn't: rewrite the rare, complex integration where Zapier is doing real work — multi-step branching with retries and error handling and dedup. Those are worth paying for.

    The deeper point: SaaS makes sense for things you'll touch once a year. For things that run every day and matter, write the 40 lines.

    Share

    This essay is excerpted from the book.