n8n Workflow Templates

Production-ready n8n workflow templates for AI agents. Deploy pre-built automations for webhooks, RSS monitoring, health checks, social metrics, and data bac...

Security Scan

The skill largely matches its stated purpose (n8n workflow templates + management scripts) but contains a few incoherences and undeclared runtime requirements that the user should understand before installing or deploying workflows.

Purpose & Capability

Name, description, scripts, and JSON templates all align: this package provides n8n workflow templates and small bash utilities to deploy/list/manage workflows. Requested binaries (curl, bash) and env vars (N8N_HOST, N8N_API_KEY) are relevant. However, the templates and scripts implicitly rely on additional runtime capabilities not declared (see below), which is an inconsistency with the declared requirements.

Instruction Scope

SKILL.md and README instruct running the included scripts and editing templates, but they do not call out that several templates include executeCommand nodes that will run shell commands (e.g., df, pg_dump, ls) inside the n8n runtime and that code nodes reference environment variables within n8n. The documentation also omits that deploy/list scripts use python3 for JSON parsing/pretty-printing even though python3 is not listed as a required binary. These omissions expand the runtime scope beyond what the skill declares.

Install Mechanism

No install spec — instruction-only with bundled scripts and templates. Nothing is downloaded or executed automatically during installation; files are local and visible for review. This is low install risk.

Credentials

Declared required env vars are only N8N_HOST and N8N_API_KEY (which are appropriate). However: (1) multiple templates reference TELEGRAM_CHAT_ID via n8n's {{$env.VAR}} expression (or otherwise expect platform API credentials) but TELEGRAM_CHAT_ID is not declared in requires.env, (2) templates expect external service credentials (Twitter, LinkedIn, Telegram) to be configured in n8n credentials or environment but the skill metadata doesn't enumerate these, and (3) scripts invoke python3 though python3 is not listed in required binaries. These are mismatches between what is declared and what the templates actually require to function.

Persistence & Privilege

always:false and user-invocable:true. The skill does not request permanent presence or modify other skills. There is no autonomous installation hook or elevated platform privileges requested.

What to consider before installing

This package appears to be what it says (n8n workflow templates + small bash helpers), but before using it: 1) Review each workflow JSON—some templates include executeCommand nodes that will run shell commands (pg_dump, df, ls, etc.) inside the n8n process; only deploy these to a controlled host where running those commands is safe and expected. 2) Ensure python3 is available on the machine where you run the included scripts (deploy/list scripts call python3 for JSON parsing/formatting) or edit the scripts to remove that dependency. 3) The templates reference TELEGRAM_CHAT_ID via environment expressions and expect external platform credentials (Telegram, Twitter, LinkedIn, DB credentials) to be set in your n8n instance; these are not declared as required env vars in the skill metadata—set them intentionally in n8n or replace the placeholders with proper credentials. 4) Do not deploy these templates to shared or multi-tenant n8n instances without auditing the executeCommand nodes and replacing any commands that could leak data or escalate privileges. 5) If you need higher confidence, ask the author for an explicit list of runtime requirements (python3, any n8n env vars like TELEGRAM_CHAT_ID) and confirm whether executeCommand nodes assume access to local databases/files.

Deploy production-ready n8n workflows in seconds. Five battle-tested templates plus management scripts for the complete n8n workflow lifecycle.

Quick Start

# Set your n8n credentials
export N8N_HOST="http://localhost:5678"
export N8N_API_KEY="n8n_api_xxxxx"

# List existing workflows
bash list-workflows.sh

# Deploy a template
bash deploy.sh "$N8N_HOST" "$N8N_API_KEY" templates/webhook-to-telegram.json

Templates

Template	Description	Use Case
webhook-to-telegram.json	Webhook receiver → Telegram alerts	Instant notifications from any service
rss-monitor.json	RSS feed monitoring with filtering	Track blogs, news, releases
health-check.json	HTTP health checks with alerts	Monitor services, APIs, websites
social-metrics.json	Scheduled social media collection	Track followers, engagement
data-backup.json	Automated backup with notifications	Database/file backups

Detailed Usage

Environment Variables

Variable	Required	Default	Description
N8N_HOST	Yes	-	n8n instance URL
N8N_API_KEY	Yes	-	API key from n8n settings

Deployment

bash deploy.sh <n8n-url> <api-key> <template-file> [workflow-name]

Arguments:

• n8n-url - Full URL to n8n instance (e.g., http://10.0.0.120:5678)
• api-key - n8n API key
• template-file - Path to workflow JSON file
• workflow-name (optional) - Override the workflow name

Example:

bash deploy.sh "http://10.0.0.120:5678" "n8n_api_abc123" templates/health-check.json "My Health Monitor"

Listing Workflows

bash list-workflows.sh <n8n-url> <api-key>

Lists all active workflows with their IDs, names, and activation status.

Template Details

webhook-to-telegram

Receives HTTP POST requests, processes JSON payload, sends formatted messages to Telegram.

Webhook URL: ${N8N_HOST}/webhook/workflow-id

Expected payload:

{
  "message": "Alert from my service",
  "level": "warning",
  "timestamp": "2026-02-10T22:00:00Z"
}

Required setup: Configure Telegram bot token and chat ID in the workflow.

rss-monitor

Monitors RSS feeds on schedule, filters by keywords, alerts on new items.

Features:

• Runs every 15 minutes
• Keyword filtering (include/exclude)
• Duplicate detection
• Multi-channel alerts (Telegram, Discord, email)

Required setup: Set RSS feed URL and alert destination.

health-check

Performs HTTP health checks, alerts on failure, tracks response times.

Features:

• Configurable check interval
• Response time thresholds
• Consecutive failure alerts
• Status history tracking

Required setup: Set target URLs and alert channels.

social-metrics

Collects social media metrics on schedule, stores for trending.

Features:

• Daily metric collection
• Multi-platform support (X/Twitter, LinkedIn, etc.)
• Data storage in n8n or external DB
• Trend analysis ready

Required setup: Configure API credentials for each platform.

data-backup

Automated backup workflow with pre/post checks and notifications.

Features:

• Schedule-based execution
• Pre-backup validation
• Backup verification
• Success/failure notifications
• Retention policy enforcement

Required setup: Configure backup source, destination, and credentials.

API Reference

The scripts use n8n REST API v1:

GET  /api/v1/workflows          # List workflows
POST /api/v1/workflows          # Create workflow
GET  /api/v1/workflows/:id      # Get workflow
PUT  /api/v1/workflows/:id      # Update workflow
POST /api/v1/workflows/:id/activate    # Activate
POST /api/v1/workflows/:id/deactivate  # Deactivate

Full API docs: ${N8N_HOST}/api/v1/docs

Customizing Templates

Templates are standard n8n workflow JSON. Edit in n8n UI or modify the JSON directly:

# Copy and customize
cp templates/health-check.json my-custom-check.json
# Edit my-custom-check.json with your favorite editor
bash deploy.sh "$N8N_HOST" "$N8N_API_KEY" my-custom-check.json

Troubleshooting

"Unauthorized" error

• Verify API key is correct
• Check API key hasn't expired in n8n settings

"Connection refused"

• Verify n8n is running
• Check N8N_HOST includes correct port
• Ensure firewall allows connection

Workflow won't activate

• Check all credentials are configured in the workflow
• Verify webhook nodes don't conflict with existing webhooks
• Check n8n execution logs for errors

Template deployment fails

• Validate JSON: python3 -c "import json; json.load(open('template.json'))"
• Check n8n version compatibility (templates tested on v1.0+)

Requirements

• n8n instance v1.0 or later
• API access enabled in n8n settings
• curl and bash
• Network access to n8n instance

See Also

• n8n Documentation: https://docs.n8n.io/
• n8n API Reference: https://docs.n8n.io/api/
• Workflow examples: https://n8n.io/workflows/