There is a new genre of video: "this free workflow automates your whole business, just download it from my link." The template imports, the demo works, and nobody in the video ever asks the question a business should ask first: what did we just install, and who wrote it?
Community templates, n8n workflows, MCP servers and GitHub projects are one of the best things about the automation ecosystem. We use them. But installing one is not like watching the video; it is like hiring a tiny contractor and handing them your credentials. A workflow template can contain hardcoded destinations your data gets sent to. An MCP server runs with whatever access you grant it. A vibe-coded tool from an unknown repository is code your business now runs, written by someone you cannot name.
The five checks before you install
Who published it, and do they exist anywhere else? A real maintainer has a history: other projects, a company, a profile that did not appear last month. Anonymous accounts with one repository and heavy video promotion are the pattern behind most malicious packages.
Is the project alive? Look at the last update, the open issues and whether the maintainer responds. Abandoned projects do not get security fixes, and forks of popular projects with tiny changes deserve extra suspicion: that is a classic way to slip something in. On GitHub, stars help but can be bought; recent, substantive activity is harder to fake.
Can you read what it does with your data? For an n8n or Make template, open every node before running it and check where data is sent: any URL, webhook or email address you do not recognise is a stop sign. For an MCP server, check which scopes it requests and whether it phones home anywhere. If nobody on the team can answer "where does our data go when this runs", do not run it.
What access does it ask for? The connectors rule applies: least privilege. A template that asks for admin access, full drive scope or credentials it does not obviously need is either lazily built or worse. Grant the narrowest access that lets it work, and use test credentials first.
Did you test it away from production? Run it with synthetic data in a sandbox account before it touches real customers, invoices or inboxes. Ten minutes of testing is cheaper than any incident.
Turn the checks into a team habit
One cautious person reviewing everything does not scale, and it recreates the single-expert trap. Make provenance part of how the team adopts anything. Keep an inventory of what is installed, from where, with what access, the same inventory we recommend for connectors. Prefer sources with real maintainers and real histories. And when a template passes the checks, save your reviewed copy in your own repository, so the version you trust is the version you run.
This is the same supplier diligence your business already applies to everything else, finally applied to the fastest-growing category of software you install.
If your team is adopting automation templates faster than anyone is reviewing them, that is a governance gap: the free assessment will show where it sits among the five layers, or bring it to a 30-minute diagnosis call.