What to put in an n8n freelancer portfolio

Short answer

Choose two or three narrow workflow examples. For each one, show the business problem, trigger, main steps, systems touched, failure path, and handover notes. Label demos as demos. If you have client work, describe only what you are allowed to share.

Pick examples a buyer can understand

A workflow name such as "multi-agent orchestration" leaves the reader guessing. "New enquiry to CRM and team alert" is easier to place.

Good portfolio examples can be small:

• a form submission that creates a CRM record and alerts the right person
• a paid order that updates a spreadsheet and sends an internal notice
• a client onboarding form that creates a folder, task, and welcome email

You do not need to claim a business result. Explain the task the workflow handles. If the example uses sample data, say so in the first paragraph.

Make's freelancer guide starts with skills, tools, industries, and processes. That is a useful way to choose portfolio pieces. Do not list every node you have tried. Pick workflows that match the kind of work you want to discuss.

Use the same page shape for every example

A reader should be able to scan your examples and compare them. Use these headings:

Problem

Write one sentence about the manual handoff or missed step. "A form response sat in an inbox until someone copied it into the CRM" is enough.

Trigger and path

State what starts the workflow, then describe the main steps in order. Name the systems. If a webhook starts it, explain what sends the webhook. If a schedule starts it, say how often only when that is part of the demo.

Data and permissions

Say what data moves between systems. Do not publish tokens, private customer details, or screenshots containing credentials. Explain which accounts a client would own and which access you would need.

Failure path

Show the branch or handler for a failed request. According to n8n's documentation, the Error Trigger node lets you build an error workflow that runs when a linked workflow fails and receives details about the failed workflow and the error. The same page says you cannot test error workflows by running a workflow manually, since the trigger only runs when an automatic execution errors. The Stop And Error node can send a custom message to the Error Trigger. A portfolio entry that shows the failure path answers a question many happy-path demos avoid.

Test and handover

List the test data you used and the cases you checked. Include a short handover note with the credentials the client must own, the places they can change safely, and what to do when a service rejects a request.

A demo is still useful

A new freelancer often has no client case studies. That does not prevent a useful portfolio. Build a demo around a public or invented process and label it clearly:

"Demo built with sample form data. No client account or customer data was used."

Then describe what the demo proves. It may prove that you can validate a field, route records, call an API, or handle a failed step. It does not prove that a client saved a certain amount of time. Do not write that claim.

Some portfolio guides tell you to write lines such as "reduced manual data entry by 15 hours per week". One page we read gave that as an example and also quoted a survey statistic with no source. If you have no measured result, do not write one.

The n8n workflow library page we read uses a form, proposal variables, Google Drive, and Google Slides. Its useful pattern is that the page explains setup requirements and the order of operations. Its marketing copy is not proof that every portfolio owner has the same result. Keep your own page focused on what you built.

Two freelancer portfolio pages on Freelancer.com name the client process, the connected services, and the type of technical work involved. Their production counts and hourly rates belong to those profiles, so do not copy them as benchmarks.

Write for the buyer's next question

After reading an example, a buyer will usually want to know one of these things:

• Can this connect to our tools?
• What happens when an API call fails?
• Will we own the accounts?
• Can we change the workflow later?
• How would we test it without sending real messages?

Answer those in the example itself. A tool logo does not answer them.

Your profile can then point to a small service. For example, "I build and repair n8n workflows for lead routing and onboarding." That is easier to match with a request than "automation specialist" alone.

Keep the technical notes readable

You can include a workflow screenshot, but it should support the explanation. Crop out private data. Add labels for the trigger, main action, validation, and error route. If the screenshot is too wide to read on a phone, use a text summary beside it.

Avoid a wall of node names. Explain the decision behind a node. "The lookup checks for an existing customer before creating a second record" tells more than "HTTP Request, IF, Merge, Code."

For context on finding first projects, read how to become an n8n freelancer and find first clients. For support work after launch, read error handling for client automations.

A portfolio review checklist

Before you send a link, check that each example has:

• a named business problem
• a labelled demo or a permitted client example
• the trigger and main path
• systems and access assumptions
• a failure case
• test notes
• a plain next step

Remove claims that depend on numbers you cannot source. Remove screenshots with real names or private records. Ask a friend who does not use n8n to explain what the workflow does after one minute. If they cannot, shorten the technical section.

Thomas Partners brings client work to freelancers. You keep 90% of the profit after documented costs are repaid. Apply to join.