Start from what you have
Attach an OpenAPI spec, an n8n workflow, or your own documents when you create a project.
Plenty of products don't start from a blank page. You might already have an API, an automation you've outgrown, or a folder of documents describing how the thing is supposed to work. When you create a project you can attach any of it, and Pikku Studio Cloud works out what each file is.
Annotated screenshot of project creation with files being attached: one tagged "OpenAPI spec", one tagged "n8n workflow", one tagged "Reference". Callout: "Attach what you have — Pikku Studio Cloud works out what it is."
Three kinds of file
Pikku Studio Cloud classifies each attachment from its contents, not its name:
- An OpenAPI spec — a
.json,.yamlor.ymlfile describing an API. It's committed into your project so the builder can turn it into a typed integration. - An n8n workflow export — a
.jsonfile exported from n8n. It's kept for the builder to translate into a real workflow in your app. - Anything else — PDFs, Markdown, spreadsheets, CSVs, plain text. These land as background reading, and the builder decides what to do with each one.
Files are capped at 5 MB each.
Starting from an API
Attach the spec (or hand it to the builder later) and Pikku Studio Cloud wraps the API into a typed addon — every endpoint the spec describes becomes something your app can call, with its request and response shapes carried over from the contract.
Example: your logistics provider publishes an OpenAPI spec. You attach it, then say "make me a dashboard where my team books shipments and tracks them." The booking and tracking calls already exist — the builder just builds the product around them.
You don't always need to bring the spec yourself. Pikku Studio Cloud keeps a searchable registry of public API specs, so asking for a well-known service can pull its spec in and generate the same typed integration without you finding a file.
Why typed matters here
A spec is a contract: it says exactly what each endpoint accepts and returns. Pikku Studio Cloud keeps that contract in what it generates, so a screen trying to send the wrong shape of data to the API is caught before it ships — not discovered by your users.
The spec is the source of truth. Pikku Studio Cloud doesn't guess at the API from prose or examples — it generates from the machine-readable contract, and stays checked against it.
Moving off n8n
An exported n8n workflow isn't run as-is. The builder reads it and rebuilds what it does as a native workflow in your app — so you end up with code you own and can change, rather than a wrapper around the thing you were trying to leave.