← Search

n8n workflow automation playbook for document pipelines
Productivity 🧪 Install ran in our test sandbox · Nov 11, 2026 📌 Pinned version: commit 9c4c7d5
Install test only, on the date shown. This does not guarantee the code is safe.
⚙ Needs: an n8n instance…

n8n workflow automation playbook for document pipelines

Automate document workflows with n8n — node-based pipelines, 400+ app integrations, contract-review example, self-host vs cloud

At a glance
What
Automate document workflows with n8n — node-based pipelines, 400+ app integrations, contract-review example, self-host vs cloud
Cost
Free
Needs
an n8n instance — self-hosted via Docker (n8nio/n8n, free) or n8n Cloud (billed at scale); your own LLM API keys for AI nodes and credentials for the apps the workflows touch — all kept in the secure vault / n8n credential manager, never pasted into workflows
Install
Copy the installer prompt below into your Muse — your agent does the rest.

Version:

@
Created by: @claude-office-skills

Quick answer

n8n workflow automation playbook is a free Muse skill that automates document workflows with n8n, using node-based pipelines and over 400 app integrations. It teaches n8n fundamentals, a Trigger to Action to Output flow with data moving between nodes, document nodes like read-PDF and OCR, transform nodes, and output nodes like email, Slack and Google Drive.

⌁

Install

Copy the install package below, then paste it into Muse🧪 Install ran in our test sandbox · Nov 11, 2026📌 Pinned version: commit 9c4c7d5

Step 0 — before installing anything: read this install prompt, summarize in a few lines what this build does and what installing it involves, then ask me to confirm before you proceed. Prerequisites: an n8n instance — self-hosted via Docker (n8nio/n8n, free) or n8n Cloud (billed at scale); your own LLM API keys for AI nodes and credentials for the apps the workflows touch — all kept in the secure vault / n8n credential manager, never pasted into workflows Install "n8n workflow automation playbook for document pipelines" for me. It gives my agent @claude-office-skills' n8n guide: node-based fundamentals and node-type table, a worked contract-review pipeline (watch folder → extract text → AI review → save report → Slack notify), self-hosted vs cloud comparison with a Docker quick start, and best practices (community templates, error-handling nodes, credential manager, test with sample data). MIT-licensed. Repository: https://raw.githubusercontent.com/claude-office-skills/skills/9c4c7d5cd2813a8936bf2c9fdb174ea883b85a11/n8n-workflow/SKILL.md Pinned version: install the code at commit 9c4c7d5cd2813a8936bf2c9fdb174ea883b85a11 exactly (Skill Harbor tested this version). Do not substitute a newer version. If this commit is unreachable, stop and tell me. 1. Fetch the SKILL.md file (and any helper files) from the repository path into a temporary folder 2. Safety check: review the SKILL.md and scripts for anything suspicious (unexpected network calls, shell commands, credential harvesting). This repo should contain zero secrets in code, credentials only via the secure vault, allowed hosts declared in the SKILL.md. Verify that holds here; STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md and its helper files into the agent's skills directory, in a folder named "n8n-workflow". 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself (e.g. start my n8n instance and connect the first app credentials in the credential manager; then describe the document pipeline to automate). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.

🔒 Security, provenance and what this touches
🧭 What this touches
Based on the install prompt we scanned, this skill does not run commands, make third-party network calls, install packages, write files, or ask for API keys.
Install prompt analysis · 2026-10-13
🔒 Security and provenance
📌 Pinned version: commit 9c4c7d5 · 2026-10-13
🧪 Install ran in our test sandbox · Nov 11, 2026
👁 Observed during the install test · Nov 11, 2026 : no network contact
🔎 Last checked · Nov 19, 2026 : no change detected in the files linked by this install prompt
Skill Harbor never reviews the code of a listed skill. These are dated facts about the install prompt and our install test, not a safety certification. Review a skill yourself before you install it. How we verify
Wanna be extra careful?

The install prompt below already includes the vetting steps: your agent follows the community checklist before installing anything with executable code. Want more?

How to check a skill before installing →

✓

Verification certificate

Dated facts about what was checked for this listing, and how. This is not a safety certification.

Pinned version
9c4c7d5 · 2026-10-13
Sandbox install test
Install ran in our test sandbox · Nov 11, 2026
Creator identity
Not verified
Fingerprint watch
Last checked · Nov 19, 2026 : no change detected in the files linked by this install prompt
Install prompt analysis
2026-10-13 : No commands, network calls, packages, file writes or API keys detected.

Skill Harbor never reviews the code of a listed skill. These are dated facts about the install prompt and our install test, not a safety certification. Review a skill yourself before you install it. How we verify

?

Questions

How do I install a skill?

Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the skill up for you — no manual configuration.

Where does my money go?

Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.

What does the ✓ next to a creator’s name mean?

It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a skill before installing it.