About
Peter Prochazka
Automation, AI workflows, system integrations, and internal tools.
Background
I start with the process: understand it, map it, break it down. People inside a business get used to the breaks — an eight-hour handoff becomes "how we do it." I find where a call fails overnight or two systems disagree about the same number, and rank the fixes.
What I build
A Slack agent that classifies inbound messages, answers from a knowledge base during working hours, and escalates with the original thread intact. Reporting that replies in the email that asked for the numbers. A commerce console where Shopify, content, and ops agents share one panel, and failures surface instead of disappearing into a queue. Those are a few that shipped. There's more. If you're not sure it fits, email me. I'll tell you if I've done it, something close, or how I'd do it.
Stack
n8n, Make, Zapier, OpenAI/Claude, Cursor, Shopify, Meta Marketing API, Slack, webhooks, custom REST/API integrations where no native connector exists.
How I work
Email me a brief if you have one. If you don't, tell me how the process runs and where it sticks. I'll come back with what's worth building and how. I use the tool that already matches the rest of the stack — not a new one for its own sake. You get the workflow, the credentials path, and notes on what fails and how it retries. If you're an agency, start on the agencies page so the terms aren't a surprise.
Contact
Rate is a conversation.