awml
Sign in

awml / platforms / n8n-cloud

n8n Cloud

Platform · Public ·
Version 2 of 2
  1. #2 · chrismdp · · 0.4ShowingLatest
  2. #1 · chrismdp · · 0.3

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.

What it offersInstall recipeYAML

Install a workflow on n8n Cloud

The workflow runs as an n8n workflow on n8n's hosted service: a trigger node, then nodes that run in order. Each code step is a node, each AI step is an AI node with a chat model for the company the fit named, and each connector is an app node with its own credential. n8n Cloud keeps no folders: state the workflow makes lives in a data table or a connected app.

Run awml fit with the workflow's security view and this description first. Contexts kept in folders, with at, do not fit here. n8n runs the instance and sees what the workflow handles, which the fit does not check, so make sure every scope the workflow touches allows n8n.

What to create

  1. A new workflow in the n8n Cloud instance, named after the AWML workflow.
  2. A trigger node: a Schedule Trigger for a time, or an app trigger or Webhook node for an event.
  3. One node, or a short run of nodes, for each step, in the order the drawing lists them. A code step uses ordinary nodes or a Code node. An AI step uses a Basic LLM Chain or AI Agent node with the chat model sub node for the company the fit named, and passes it only what that step may read. An outside action marked Ask ends in a draft or a message asking a person for a yes, never in the action itself.

Where secrets go

Every key and sign in goes in an n8n credential, chosen on the node that uses it. n8n encrypts credentials before saving them. Never paste a key into a Code node, an expression or a node's text fields.

How to schedule the triggers

Set the Schedule Trigger's interval or cron expression. It uses the workflow's time zone if set, otherwise the instance's, which n8n Cloud sets from the owner's at sign up. Save and publish the workflow: a schedule does not fire until it is published, and a variable used in it is read only when it is published.

How to check it is running

The workflow's Executions list shows every run, with each node's input and output. Use Execute workflow in the editor once before publishing to test it, and set an error workflow in the workflow's settings so a failed run sends you a message.

Sources

  • https://docs.n8n.io/integrations/builtin/core-nodes/n8n-nodes-base.scheduletrigger/
  • https://docs.n8n.io/integrations/builtin/cluster-nodes/sub-nodes/
  • https://docs.n8n.io/deploy/host-n8n/configure-n8n/basic-configuration/configuration-examples/set-a-custom-encryption-key
  • https://docs.n8n.io/integrations/builtin/core-nodes/n8n-nodes-base.readwritefile/