The problem
Workflow platforms like n8n, Make, and Zapier are excellent at moving data between systems — and have almost nothing to offer the moment a human needs to be involved. There's no natural place for a customer to submit a request, for a team to see work in progress, or for a record to live between workflow runs. Teams end up bolting together forms, spreadsheets, and databases around their automations, and every one of those seams is something else to maintain.
Snapi is the application layer those platforms are missing: an embeddable UI you can drop into a portal or public website, persistent storage for the records your workflows operate on, Kanban-style positioning so people can see and move work, authentication, and direct integration with the workflow platforms themselves.
What I built
- An Angular frontend and a Node.js REST backend, designed and built end to end — UX, component architecture, state management, and API design by one person.
- Embeddable components that live inside other people's pages — the contact form at the bottom of my own resume is one of them, running in production.
- Persistent record storage with Kanban-style positioning, so workflow output becomes something a team can actually see, sort, and act on.
- Autonomous AI agents that triage, enrich, route, and complete workflow tasks — automation that participates in the queue rather than just feeding it.
- Subscription billing, built and wired in end to end — currently running on sandbox payments ahead of public launch.
- An n8n community node for Snapi, published and awaiting verification.
Decisions that mattered
Snapi is embed-first: the product's home is inside someone else's page, not its own app. That constraint drove the architecture — components have to carry their own styling, auth has to work across origins, and the API has to be safe to expose from a public website.
Where it stands
Live in production, pre-release, with sandbox payment integration ahead of public launch. Built at solo speed using AI-assisted development — this is the project where that workflow is most visible: one developer covering product design, frontend, backend, agents, and billing at a pace that used to take a team.