one-off-operations

Build and execute single-run n8n workflows for bounded data operations.

203k|60.5k|Updated Jun 22, 2019
One-click install
npx skills add https://github.com/n8n-io/n8n --skill one-off-operations
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: one-off-operations
Source: https://github.com/n8n-io/n8n/tree/main/packages/%40n8n/instance-ai/skills/one-off-operations
Command: npx skills add https://github.com/n8n-io/n8n --skill one-off-operations

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Many user requests describe a concrete effect that should happen once — exporting rows, copying data, cleaning duplicates, or backfilling a table — rather than an automation that runs repeatedly. This Skill recognizes those requests and routes them through a manual-trigger workflow that executes live and reports the actual outcome.

Core Features & Use Cases

  • One-Off Recognition: Infers from task shape (bounded data, imperative phrasing, no trigger vocabulary) whether the request is a single operation rather than a reusable automation.
  • Manual-Trigger Build: Constructs the workflow with a manual trigger and executionIntent: "one-off", marking verification as optional and treating the live run as the completion criterion.
  • Live Execution and Read-Back: Runs the workflow via executions(action="run") and inspects effect-node output with executions(action="get-node-output") before reporting quantitative claims.
  • Use Case: A user pastes 50 rows and asks to copy them into a Google Sheet. The Skill builds a manual-trigger workflow, runs it live, reads back the written rows, and confirms the exact count and columns.

Quick Start

Build a one-off workflow that copies the rows from the pasted data into the Google Sheet named "Q4 Audit".

Frequently Asked Questions about one-off-operations

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run a one-off data operation in n8n?

Build a workflow with a manual trigger and pass executionIntent "one-off" to build-workflow. Then run it live with executions(action="run") and read back the effect-node output with executions(action="get-node-output") to confirm the actual data written.

What is the difference between a one-off workflow and a scheduled automation?

A one-off workflow uses a manual trigger and runs once for a bounded data effect like an export or cleanup. A scheduled automation uses a schedule trigger and runs repeatedly on new or recurring data.

Can a one-off workflow write to external services like Google Sheets?

Yes. One-off operations that touch external systems are still workflow-anchored because direct writes are not possible. The workflow runs live with real credentials and the effect-node output is read back for confirmation.

Why does my one-off workflow report success but write the wrong data?

A successful run status only proves the workflow executed, not that the intended data reached the write node. Inspect the effect node's actual input with executions(action="get-node-output") to verify the rows match what you meant to write.

When should I not use the one-off operations flow?

Do not use it when the request includes trigger vocabulary like "when", "every", or "whenever", or when the user wants the automation itself for future reuse. In those cases, follow the normal reusable build flow with verification.