@n8n/instance-ai 1.16.2 → 1.17.0

package/skills/workflow-builder/SKILL.md

@@ -259,19 +259,19 @@ decision after testing.
   collects real ones later.
 - When `build-workflow` returns `resolvedCredentialsByNode`, the build already
   attached a credential to those nodes — either an existing stored credential or
-  an n8n Connect–managed one (entries with `id: null` and `__aiGatewayManaged:
+  an n8n credits–managed one (entries with `id: null` and `__aiGatewayManaged:
   true`). Treat them all as connected: do not ask the user to connect or create
   those credentials, do not route them to credential setup, and mention at most
-  that the credential (or n8n Connect) is being used.
+  that the credential (or n8n credits) is being used.
 - Never use raw credential objects like `{ id: '...', name: '...' }` in SDK
   code; replace them with `newCredential()` when editing roundtripped code.
 - If a required credential type is not listed, call
   `credentials(action="search-types")` with the service name. Prefer dedicated
   credential types over generic auth; when generic auth is truly needed,
   prefer `httpBearerAuth` over `httpHeaderAuth`.
-- `credentials(action="list", type=...)` may include a synthetic n8n Connect
-  entry `{ id: null, name: "n8n Connect", type, __aiGatewayManaged: true }`
-  when the type is covered by n8n Connect (see n8n Connect Preference). It is
+- `credentials(action="list", type=...)` may include a synthetic n8n credits
+  entry `{ id: null, name: "n8n credits", type, __aiGatewayManaged: true }`
+  when the type is covered by n8n credits (see n8n credits Preference). It is
   not a stored credential: never pass it to `newCredential(...)` and never
   emit `id: null` or the `__aiGatewayManaged` marker in SDK output. Setup
   applies it automatically when the user has no stored credential of that type.
@@ -281,11 +281,11 @@ decision after testing.
 - Always declare `output` on nodes that use unresolved credentials when mock
   data is needed for verification.
 
-## n8n Connect Preference
+## n8n credits Preference
 
-"n8n Connect" is the user-facing name of n8n's managed credential
+"n8n credits" is the user-facing name of n8n's managed credential
 service. On instances licensed for it, several common AI-provider and
-scraping nodes can run with zero credential setup on the user's side.
+scraping nodes can run with no API key required on the user's side.
 
 **Discovery (while building):** `nodes(action="search")` and
 `nodes(action="describe")` results carry an `aiGateway` field on covered nodes
@@ -298,7 +298,7 @@ tool*, and respect the constraints it reports:
     use the marker key `__operation_only__`.
   - Do not set parameters listed in `aiGateway.hiddenProperties`.
 
-**Enumeration (answering "what does n8n Connect support?"):**
+**Enumeration (answering "what does n8n credits support?"):**
   - All supported nodes: `nodes(action="list", n8nConnectOnly=true)` — each
     result carries the full `aiGateway` field (minVersion, operations,
     hiddenProperties).
@@ -308,18 +308,20 @@ tool*, and respect the constraints it reports:
     → `aiGateway.operations`.
 
 **Preference rule:** When adding a new node that has no credential assigned
-yet, prefer n8n Connect over stored credentials if the credential type is
-supported — it provides zero-setup access and avoids spending the user's API
-quota. The synthetic entry in `credentials(action="list", type=...)` (see
+yet, prefer n8n credits over stored credentials if the credential type is
+supported — it works with no API key required and avoids spending the user's
+API quota. The synthetic entry in `credentials(action="list", type=...)` (see
 Credential Rules) is your signal that a type is covered. Do not change
 credentials on nodes that already have one assigned (editing an existing
 workflow, or after the user has made a credential choice).
 
 - If the user explicitly specified their own credential (by name or by
   choosing one from a list), use that credential and do not substitute
-  n8n Connect.
+  n8n credits.
 - When speaking to the user in chat, always refer to this feature as
-  "n8n Connect" — not "AI Gateway", which is only an internal name.
+  "n8n credits" — never "n8n Connect", "AI Gateway", or "gateway". Those are
+  internal names only, including the `aiGateway` field on node/credential
+  results: read it to make decisions, but never surface that name to the user.
 
 ## Missing Resources
 
@@ -452,7 +454,6 @@ import {
   workflow,
   node,
   trigger,
-  sticky,
   placeholder,
   newCredential,
   ifElse,
@@ -521,6 +522,12 @@ Follow these rules strictly when generating workflows:
    match time units broadly (day/days, week/weeks…), and give every classifier
    an explicit fallback bucket — a one-phrasing regex silently misroutes every
    other phrasing.
+7. Do not add sticky notes (`sticky(...)` / `n8n-nodes-base.stickyNote`) unless
+   the user explicitly asks for canvas notes. They add visual noise and are
+   often poorly positioned. Put explanations in your chat reply instead. Even
+   when the SDK language reference documents `sticky()`, do not use it by
+   default. When editing a workflow, do not add or reintroduce stickies unless the user
+   explicitly asks for them.
 
 ## Tool Naming Rules
 
@@ -682,8 +689,9 @@ For AI Agent workflows:
 ## Additional SDK Functions
 
 - `placeholder('hint')`: marks a parameter value for user input.
-- `sticky('content', nodes?, config?)`: creates a sticky note. It must still be
-  added to the workflow.
+- `sticky('content', nodes?, config?)`: opt-in only when the user explicitly
+  asks for a sticky note on the canvas. Do not import or call it otherwise.
+  When used, it must still be added to the workflow.
 - `.output(n)`: selects a zero-based output index.
 - `.onError(handler)`: connects a node's error output to a handler. Requires
   `onError: 'continueErrorOutput'` in the node config.