Workflow Templates

Tagged with: , , , ,

Tagged with: , , , ,

GitHub PR Deep-Link & Routing Validator (ExecuteCommand + GitHub Comment) 🚀 Quick-Start TL;DR Import the workflow JSON into n8n (Cloud or self-hosted). Create a GitHub Personal Access Token with repo:public_repo (or repo) scope and add it to n8n credentials. Open the “CONFIG - Variables” node and tweak: manifestPath – path to your deep-link manifest (AndroidManifest.xml, Info.plist, etc.). scriptPath – helper script that boots the emulator & checks each route. Enable the workflow. Every push to a PR branch triggers validation and posts a Markdown pass/fail matrix back to the PR. What It Does This workflow delivers an automated, CI-friendly smoke-test of every deep link defined in your mobile app. On each push to an open GitHub PR, it: Clones the PR branch. Runs a lightweight validation script (provided) that spins up an emulator/simulator, attempts to open each declared URI, and records OK/FAIL. Generates a Markdown table summarizing the results. Comments that table in the PR, letting reviewers spot broken schemes at a glance. Who’s It For Mobile teams maintaining Android or iOS deep-link manifests. CI engineers who need a simple, language-agnostic check they can publish to each PR. OSS maintainers wanting a template-library-ready n8n recipe. Requirements | Requirement | Notes | |-------------|-------| | n8n Cloud / CE | Works everywhere; self-hosted users need Docker with Android / Xcode if validating on-runner. | | GitHub Personal Access Token | Used for posting PR comments. | | Emulator-capable runner | Local dev hardware or CI image that can run adb / xcrun simctl. | How It Works GitHub Trigger fires on pull_request → synchronize (i.e., each push to the PR branch). Set (CONFIG - Variables) centralises repo URL, manifest path, script path, timeout, and comment mode. ExecuteCommand clones the repo and calls the validation script. Function converts CLI CSV output into a Markdown table. GitHub node posts (or appends) the results as a comment on the PR. How To Set Up Auth: In n8n, add a GitHub credential with your PAT named “GitHub Personal Access Token”. Import: Settings → Import workflow and paste the JSON above. Edit Config: Double-click CONFIG - Variables and change any default values. Validation Script: Commit scripts/validate_deeplinks.sh into your repo (see sample below). Enable the workflow. Push to any PR branch and watch the comment appear. Sample validate_deeplinks.sh #!/usr/bin/env bash set -e while getopts "m:" opt; do case $opt in m) MANIFEST="$OPTARG" ;; esac done echo "⇨ Parsing deep links from $MANIFEST" rudimentary parser—replace with something smarter for XML/Plist grep -oE 'http[s]?://+' "$MANIFEST" | while read -r uri; do if adb shell am start -W -a android.intent.action.VIEW -d "$uri" >/dev/null 2>&1; then echo "$uri,OK" else echo "$uri,FAIL" fi done How To Customise Multiple manifests:** duplicate the Execute-Command step or extend the script to accept a list. Replace-latest comment:** switch commentMode to replace-latest and update the GitHub node to search for the newest bot comment before editing. Status checks instead of comments:** call the GitHub → “Create Commit Status” endpoint. Add-Ons | Add-On | Idea | |--------|------| | Multi-platform sweep | Loop over Android + iOS manifests and aggregate results. | | Slack/Teams alert | Push failures into your chat of choice via Incoming-Webhook node. | | Parallel device grid | Trigger multiple emulators (API 19 → 34) to catch OS-specific issues. | Use Case Examples Ensure new features don’t break existing URI schemes before merge. Catch mis-typed hosts/paths introduced by junior devs. Baseline check on dependency bumps (e.g., upgrading Navigation libraries). Validate white-label builds that override path segments. Automated QA gate that blocks merge if any link fails. (…and many more!) Troubleshooting Guide | Issue | Possible Cause | Solution | |-------|---------------|----------| | Workflow hangs at “Execute – Validate” | Emulator image isn’t installed | Pre-install SDK & start the emulator in a startup script | | PR comment missing | Token lacks repo scope | Regenerate PAT with proper scopes | | All links marked FAIL | Manifest path incorrect | Update manifestPath in CONFIG | | Command node hits timeout | Huge manifest / slow CI | Increase timeoutSecs in CONFIG | Need a Hand? 🤝 Stuck or want to extend this with multi-platform coverage? WeblineIndia’s automation experts can help. Drop us a note to fine-tune or scale out your n8n workflows — fast.

PDF Digital Signature API with PAdES Compliance Sign PDF documents with legally-compliant digital signatures using X.509 certificates. Supports multiple PAdES signature levels (B, T, LT, LTA) with optional visible stamps. What this workflow does This workflow creates a professional PDF signing service that: Accepts PDF files via webhook API Signs documents using X.509 certificates (PFX format) Returns cryptographically signed PDFs compliant with EU eIDAS standards Supports both visible and invisible signatures Provides multi-language landing pages for easy testing Perfect for contracts, invoices, legal documents, and any PDF requiring digital authentication. Use Cases Legal Document Signing**: Sign contracts and agreements with legally-binding digital signatures Invoice Authentication**: Add cryptographic signatures to invoices for validation Regulatory Compliance**: Meet EU eIDAS and other digital signature requirements Document Archival**: Create long-term valid signatures for permanent storage Automated Signing Pipeline**: Integrate PDF signing into your existing workflows How it Works Workflow Process File Upload: Receives PDF, certificate (PFX), and password via webhook Dependency Check: Automatically installs Java and signing tool if needed Certificate Processing: Extracts certificate and private key from PFX Signature Selection: Routes to appropriate signing method based on level PDF Signing: Signs document using open-pdf-sign tool Response: Returns signed PDF and cleans up temporary files Signature Levels Explained Choose the signature level based on your needs: BASELINE-B (Basic, 2-3 seconds) Fastest option Short-term validity (months) Best for: Testing, internal documents BASELINE-T (Timestamp, 3-5 seconds) - Recommended Includes trusted timestamp Medium-term validity (years) Best for: Contracts, invoices, business documents BASELINE-LT (Long-Term, 5-10 seconds) Includes revocation information Long-term validity (decades) Best for: Banking, healthcare, government BASELINE-LTA (Archival, 8-12 seconds) Maximum compliance level Permanent validity Best for: Critical legal documents Visible vs Invisible Signatures Invisible (default): No visual mark on document Preserves original appearance Signature in document metadata Visible: Shows signature stamp on PDF Includes logo and signature details More reassuring for recipients Add isVisible=true and logoFile to request Customization Change Signature Level Modify the signLevel parameter in your request: B - Basic T - Timestamp (default) LT - Long-term LTA - Archival Customize Visible Signature Upload a logo and add customization parameters to the signing command nodes: --hint "Digitally Signed" # Custom text --page 2 # Sign on page 2 --label-signee "Signed by" # Custom label --label-timestamp "Date" # Custom timestamp label --no-hint # Hide hint row --signature-reason "Contract Approval" # Reason text Adjust File Paths Modify these nodes to change temporary file locations: Write Files : PDF - PDF storage path Write Files : PFX - Certificate storage path Write Files : LOGO - Logo storage path Add Authentication For production use, add authentication before the webhook: Insert HTTP Request node to validate API key Add rate limiting Log signature operations Technical Details What Gets Installed The workflow automatically installs: OpenJDK 11 JRE (Java runtime) curl (for downloading) open-pdf-sign v0.3.0 (signing tool) Certificate Processing Uses OpenSSL to extract: X.509 certificate chain (.pem) Private key (.pem) All files use timestamped names to prevent conflicts. Security Features Automatic cleanup of sensitive files after each request No persistent storage of certificates or keys HTTPS recommended for production Supports password-protected certificates Standards Compliance Implements ETSI EN 319 142 PAdES standards: EU eIDAS regulation compliant Validates in Adobe Acrobat Reader Verifiable at EU DSS Demo webapp FAQ Q: Where do I get certificates? A: For testing, use free certificates from Codegic. For production, purchase from DigiCert, GlobalSign, or Sectigo. Q: What PDF sizes are supported? A: Up to 50MB by default. Adjust n8n configuration for larger files. Q: Can I sign multiple PDFs at once? A: Call the API once per PDF, or modify the workflow to accept multiple files. Q: Will signatures work in Adobe Reader? A: Yes, if using certificates from trusted CAs. Self-signed certificates will show warnings. Q: How do I verify signed PDFs? A: Open in Adobe Acrobat Reader and check the signature panel, or use the EU DSS validation tool webapp. Q: Can I use this commercially? A: Yes, the workflow is free for personal and commercial use. Support Documentation**: See workflow sticky notes for detailed information Tool Source**: open-pdf-sign on GitHub Standards**: ETSI PAdES specifications Community**: n8n Community Forum License: Free for personal and commercial use Dependencies: OpenJDK 11, OpenSSL, curl, open-pdf-sign v0.3.0 (Apache 2.0)

🌡 IoT Sensor Data Cleaner + InfluxDB Logger (n8n | Webhook | Function | InfluxDB) This workflow accepts raw sensor data from IoT devices via webhook, applies basic cleaning and transformation logic, and writes the cleaned data to an InfluxDB instance for time-series tracking. Perfect for renewable energy sites, smart farms and environmental monitoring setups using dashboards like Grafana or Chronograf. ⚡ Quick Implementation Steps Import the workflow JSON into your n8n instance. Edit the Set Config node to include your InfluxDB credentials and measurement name. Use the webhook URL (/webhook/sensor-data) in your IoT device or form to send sensor data. Start monitoring your data directly in InfluxDB! 🎯 Who’s It For IoT developers and integrators. Renewable energy and environmental monitoring teams. Data engineers working with time-series data. Smart agriculture and utility automation platforms. 🛠 Requirements | Tool | Purpose | |------|---------| | n8n Instance | For automation | | InfluxDB (v1 or v2) | To store time-series sensor data | | IoT Device or Platform | To POST sensor data | | Function Node | To filter and transform data | 🧠 What It Does Accepts JSON-formatted sensor data via HTTP POST. Validates the data (removes invalid or noisy readings). Applies transformation (rounding, timestamp formatting). Pushes the cleaned data to InfluxDB for real-time visualization. 🧩 Workflow Components Webhook Node:** Exposes an HTTP endpoint to receive sensor data. Function Node:** Filters out-of-range values, formats timestamp, rounds data. Set Node:** Stores configurable values like InfluxDB host, user/pass, and measurement name. InfluxDB Node:** Writes valid records into the specified database bucket. 🔧 How To Set Up – Step-by-Step Import Workflow: Upload the provided .json file into your n8n workspace. Edit Configuration Node: Update InfluxDB connection info in the Set Config node: influxDbHost, influxDbDatabase, influxDbUsername, influxDbPassword measurement: What you want to name the data set (e.g., sensor_readings) Send Data to Webhook: Webhook URL: https://your-n8n/webhook/sensor-data Example payload: { "temperature": 78.3, "humidity": 44.2, "voltage": 395.7, "timestamp": "2024-06-01T12:00:00Z" } View in InfluxDB: Log in to your InfluxDB/Grafana dashboard and query the new measurement. ✨ How To Customize | Customization | Method | |---------------|--------| | Add more fields (e.g., wind_speed) | Update the Function & InfluxDB nodes | | Add field/unit conversion | Use math in the Function node | | Send email alerts on anomalies | Add IF → Email branch after Function node | | Store in parallel in Google Sheets | Add Google Sheets node for hybrid logging | ➕ Add‑ons (Advanced) | Add-on | Description | |--------|-------------| | 📊 Grafana Integration | Real-time charts using InfluxDB | | 📧 Email on Faulty Data | Notify if voltage < 0 or temperature too high | | 🧠 AI Filtering | Add OpenAI or TensorFlow for anomaly detection | | 🗃 Dual Logging | Save data to both InfluxDB and BigQuery/Sheets | 📈 Use Case Examples Remote solar inverter sends temperature and voltage via webhook. Environmental sensor hub logs humidity and air quality data every minute. Smart greenhouse logs climate control sensor metrics. Edge IoT devices periodically report health and diagnostics remotely. 🧯 Troubleshooting Guide | Issue | Cause | Solution | |-------|-------|----------| | No data logged in InfluxDB | Invalid credentials or DB name | Recheck InfluxDB values in config | | Webhook not triggered | Wrong method or endpoint | Confirm it is a POST to /webhook/sensor-data | | Data gets filtered | Readings outside valid range | Check logic in Function node | | Data not appearing in dashboard | Influx write format error | Inspect InfluxDB log and field names | 📞 Need Assistance? Need help integrating this workflow into your energy monitoring system or need InfluxDB dashboards built for you? 👉 Contact WeblineIndia | Experts in workflow automation and time-series analytics.

Tagged with: , , , ,

Tagged with: , , , ,

Tagged with: , , , ,

Tagged with: , , , ,

Tagged with: , , , ,

🧑‍💻 Description This workflow demonstrates how to take structured data (e.g., Name, Business, Address) and automatically fill a PDF form (IRS W-9) using PDF.co inside n8n. The workflow extracts values from a data source (e.g., Set node, database, or webhook), maps those values to fields in a PDF template, and generates a completed PDF. This can be adapted for contracts, invoices, HR forms, or any standardized documents that need automation. By chaining additional nodes, you can also store completed PDFs in Google Drive/Dropbox, email them to recipients, or route them into CRM/ERP systems. Disclaimer: this template can only be used on self-hosted n8n instances ⚙️ Setup Instructions 1️⃣ Prepare Your Data Add a Set node (or connect to your data source such as Google Sheets, Airtable, or a webhook). Define fields like: Name Business Address CityState These fields will map directly to form fields in the PDF. 2️⃣ Connect PDF.co Create a free account at PDF.co Copy your API Key from the dashboard In n8n → Credentials → New → PDF.co API Paste your API Key → Save In the PDF.co node, select your credential and choose the Fill a PDF Form operation Map each field in your dataset to the corresponding PDF form field (e.g., Name → Line 1 on the W-9). 📄 Example Form This template uses the official IRS W-9 PDF: https://www.irs.gov/pub/irs-pdf/fw9.pdf Mapped fields include: Name → Line 1 Business → Line 2 Address + City/State → Address block You can expand this by mapping additional fields such as Tax Classification, Exemptions, TIN, and Signature. 🎛️ Customization Guidance Different PDFs**: Swap the W-9 for any contract, invoice, or onboarding form your business uses. Dynamic Data Sources**: Replace the Set node with Google Sheets, Airtable, or API/Webhook inputs to pull live data. Automated Delivery**: After filling the form, use Email or Slack nodes to send PDFs directly to recipients. Document Storage**: Save completed PDFs automatically to Google Drive, Dropbox, or AWS S3. Bulk Processing**: Loop through rows of a dataset (e.g., customer list) to generate multiple personalized PDFs at once. 📬 Contact Need help customizing this workflow for contracts, invoices, or HR forms? 📧 robert@ynteractive.com 🔗 Robert Breen 🌐 ynteractive.com

Description: Automatically detect and flag high-value sales orders as VIP in Zoho CRM using this intelligent n8n workflow. Ideal for eCommerce platforms, sales automation tools, or ERP systems, this automation template listens to incoming order data via webhook, checks if the sales order amount exceeds a set threshold (₹10,000 or $10,000), and updates the CRM with a VIP tag in real time. Whether you're scaling your operations or building a smart sales pipeline, this template ensures no important order goes unnoticed—real-time tagging of premium clients made easy. What This Template Does (Step-by-Step) 🔔 Webhook Trigger (Sales Order Intake) Receives real-time POST requests from your e-commerce, POS, or order management system Captures order details, including total value ($json.body.salesorder.total) ⚖️ High-Value Condition Check Evaluates whether the sales order value exceeds a custom threshold (default: 10,000) If order total > 10,000, continues the workflow Otherwise, halts execution (no CRM action) 🏷️ Zoho CRM VIP Tagging Automatically creates or updates a purchase order record in Zoho CRM Tags the record with “VIP Order” to flag it for priority handling Uses OAuth2-secured integration with your Zoho account Required Integrations: ✅ Zoho CRM (OAuth2 credentials) ✅ Any external sales/order system with webhook support Use Cases: 💰 B2B sales teams tracking large enterprise orders 🛍️ D2C brands prioritizing premium customers for fulfillment or loyalty 🔁 CRM automation agencies building smart workflows for clients 🧑‍💼 Sales managers setting up internal escalations or alerts for VIP deals Key Features: ⚙️ No-code CRM automation using n8n 🔒 Secure Zoho CRM integration via OAuth2 ⏱️ Instant tagging for faster follow-up 🧠 Configurable logic (change the threshold easily!) 📈 Scalable for thousands of incoming orders