Tencent SkillHub · Developer Tools

Reef n8n Automation

Build, customize, and deliver n8n workflows fast using a 2,061-template library for triggers, actions, error handling, and multi-step automation.

skill openclawclawhub Free

0 Downloads

0 Stars

0 Installs

0 Score

High Signal

Build, customize, and deliver n8n workflows fast using a 2,061-template library for triggers, actions, error handling, and multi-step automation.

⬇ 0 downloads ★ 0 stars Unverified but indexed

Install for OpenClaw

Quick setup

Download the package from Yavira.
Extract the archive and review SKILL.md first.
Import or place the package into your OpenClaw setup.

Requirements

Target platform: OpenClaw
Install method: Manual import
Extraction: Extract archive
Prerequisites: OpenClaw
Primary doc: SKILL.md

Package facts

Download mode: Yavira redirect
Package format: ZIP package
Source platform: Tencent SkillHub
What's included: SKILL.md

Validation

Use the Yavira download entry.
Review SKILL.md after the package is downloaded.
Confirm the extracted package contains the expected setup assets.

Install with your agent

Agent handoff

Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.

Download the package from Yavira.
Extract it into a folder your agent can access.
Paste one of the prompts below and point your agent at the extracted folder.

New install

I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete.

Upgrade existing

I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run.

Open Send to Agent page Open JSON manifest Open Markdown brief

Trust & source

Release facts

Source: Tencent SkillHub
Verification: Indexed source record
Version: 1.0.0

Provenance

Publisher: staybased
Source page: View original listing
Canonical URL: Open canonical page

Documentation

ClawHub primary doc Primary doc: SKILL.md 24 sections Open source page

n8n Automation — Build & Deliver Workflows Fast

Build, customize, and deliver n8n workflows using our 2,061-template library. Reference: ~/projects/n8n-workflows/ — browse by integration folder. Our n8n instance: localhost:5678 (requires fnm use 22 before starting). All outputs go to workspace/artifacts/.

Use when

Building an n8n workflow for a client (Upwork, Alfred, direct) Customizing a template from our library for a specific use case Debugging or optimizing an existing n8n workflow Designing a workflow architecture before building Estimating delivery time for a workflow project Importing/exporting workflow JSON

Don't use when

Finding Upwork jobs (use upwork-hunting skill) Writing the client proposal (use proposal-writing skill) General coding tasks not involving n8n Zapier/Make.com builds (different platforms, different nodes)

Negative examples

"Find me automation jobs on Upwork" → No. Use upwork-hunting. "Build me a Python script" → No. This is n8n-specific. "Set up my n8n server" → Borderline. Infrastructure setup is ops, not workflow building. But credential configuration fits here.

Edge cases

Workflow uses custom JavaScript (Code node) → YES. n8n supports inline JS. Client wants Zapier→n8n migration → YES. Map Zapier triggers/actions to n8n equivalents. Workflow needs external API with no n8n node → YES. Use HTTP Request node. Multi-workflow orchestration → YES. Use Execute Workflow node.

Template Library Quick Reference

Location: ~/projects/n8n-workflows/workflows/ Structure: workflows/[IntegrationName]/[id]_[integration]_[action]_[trigger].json

Finding the Right Template

# List all templates for an integration ls ~/projects/n8n-workflows/workflows/Twilio/ # Search across all workflows find ~/projects/n8n-workflows/workflows/ -name "*.json" | grep -i "shopify" # Count templates per integration ls ~/projects/n8n-workflows/workflows/ | while read d; do echo "$(ls ~/projects/n8n-workflows/workflows/$d/ | wc -l) $d"; done | sort -rn | head -20

Top Integration Folders (by Upwork demand)

IntegrationPathCommon JobsGmailworkflows/Gmail/Auto-responders, lead capture, notificationsGoogle Sheetsworkflows/Googlesheets/Data logging, reporting, syncSlackworkflows/Slack/Notifications, bots, CRM syncTwilioworkflows/Twilio/SMS automation, call routing, alertsTelegramworkflows/Telegram/Chatbots, notifications, AI assistantsWhatsAppworkflows/Whatsapp/Business messaging, chatbotsShopifyworkflows/Shopify/Order notifications, inventory syncHubSpotworkflows/Hubspot/CRM automation, lead routingCalendlyworkflows/Calendly/Booking confirmations, follow-upsOpenAIworkflows/Openai/AI chatbots, content generationWebhookworkflows/Webhook/Custom triggers, API integrationsAirtableworkflows/Airtable/Database sync, form processing

Step 1: Assess Requirements

From client discovery, answer: What triggers the workflow? (webhook, schedule, form, app event) What actions need to happen? (send email, update CRM, create record) What data needs to flow? (fields, formats, transformations) What error handling is needed? (retries, fallback, alerts) What credentials are required? (API keys, OAuth, etc.)

Step 2: Find Matching Templates

# Search for relevant templates find ~/projects/n8n-workflows/workflows/ -name "*.json" | xargs grep -l "keyword" 2>/dev/null Or browse by integration folder. Most jobs need 2-3 templates stitched together.

Step 3: Import & Customize

Copy template JSON In n8n: Menu → Import from File (or paste JSON) Update credentials (Client's API keys) Update field mappings (their data structure) Adjust trigger settings (their webhook URL, schedule, etc.) Add error handling nodes (Error Trigger → notification)

Step 4: Test

Use n8n's Manual Execution to test each node step-by-step Verify data flows correctly between nodes Test error paths (what happens when an API is down?) Check rate limits (especially for bulk operations)

Step 5: Document & Deliver

Every delivered workflow includes: ## Workflow: [Name] **Trigger:** [What starts it] **Steps:** [1. → 2. → 3.] **Credentials needed:** [List] **Testing:** [How to verify it works] **Maintenance:** [What might break and how to fix it]

Pattern 1: Trigger → Transform → Action

The simplest and most common. Event happens → process data → do something. [Webhook/Form/Schedule] → [Set/Code node: transform data] → [Send Email/Update CRM/Create Record]

Pattern 2: Trigger → Branch → Multiple Actions

Different outcomes based on conditions. [Trigger] → [IF node: check condition] → True: [Action A] / False: [Action B]

Pattern 3: Scheduled Batch Processing

Periodic bulk operations. [Cron/Schedule] → [Get data from Sheet/DB] → [Loop: process each item] → [Action per item]

Pattern 4: Webhook API Endpoint

n8n acts as an API that other services call. [Webhook: receive request] → [Process] → [Respond to Webhook: return data]

Pattern 5: Multi-Step Pipeline

Complex workflows with multiple stages. [Trigger] → [Enrich data] → [Route/Split] → [Multiple actions] → [Aggregate] → [Final action]

Pattern 6: Error-Resilient Workflow

Production-grade with error handling. [Trigger] → [Try: main flow] → [Catch: Error Trigger] → [Alert via Slack/Email]

Node Cheat Sheet

NeedNodeNotesCustom logicCodeJavaScript, access to all dataAPI call (no native node)HTTP RequestWorks with any REST APIConditional routingIF / SwitchBranch based on dataLoop over itemsSplit In BatchesProcess items one at a timeWait/delayWaitPause between stepsMerge dataMergeCombine data from branchesTransform dataSetRename/restructure fieldsScheduleSchedule TriggerCron expressionsWebhookWebhookReceive external HTTP callsRespondRespond to WebhookReturn data to callerError handlingError TriggerCatch workflow errorsSub-workflowExecute WorkflowCall another workflow

Credential Setup Checklist

Before delivering to a client, ensure: All credentials use THEIR API keys (never ours) OAuth tokens are connected to THEIR accounts Webhook URLs point to THEIR n8n instance (or ours if managed) Sensitive data isn't hardcoded in nodes (use credentials store) Test credentials work in production (not just sandbox)

Delivery Checklist

Workflow tested end-to-end with real data Error handling nodes in place Documentation written (trigger, steps, credentials, maintenance) Workflow JSON exported as backup Client can import and run independently Edge cases tested (empty data, API errors, rate limits) Screenshot of working workflow included in delivery

Estimation Guide

ComplexityDescriptionTimePrice RangeSimple2-3 nodes, single trigger→action1-2 hrs$100-300Standard4-8 nodes, branching, transforms2-4 hrs$300-600Complex10+ nodes, multiple APIs, error handling4-8 hrs$600-1,200EnterpriseMulti-workflow, database, custom code8-20 hrs$1,200-3,000 Our speed advantage: Templates cut these times by 40-60%.

n8n Instance Management

Start n8n: eval "$(fnm env)" && fnm use 22 && nohup n8n start > /tmp/n8n.log 2>&1 & Access: http://localhost:5678 Import workflow via API: curl -X POST http://localhost:5678/api/v1/workflows \ -H "Content-Type: application/json" \ -H "X-N8N-API-KEY: $N8N_API_KEY" \ -d @workflow.json Our credentials configured: Twilio API Auth (ID: 2hP5kiyhResadXrF) More to be added per client

Category context

Code helpers, APIs, CLIs, browser automation, testing, and developer operations.

Source: Tencent SkillHub

Largest current source with strong distribution and engagement signals.

Package contents

Included in package

1 Docs

SKILL.md Primary doc