How Can a Spanish Automation Consultant Show n8n and Make Client Work Under NDA?

An automation consultant working under NDA should publish only a sanitised project summary: the business process category, their own role, the deliverable type, and an outcome the client has explicitly allowed them to disclose.

A useful portfolio does not need screenshots of a client's live n8n canvas, Make scenario, CRM, or internal records. It needs enough structure for a prospect to understand the kind of problem you solve while confidential names, credentials, node details, volumes, and commercial data stay private.

What can an automation consultant safely show?

Show the problem class, your responsibility, the tools used at a high level, and only client-approved evidence.

A card can say that you designed an intake-to-CRM workflow or a monitored reporting pipeline without naming the client or exposing its topology. If permission is unclear, omit the brand, screenshots, dataset, exact volumes, and internal URLs.

Public template workflows, personal utilities, and open-source connectors can appear as separate projects because visitors can verify them directly.

Safe: general process and your role.
Conditional: approved testimonial or exact outcome.
Private: credentials, personal data, internal URLs, and copied client workflows.

What is the quick way to build the consultant page with IndieShow?

The quick way is to create an IndieShow page with separate cards for public tools, anonymised engagements, and active experiments.

Use the description for scope and responsibility, the tag for a truthful category such as automation or data workflow, and the link only when a public case study, demo, or repository exists. A project may stay useful without a destination when confidentiality requires it.

Place verifiable public work first, anonymised summaries second, and unfinished internal experiments under Building or Working on.

Build your IndieShow pageClaim a handle, organise the projects in the editor, and review the $15 one-year and $30 lifetime publishing options in the dashboard.

How should an anonymised automation case study be written?

Write an anonymised case study as problem, responsibility, delivered system, and approved result—without reconstructable client clues.

Avoid combining sector, city, team size, unusual tool stack, and dates if those details reveal the organisation. Explain what you personally designed or implemented, then distinguish tested delivery from an ongoing experiment.

Never invent time saved or error reductions. If the client did not approve a number, use a factual output such as automated handoff with monitoring and manual fallback.

Where should demos, templates, and private workflows link?

Link public demos and templates to their maintained source, and leave confidential workflows unlinked or point to an approved public case study.

Test each destination without a logged-in session. A broken Make template, inaccessible n8n instance, or private Notion page weakens the evidence and can expose a careless access setup.

The related IndieShow articles explain how to handle heterogeneous no-code projects and how to present archived work without overstating it.

How does IndieShow support a confidentiality-safe sales link?

IndieShow supports a stable, editable project index where a consultant can present approved evidence without uploading the underlying client system.

You control each project name, description, tag, optional metric, status, logo, and destination. That makes it possible to remove an expired approval, update an anonymised summary, or reorder proof before a proposal while the public handle stays the same.

IndieShow is the front door, not a substitute for the NDA or the client's approval process. When in doubt, disclose less and discuss sensitive details privately after authorisation.