n8n Cloud

description.yaml is AWML 0.3, as it was pushed. The fit reads it converted to AWML 0.8.

# A workflow built in n8n Cloud, n8n's hosted service: nodes run in order from a trigger, and AI
# nodes call the model companies whose credentials you add. This describes a kind of platform, not
# anyone's instance; a self-hosted n8n is a server, with its own disk. n8n, which runs the instance,
# sees everything the workflow handles, and the fit has no field for that. Checked against n8n's
# documentation on 22 October 2026.
awml: "0.3"
platform: { id: n8n-cloud, label: "n8n Cloud" }

# A hosted service that is always on. A Schedule Trigger fires only once the workflow is saved and
# published.
# https://docs.n8n.io/integrations/builtin/core-nodes/n8n-nodes-base.scheduletrigger/
off_for_up_to: PT0S

# The workflow's nodes run in the order drawn, the same way every time. An AI Agent node is a step an
# AI decides, calling a chat model, so it counts under calls, not agents.
# https://docs.n8n.io/integrations/builtin/cluster-nodes/sub-nodes/
steps: code

# No agent runs over the whole instance: each AI node sees only what the workflow passes it.
# https://docs.n8n.io/integrations/builtin/cluster-nodes/sub-nodes/
agents: []

# Chat model nodes reach OpenAI, Anthropic, Google Gemini and Vertex, Mistral, Amazon Bedrock and
# many more, and the HTTP Request node can call any API.
# https://docs.n8n.io/integrations/builtin/cluster-nodes/sub-nodes/
# https://docs.n8n.io/integrations/builtin/core-nodes/n8n-nodes-base.httprequest/
calls: any

# n8n Cloud keeps no folders: its file system is limited to /home/node and files written there are
# not kept between executions, and the Execute Command node isn't available.
# https://docs.n8n.io/integrations/builtin/core-nodes/n8n-nodes-base.readwritefile/
# https://docs.n8n.io/integrations/builtin/core-nodes/n8n-nodes-base.executecommand/
holds: []