7 posts tagged with "automation"
I used to build my back ends in n8n - APIs, background jobs, queue work, AI integration, all of it. Something happened in January 2026 and now I don't reach for it, or for no-code platforms, at all. Here's the walls I hit and what I build with instead.
Read post →
Taking the agent from the last video and plugging it into a Slack room so it listens to everything, remembers it, and wakes up a real Linux box when it needs to. Supabase for the route and the memory, Railway for the box, Zapier's SDK for the CRM.
Read post →
Your vibe-coded app calls the Zapier SDK, which calls a real API. Run that in a test and it's not a test anymore: it needs a key, it costs a call, and it goes red when the wifi hiccups. Here's how to test it without ever hitting the real thing, and the one reminder to give your AI so it always does.
Read post →
You vibe-code a feature, it works, and a week later it's mysteriously broken again. And every time you want to go live it's the same tedious steps: run the database change by hand, copy the keys, click deploy, hope. CI/CD hands all of that to automation that refuses to ship anything broken. Here's how, using a real repo.
Read post →
I drag a feature card in my app and AI writes the code, runs the tests through GitHub Actions, and opens a pull request. I review, merge, and it deploys itself. Here's how the pipeline is wired, from a dragged card to a deploy, and what to do when a step needs a fix.
Read post →
There are plenty of hosted ways to give an AI a browser. This week I built my own — a little Chromium-on-a-server that stays logged in, spits out clean Markdown, and that any of my AI tools can drive. The real unlock: wrap it as an MCP and every agent I make gets a browser for free.
Read post →
Automation works — I've watched it save companies hundreds of thousands of dollars. But the wins came from sitting next to the person doing the work, not from dropping in a magic agent. Two real stories on what actually makes it stick.
Read post →