What "validated" means here
Every file on this site is generated from the Actor's published input and output schema and passes the checks below before the page is built. A failing check stops the build. Validated is not executed: nothing here runs an Actor, so no page shows invented results.
- Actor pages
- 394
- With a full published schema
- 394
- Recipes
- 65
- n8n node types known
- 27
Example input
- Values come from the Actor's own Store prefill, then from schema defaults for required fields. Optional fields without a prefill are left out so the Actor applies its defaults.
- Every key exists in the published input schema, every value has the declared type, choice fields use a published option and numbers respect the minimum and maximum.
- Secret fields are never filled. Where a required field has no safe default, the page names it and asks you to fill it in.
n8n workflows
- The JSON has nodes and connections, names are unique and each node has a type, typeVersion, position and parameters.
- Node types and versions come from n8n's source. The site emits versions n8n has shipped since 1.80 (for example HTTP Request 4.2, Google Sheets 4.5, Notion 2.2), so older self-hosted instances import them.
- Every connection resolves, a trigger starts the flow, and every working node is reachable from it.
- The Apify call uses POST to
/v2/actors/owner~name/run-sync-get-dataset-itemswith a Header Auth credential, and its JSON body passes the input checks above. - Credentials are not in the file. You select them after import.
MCP configs
- The URL is Apify's hosted server,
https://mcp.apify.com/?tools=, listingfetch-actor-detailsand the chosen Actors as owner/name. The retired/sseendpoint andactors=parameter are never used. - Each client uses its documented format:
mcpServerswithurlfor Cursor,serverswithtype: httpfor VS Code,[mcp_servers.name]for Codex, the HTTP transport for Claude Code and OAuth for ChatGPT. - Tokens are placeholders or environment variables, never values.
Agent skills
- SKILL.md has front matter with only the spec's fields; the name is lowercase with single hyphens, at most 64 characters, and matches the folder; the description is at most 1,024 characters.
- The run command calls the right Actor endpoint, reads the token from
APIFY_TOKEN, and its example input passes the input checks.
Pages
- A built-page gate fails the build if any page shows
undefined,NaN,null,[object Object], template braces outside code, an empty heading or a broken internal link. - Every catalogue Actor must have its own page. Pages whose Actor publishes no usable schema stay out of search and say why.
- Written text that names a field or node the current file does not contain is dropped rather than shown.
The catalogue
Recipes, MCP configs and Store links are limited to the catalogue, which is finely curated by our research team after detailed manual testing. Every catalogue Actor is manually tested on a daily basis. That programme is separate from file validation, which checks structure and schema fit, not a live run.
What is not checked
We do not run paid Actor runs, check your credentials or your destination's settings, or evaluate n8n expressions. A file can pass and still fail at run time if the Actor, the source site or a credential changes. If you find a file that fails a check above, email the page address and the error.