Vibe Coder · Unit 15: Workflows With n8n · Project
Milestone 15 of 23
Your product’s back office
The automatic jobs behind your product, as tested workflows in GitHub.
One product, built one milestone at a time
Vibe Coder has one project. You pick an idea in Unit 1 and every unit adds a piece to it, until the last unit launches it. Every milestone ends with a push to your own GitHub repository. A product is more than its screens. This milestone builds the work that has to happen by itself: a signup handled, a webhook answered, a failure reported. It uses n8n, so every step is visible.
- 1Your builder’s kitA one-line product idea, your role, and five working accounts.
- 2A fact-checked product briefOne page on your idea, tested against how the models really behave.
- 3Your product project in ClaudeA project with instructions and files, and your first real piece of work from it.
- 4A brand kit and research fileA name, images and market research for your product, with a second opinion.
- 5Your prompt libraryThe prompts you will reuse to build the product, each one tested.
- 6Your product specThe problem, the people, the first version and how you will measure it.
- 7A clickable prototypeA version people can click through, shown to three of them.
- 8A working first draftYour product generated from the brief, with sign-in and data, in your own GitHub repository.
- 9The first working versionYour app running on your computer, built with Claude Code.
- 10Your Claude Code setupProject instructions, a custom command and a skill made for your app.
- 11One AI featureA feature in your app that calls a model, with its key kept safe.
- 12A connected assistantClaude or ChatGPT connected to a tool you already use, with the right permissions.
- 13Sign-in and saved dataAccounts and a database behind your app.
- 14Your app, liveOnline at its own address, updating every time you save.
- 15Your product’s back officeThe automatic jobs behind your product, as tested workflows in GitHub.
- 16An agent that works for your productOne agent with narrow tools, limits, approval and a test set.
- 17A helper that answers from your documentsAnswers with sources, scored on your own questions.
- 18A product that can chargeEmail from your own domain and a tested checkout, in test mode.
- 19A model tuned for one jobA small experiment, measured against your best prompt.
- 20A brand image kitOn-brand images from one saved workflow, with your own LoRA.
- 21A launch videoThirty to sixty seconds, with voice, music and sound.
- 22A tested, locked-down appEvery flow checked, and each person able to see only their own data.
- 23Your launched productThe finished product, in front of people, with a page that shows your work.
Your product gains
Automatic jobs that run without you
That makes 15 of 23 pieces in place.
Your role
The steps change with your role. Choose yours to see your version of this milestone.
Start with this prompt
Paste it into Claude or ChatGPT, or into Claude Code once you are building. Fill in the parts in square brackets with your own product.
Here is my product and what it does today: [paste the one-line description and the main journey] Help me list the jobs that should happen automatically behind it. For each one I want: the trigger, the steps in plain words, the services it touches, and what should happen when it fails. Work with me one step at a time. Ask me one question, wait for my answer, then go on. Do not write the finished thing for me: show me a draft, tell me what is weak about it, and let me decide. Start with the job a new signup needs. I will build that one first in n8n.
Build it step by step
6 steps, one from each lesson of the unit. Do each step after its lesson. A box you tick here is ticked in the lesson too.
Step 1 of 6 · from the lesson What n8n is
Read the short notes and pictures.Do everything inside a blue frame.
ActivityBuild stepYour product’s back office Map your back office
Create an n8n account (Cloud is fine). Then write a list of the three to five automatic jobs your product needs. For each: the trigger, the steps in plain words, and which services it touches.
Done when
You will build the first of these in the next lesson.
Step 2 of 6 · from the lesson Your first workflow
Read the short notes and pictures.Do everything inside a blue frame.
ActivityBuild stepYour product’s back office Build the signup workflow
In n8n, build the workflow for a new signup: trigger, save a row, send a welcome message, notify yourself. Test it with three different signups and then publish it.
Done when
Export the workflow as a JSON file and keep it. It goes into your repository later in this unit.
Step 3 of 6 · from the lesson Data between nodes
Read the short notes and pictures.Do everything inside a blue frame.
ActivityBuild stepYour product’s back office Add a branch to your workflow
Extend your signup workflow: clean the incoming data with Edit Fields, then branch on one field that matters in your product (plan, country or role) so that each group gets a different message.
Done when
Export the updated workflow JSON, replacing the earlier file.
Step 4 of 6 · from the lesson Webhooks: your own API
Read the short notes and pictures.Do everything inside a blue frame.
ActivityBuild stepYour product’s back office Give your product one webhook feature
Pick one feature your app needs a backend for. Build a workflow that starts with a Webhook node, does the work, and ends with Respond to Webhook. Protect it with a secret and call it from your app.
Done when
Write the request and response shapes down in a short file. It belongs in your repository beside the workflow JSON.
Step 5 of 6 · from the lesson Calling any API
Read the short notes and pictures.Do everything inside a blue frame.
ActivityBuild stepYour product’s back office Connect a service that has no node
Pick one service your product needs that has no n8n node, or use the node-free route for one that does. Call it with an HTTP Request node from one of your workflows, using a saved credential.
Done when
Note the endpoint and what it does in your workflow notes.
Step 6 of 6 · from the lesson When workflows fail
Read the short notes and pictures.Do everything inside a blue frame.
ActivityBuild stepYour product’s back office Harden and publish your workflows
Add an error workflow that messages you, switch on retries for nodes that call outside services, and make your riskiest step safe to run twice. Then export every workflow and push them to your product’s GitHub repository with a README.
Done when
This folder is your back office, in version control. Keep it up to date for the rest of the course.
Publish it to GitHub
Your product repository
Export every workflow as JSON into a workflows/ folder with a README. Search the files for anything that looks like a key, then commit and push.
A milestone is not finished until it is pushed. A public repository with a history is how other people, including employers, can see what you built. Never commit a key, a token or anyone’s private data.
When it is done
Every box above is ticked, the work is pushed to GitHub, and you can show the result to someone who has not seen it before. Then move on: milestone 16 is an agent that works for your product.