Workflow Templates

🧩 Short Summary Proactively alert to service endpoint changes and pod/container issues (Pending, Not Ready, Restart spikes) using Prometheus metrics, formatted and sent to Slack. 🗂️ Category DevOps / Monitoring & Observability 🏷️ Tags kubernetes, prometheus, slack, alerting, sre, ops, kube-state-metrics ✅ Prerequisites Prometheus scraping kube-state-metrics v2.x. Slack App or Incoming Webhook (channel access). n8n instance with outbound access to Prometheus & Slack. 🔑 Required Credentials in n8n Slack: Bot OAuth (chat:write) or Incoming Webhook URL. (Optional) Prometheus Basic Auth (if your Prometheus needs it). 🧠 What This Template Does Detects pods stuck in Pending (scheduling problems like taints/affinity/capacity). Detects containers Not Ready (readiness probe failures). Detects container restart spikes over a sliding window (default 5 minutes). Detects service discovery changes (endpoint count diffs current vs previous snapshot). Sends clean, emoji-enhanced Slack alerts with pod/namespace/service context. Outputs a 5-minute summary block to reduce noise. 📣 Slack Message Style (examples)

This n8n workflow ensures instant notifications to parents and staff during school emergencies. It processes incoming alerts via webhooks, filters active emergencies, and sends notifications through email and Slack. Key Features Instant Alerts**: Triggers notifications immediately upon detecting emergencies. Multi-Channel**: Sends alerts via email and Slack for broad reach. Automated Filtering**: Identifies and processes only active emergency alerts. Reliable Delivery**: Ensures notifications reach parents and staff swiftly. No Action Needed**: Skips inactive alerts without further processing. Workflow Process Webhook Trigger: Receives POST requests with emergency data. Filter Emergency Alerts: Checks and validates active emergency alerts. Send Email Alert: Delivers email notifications to parents and staff. Send Slack Alert: Posts real-time messages to a Slack channel. No Action for Inactive: Ignores and stops for inactive alerts. Setup Instructions Import Workflow**: Load the workflow into n8n using the import feature. Configure Webhook**: Set up a webhook URL to receive emergency data. Set Up Notifications**: Add email (e.g., Gmail) and Slack credentials. Activate**: Save and enable the workflow in n8n. Test**: Simulate an alert to ensure notifications work. Requirements n8n Instance**: Hosted or cloud-based n8n environment. Webhook Source**: System to send emergency data via POST. Email Service**: SMTP setup for email alerts. Slack Integration**: Configured Slack workspace for alerts. Customization Options Add Channels**: Include SMS or other platforms for alerts. Adjust Filters**: Modify criteria for active alerts. Custom Messages**: Tailor email/Slack content for clarity.

This is an n8n template that Automate welcome emails with discount codes via Mailchimp and Gmail Who's it for Perfect for e-commerce businesses, SaaS companies, course creators, and service providers who want to automatically nurture new subscribers with personalized welcome emails and discount codes. If you're looking to boost conversions from your website signup forms and create a professional onboarding experience, this workflow is your solution. How it works This workflow creates a seamless subscriber onboarding process: Webhook receives signup data from your website form (name, email, timestamp, source) Mailchimp integration automatically adds the subscriber to your email list with their name Gmail sends personalized welcome email with a discount code and branded content Error handling ensures the welcome email sends even if Mailchimp fails The workflow is triggered instantly when someone submits your website signup form, creating a professional first impression that can significantly improve customer engagement and conversion rates. How to set up Requirements Mailchimp account** with an active audience/list Gmail account** with OAuth2 access Website or landing page with a signup form Basic HTML/CSS knowledge** for email customization (optional) Step-by-step setup 1. Configure Mailchimp Integration Create or identify your Mailchimp audience Replace YOUR_MAILCHIMP_LIST_ID with your actual list ID Add your Mailchimp API credentials in n8n Set up any custom merge fields you need (FNAME is included by default) 2. Set Up Gmail Credentials Add your Gmail OAuth2 credentials in n8n Ensure the sending email account has appropriate permissions Test email delivery to avoid spam folder issues 3. Customize the Welcome Email Replace [Your Business Name] with your actual business name Update the discount code (WELCOME15) with your preferred offer Modify the shop URL (https://your-website.com/shop) to your store. Update social media links with your actual profiles Customize colors, fonts, and branding to match your business. 4. Deploy Your Webhook Copy the webhook URL from the n8n workflow Add this URL to your website signup form as the POST endpoint Ensure your form sends JSON data with name and email fields 5. Test the Complete Flow Submit a test signup through your website form Verify the contact appears in Mailchimp Check that the welcome email arrives with proper personalization How to customize the workflow Advanced Email Personalization Dynamic content blocks: Add conditional sections based on signup source or user preferences Custom merge fields: Capture additional data like company name, phone number, or interests in Mailchimp Segmented messaging: Create different email templates for different subscriber types Multi-language support: Detect user language from form data and send localized emails Webhook Integration Examples Google Forms Integration: Use Google Apps Script to POST form responses to your n8n webhook Map form fields to the expected JSON structure (name, email, source) Typeform Integration: Configure Typeform webhooks in Connect panel Set payload to include question responses in the required format Custom HTML Forms: // Example form submission code fetch('YOUR_N8N_WEBHOOK_URL', { method: 'POST', headers: {'Content-Type': 'application/json'}, body: JSON.stringify({ name: document.getElementById('name').value, email: document.getElementById('email').value, source: 'website' }) }); WordPress Contact Form 7: Use CF7 hooks to send form data to your webhook endpoint Install REST API plugins for seamless integration Workflow Logic Enhancements Data validation: Add If nodes to check email format and required fields before processing Duplicate prevention: Query Mailchimp first to avoid adding existing subscribers Source-based routing: Send different welcome emails based on signup source (blog, product page, etc.) Lead scoring: Assign scores based on signup source and send to appropriate lists Follow-up sequences: Add Wait nodes to create multi-step email campaigns Advanced Integrations CRM sync: Connect to Salesforce, HubSpot, or Pipedrive to create leads automatically Analytics tracking: Log conversions to Google Sheets or send events to Google Analytics Slack notifications: Alert your team about high-value signups or VIP customers SMS follow-up: Add Twilio integration for multi-channel welcome sequences Troubleshooting Common Issues and Solutions Emails going to spam folder: Configure SPF and DKIM records for your sending domain Use Gmail's "Send as" feature to authenticate your sending address Start with low volume and gradually increase to build sender reputation Include unsubscribe links and proper email headers Mailchimp API errors: Check your API key permissions and rate limits Verify the list ID is correct (found in Audience settings) Ensure required fields are properly mapped Review Mailchimp's compliance requirements for your region Webhook not triggering: Test the webhook URL directly using tools like Postman Check that your form sends POST requests with proper Content-Type headers Verify JSON payload structure matches expected format Review n8n execution logs for error details Personalization not working: Confirm form field names match the n8n node references Check that data is properly passed between workflow nodes Test with sample data to isolate mapping issues Use n8n's data inspection tools to debug payload structure Performance Optimization High-volume handling: Consider using Mailchimp's batch operations for multiple signups Implement queue systems for processing during traffic spikes Monitor workflow execution times and optimize slow nodes Set up error notifications to catch issues quickly Delivery improvements: Use dedicated email services like SendGrid or Mailgun for better deliverability Implement email warmup procedures for new sending domains A/B test subject lines and send times for better engagement Monitor bounce rates and remove invalid emails promptly.

🧾 Overview This n8n workflow automates the process of fetching user data from an API, verifying its validity, transforming the response, and then saving it to Google Sheets for team collaboration. Additionally, it generates a CSV backup file of the same data for offline access or external integrations. Perfect for developers, analysts, or teams who want an automated, no-code data ingestion and backup solution. ⚙️ Key Features 🔌 Fetches data from any REST API endpoint (e.g., RandomUser API) ✅ Validates successful API responses before processing 🧠 Transforms JSON response into simple key-value pairs (name and country) 📊 Appends data directly into Google Sheets 💾 Generates a downloadable CSV backup file 🧱 Modular design — easily customizable and extendable 🧱 Workflow Steps 1. Start Workflow Manually (Manual Trigger Node) The workflow starts manually by clicking Execute Workflow. You can later replace this with a Cron or Webhook trigger for automation. 2. Fetch User Data from API (HTTP Request Node) Makes an HTTP GET request to the configured API endpoint defined in the environment variable BASE_URL. Example: https://randomuser.me/api/?results=10 This node fetches raw user data in JSON format. 3. Verify API Response Success (If Node) Checks if the API response returned an HTTP 200 status code. ✅ If status = 200 → Continue processing data ❌ If status ≠ 200 → Trigger Stop and Error node to halt execution This prevents saving invalid or failed responses. 4. Transform API Data to Name and Country (Function Node) Formats the raw JSON data to extract key details (name and country) from each user record. Input Example: { "results": [ { "name": { "first": "John", "last": "Doe" }, "location": { "country": "United States" } } ] } Output Example: [ { "name": "John Doe", "country": "United States" } ] This step makes the data compatible with Google Sheets. 5. Append Data to Google Sheets (Google Sheets Node) Appends the formatted data to your specified Google Sheet. Environment Variables Required: GOOGLE_SHEET_ID → ID of your target Google Sheet Configuration: Range:** A:B Columns:** Name (A) and Country (B) Example Google Sheet: | Name | Country | | ---------- | ------------- | | John Doe | United States | | Jane Smith | Canada | 6. Create CSV Backup File (Spreadsheet File Node) Generates a .csv file named users_backup_export.csv containing all saved user data. This file can be: Stored locally Sent via email Uploaded to cloud storage (e.g., Google Drive, Dropbox) Used for external analytics tools ⚠️ Error Handling If the API response is invalid (non-200), the Stop on API Failure node halts the workflow and logs the error: > ❌ API request failed — status code not 200. Workflow stopped. This ensures only valid data is stored. 🧰 Setup Instructions Add Environment Variables: BASE_URL=https://randomuser.me/api/?results=10 GOOGLE_SHEET_ID=<your_google_sheet_id> Add Credentials: Google Sheets OAuth2 credentials API (if authentication is required) Run Workflow: Start manually or configure a Cron node to run periodically Check Output: Data appears in your Google Sheet CSV file is created in n8n’s file system 🧩 Customization Options | Goal | How to Modify | | ----------------------- | ----------------------------------------------------------------- | | Change API fields | Edit Transform API Data function to extract desired fields | | Add columns | Expand output object and update Google Sheets range (e.g., A:D) | | Automate execution | Replace manual trigger with a Cron or Webhook node | | Filter users | Add an If node after transformation to include/exclude data | | Send email notification | Add Gmail or SMTP node after CSV creation | 🧠 Example Use Case A recruiter fetches random candidate data daily from an HR API. Data (Name + Country) is saved to Google Sheets. A CSV backup is automatically generated for offline analysis. ✅ Benefits Hands-free automated data collection Centralized storage in Google Sheets for team access Built-in CSV export for reporting and backups Protects data integrity with API validation Fully customizable for any API format ✨ Tip: Add a Slack or Telegram node at the end to notify your team whenever new data is added successfully!

Odoo Customers API – Export to JSON or Excel provides a simple way to fetch customer records from your Odoo database and get them back either as a structured JSON response or a downloadable Excel (.xlsx) file. ⚙️ What it does Listens for HTTP GET requests on the endpoint /api/v1/get-customers. Checks for the required name parameter and builds a search filter automatically. Queries the res.partner model to return only customer contacts (is_company = false). Delivers results in JSON by default, or as an Excel (.xlsx) export when response_format=excel is included. 📥 Parameters name — Required. Used for partial matching on customer names (via Odoo’s Like filter). response_format — Optional. Accepts json (default) or excel. 🔗 Examples Excel Example GET /api/v1/get-customers?name=Demo&response_format=excel JSON Example GET /api/v1/get-customers?name=Demo&response_format=json 🧩 Default fields display_name, name, email, phone, mobile, parent_id, company_id, country_code, country_id 🛠️ Setup Open the Odoo node and connect your Odoo API credentials. Adjust the fieldsList in the node if you want to include more data fields (e.g., address, city, or VAT). Trigger the flow from its webhook URL or run it manually inside n8n to test the output. 💡 Notes Built and tested for n8n v1.108.2+

Swap Tokens with Li.Fi The growing popularity of agentic payments has lead to the development of protocols like x402 where agents and humans can pay for internet resources over standard http protocols using stablecoins. This workflow lets you run your own swap relayer where callers can provide an x402-compatible payment header and a desired destination network to instantly receive gas tokens. This setup is trust minimized - user's have the following guarantees: They will be the receiver of the swap. Only the amount of tokens the authorized will be swapped. Setup In order to run this relayer workflow, you will need an account on 1Shot API. You must then import the 1Shot Gas Station contract into your business for any chain you wish to support with your relayer. Next, follow the directions in the worflow sticky notes to update the Payment Configs for the tokens you wish to support swaps for. Lastly, distrubute your webhook api endpoint to your users.

Marker.io to ServiceNow Integration Automatically create ServiceNow incidents with full technical context when bugs are reported through Marker.io 🎯 What this template does This workflow creates a seamless bridge between Marker.io and ServiceNow, your IT service management platform. Every issue submitted through Marker.io's widget automatically becomes a trackable incident in ServiceNow, complete with technical details and visual context. This ensures your IT team can track, prioritize, and resolve bugs efficiently within their existing ITSM workflow. When a bug is reported, the workflow: Captures the complete Marker.io webhook payload Formats all technical details and metadata Creates a new incident in ServiceNow with the reporter information Includes comprehensive technical context and Marker.io links Preserves screenshots, browser info, and custom data ✨ Benefits Automated ticket creation** - No manual data entry required Complete context** - All bug details transfer automatically Faster triage** - IT teams see issues immediately in ServiceNow Better tracking** - Leverage ServiceNow's incident management capabilities Rich debugging info** - Browser, OS, and screenshot details preserved 💡 Use Cases IT Service Desks**: Streamline bug reporting from end users Development Teams**: Track production issues with full technical context QA Teams**: Convert test findings directly into trackable incidents Support Teams**: Escalate customer-reported bugs to IT with complete details 🔧 How it works N8N Webhook receives Marker.io bug report data JavaScript node formats and extracts relevant information ServiceNow node creates incident with formatted details Incident includes title, description, reporter info, and technical metadata Links preserved to both public and private Marker.io views The result is a fully documented ServiceNow incident that your IT team can immediately action, with all the context needed to reproduce and resolve the issue. 📋 Prerequisites Marker.io account** with webhook capabilities ServiceNow instance** with API access enabled ServiceNow credentials** (username/password or OAuth) Appropriate ServiceNow permissions** to create incidents 🚀 Setup Instructions Import this workflow into your n8n instance Configure the Webhook: Copy the production webhook URL after saving Add to Marker.io: Workspace Settings → Webhooks → Create webhook Select "Issue Created" as the trigger event Set up ServiceNow credentials: In n8n, create new ServiceNow credentials Enter your ServiceNow instance URL Add username and password for a service account Test the connection Customize field mappings (optional): Modify the JavaScript code to map additional fields Adjust priority mappings to match your ServiceNow setup Add custom field mappings as needed Test the integration: Create a test issue in Marker.io Verify the incident appears in ServiceNow Check that all data transfers correctly 📊 Data Captured ServiceNow Incident includes: Short Description**: Issue title from Marker.io Description** containing: 🐛 Issue title and ID 📊 Priority level and issue type 📅 Due date (if set) 📝 Full issue description 🖥️ Browser version and details 💻 Operating system information 🌐 Website URL where issue occurred 🔗 Direct links to Marker.io issue (public and private) 📦 Any custom data fields 📷 Screenshot URL with proper formatting 🔄 Workflow Components Webhook Node**: Receives Marker.io POST requests Code Node**: Processes and formats the data using JavaScript ServiceNow Node**: Creates the incident using ServiceNow API → Read more about Marker.io webhook events 🚨 Troubleshooting Webhook not triggering: Verify webhook URL is correctly copied from n8n to Marker.io Check that "Issue Created" event is selected in Marker.io webhook settings Ensure webhook is set to "Active" status in Marker.io Test with Marker.io's webhook tester feature Check n8n workflow is active and not in testing mode ServiceNow incident not created: Verify ServiceNow credentials are correct and have not expired Check that the service account has permissions to create incidents Ensure ServiceNow instance URL is correct (include https://) Test ServiceNow connection directly in n8n credentials settings Check ServiceNow API rate limits haven't been exceeded Missing or incorrect data: Screenshot URL broken: The workflow already handles URL formatting, but verify Marker.io is generating screenshots Custom data missing: Ensure custom fields exist in Marker.io before sending Due date formatting issues: Check your ServiceNow date format requirements JavaScript errors in Format node: Check webhook payload structure hasn't changed in Marker.io updates Verify all field paths match current Marker.io webhook schema Use n8n's data pinning to debug with actual webhook data Check for undefined values when optional fields are missing Connection issues: ServiceNow timeout: Increase timeout in node settings if needed SSL/Certificate errors: Check ServiceNow instance SSL configuration Network restrictions: Ensure n8n can reach your ServiceNow instance Authentication failures: Regenerate ServiceNow credentials if needed Testing tips: Use n8n's "Execute Workflow" with pinned test data Enable webhook test mode in Marker.io for safe testing Check ServiceNow incident logs for detailed error messages Monitor n8n execution logs for specific failure points

This n8n workflow automates the end-to-end proof-of-delivery process for logistics operations. It ingests POD data via webhook—including driver signatures, delivery photos, and GPS coordinates—performs AI-driven verification for package integrity and authenticity, updates ERP systems with delivery status, triggers automated invoicing for verified cases, and handles disputes by creating evidence-backed tickets and alerting teams. Designed for seamless integration, it minimizes errors in billing and reconciliation while accelerating resolution for mismatches. Benefits Reduced Manual Effort:** Automates verification and status updates, cutting processing time from hours to minutes. Enhanced Accuracy:** AI analysis detects damages, location discrepancies, and signature fraud with high confidence scores, preventing billing disputes. Faster Revenue Cycle:** Instant invoicing for verified deliveries improves cash flow and reduces DSO (Days Sales Outstanding). Proactive Dispute Management:** Generates high-priority tickets with linked evidence, enabling quicker resolutions and lower escalation costs. Audit-Ready Traceability:** Logs all decisions, AI outputs, and actions for compliance with logistics standards like ISO 9001. Scalability:** Handles high-volume deliveries without proportional staff increases, supporting growth in e-commerce fulfillment. Useful for Which Industry Logistics & Supply Chain:** Ideal for 3PL providers, freight forwarders, and courier services managing last-mile deliveries. E-Commerce & Retail:** Supports platforms like Amazon or Shopify sellers verifying customer receipts and automating returns. Manufacturing & Distribution:** Streamlines B2B shipments with ERP integrations for just-in-time inventory. Pharmaceuticals & Healthcare:** Ensures tamper-evident deliveries with photo verification for cold-chain compliance. Food & Beverage:** Tracks perishable goods with damage detection to maintain quality assurance. Workflow Process Webhook Intake:** Receives POD submission (driver ID, signature image, delivery photo, recipient, GPS) via POST/GET. Input Validation:** Checks for required fields; branches to error if incomplete. Parallel AI Verification:** AI Vision (OpenAI GPT-4): Analyzes photo for package condition, location match, and damage. Signature Validation: AI checks legitimacy, handwritten authenticity, and completeness. Merge & Decide:** Consolidates results with confidence scoring; routes to verified (true) or dispute (false). Verified Path:** Update ERP: POSTs status, timestamps, and coordinates to delivery system. Trigger Invoicing: Generates billable invoice with POD reference via billing API. Success Response: Returns confirmation to caller. Dispute Path:** Create Ticket: POSTs high-priority support ticket with evidence (images, scores). Alert Team: Notifies dispute team via email/Slack with issue summary and ticket link. Dispute Response: Returns status and next steps to caller. Error Handling:** Returns detailed feedback for invalid inputs. Setup Instructions Import Workflow: Paste JSON into n8n Workflows → Import from Clipboard. Configure Webhook: Set URL for POD submissions (e.g., from mobile apps); test with sample POST data. AI Setup: Add OpenAI API key to vision/signature nodes; specify GPT-4 model. Integrate Systems: Update ERP/billing URLs and auth in update/trigger nodes (e.g., https://your-erp.com/api). Dispute Config: Link support API (e.g., Zendesk) and notification service (e.g., Slack webhook). Threshold Tuning: Adjust confidence scores in decision node (e.g., >85% for auto-approve). Test Run: Execute manually with valid/invalid POD samples; verify ERP updates and ticket creation. Prerequisites n8n instance (v1.50+) with webhook and HTTP request nodes enabled. OpenAI API access for GPT-4 vision (image analysis credits required). ERP/billing APIs with POST endpoints and authentication (e.g., OAuth tokens). Support ticketing system (e.g., Zendesk, Jira) for dispute creation. Secure image storage (e.g., AWS S3) for POD uploads. Basic API testing tools (e.g., Postman) for endpoint validation. Modification Options Add OCR for recipient name extraction from photos in validation step. Integrate geofencing APIs for automated location alerts in AI vision. Support multi-signature PODs for group deliveries by expanding parallel branches. Add partial invoicing logic for mixed verified/disputed items. Incorporate blockchain for immutable POD records in high-value shipments. Extend alerts to SMS via Twilio for on-the-road driver notifications. Build analytics export to Google Sheets for delivery success rates.

Website & API Health Monitoring System with HTTP Status Validation How it works Performs HTTP health checks on websites and APIs with automatic health status validation Checks HTTP status codes and analyzes JSON responses for common health indicators Returns detailed status information including response times and health status Implements conditional logic to handle different response scenarios Perfect for monitoring dashboards, alerts, and automated health checks Set up steps Deploy the workflow and activate it Get the webhook URL from the trigger node Configure your monitoring system to call the webhook endpoint Send POST requests with target URLs for health monitoring Receive JSON responses with health status, HTTP codes, and timestamps Usage Send POST requests to the webhook URL with target URL parameter Optionally configure timeout and status expectations in request body Receive JSON responses with health status, HTTP codes, and timestamps Perfect for monitoring dashboards, alerts, and automated health checks Use with external monitoring tools like Nagios, Zabbix, or custom dashboards Set up scheduled monitoring calls for continuous health validation Example request: Send POST with {"url": "https://your-site.com", "timeoutMs": 5000} Success response returns: {"ok": true, "statusCode": 200, "healthStatus": "ok"} Failure response returns: {"ok": false, "error": "Health check failed", "statusCode": 503} Benefits Proactive monitoring to identify issues before they impact users Detailed diagnostics with comprehensive health data for troubleshooting Integration ready - works with existing monitoring and alerting systems Customizable timeout settings, expected status codes, and health indicators Scalable solution to monitor multiple services with single workflow endpoint Use Cases E-commerce platforms: Monitor payment APIs, inventory systems, user authentication Microservices: Health validation for distributed service architectures API gateways: Endpoint monitoring with response time validation Database connections: Track connectivity and performance metrics Third-party integrations: Monitor external API dependencies and SLA compliance Target Audience DevOps Engineers implementing production monitoring System Administrators managing server uptime Site Reliability Engineers building monitoring systems Development Teams tracking API health in staging/production IT Support Teams for proactive issue detection

This n8n template demonstrates how to automatically generate personalized calendar views in Baserow, based on a chosen date field and a filter. Having a personalized view with only information that is relevant to you makes it easy to integrate with external calendar tools like Outlook or Google Calendar. Use cases are many: Task management (deadlines per staff member) Customer management (appointments per customer) Inventory management (delivery dates per supplier) Good to know You only need a Date field (e.g., a task deadline, due date, appointment date) and a Link to table field (e.g., a customer, employee, product) to make this work. The generated calendar views can be shared as .ics files and imported into any external calendar application. Authentication is done through a JWT token constructed from your Baserow username and password. How it works Set Baserow credentials**: Allows you to enter your Baserow credentials (username + password) and the API host path. The host is by default https://api.baserow.io, but you can change this in case you are self-hosting. The information is required to generate a JWT token that authenticates all future HTTP request nodes to create and configure the view. Create a token**: Generates a JWT token based on the information provided in the previous node. Set table and field ids**: Stores the generated JWT token and allows you to enter the ids of the tables and fields required to run the automation. Get all records from filter table** Gets all the records from the table you want to filter on. This is the table that has a Link to table field referencing the table with the Date field. Each record from this table will get it’s own view. Some examples: Customers, Employees and Products. Create new calendar view** Calls the API endpoint /api/database/views/table/{table_id} to create a new view. Check the Baserow API documentation for further details. The body of this requests configures the new view by setting among other things a name and the date field Create filter** Calls the API endpoint /api/database/views/{view_id}/filters/ to set a filter on the view so that it only shows the records that are relevant. This filter is based on the Link to table field that is set in earlier steps. Check the Baserow API documentation for further details. Set background color** Calls the API endpoint /api/database/views/{view_id}/decorations/ to set a a color on the background or left side of each item. By default, the color is based on a single select field, but it is also possible to use a condition. Check the Baserow API documentation for further details. Share the view** Calls the API endpoint /api/database/views/{view_id} to update the current view. It updates the ical_public property to true so that an ics link is created. Check the Baserow API documentation for further details. Update the url’s** Updates all the records in the table you want to filter on to fill in the url to the new generated view and the url to the ics file. This can be useful if you want to build an application on top of your database. How to use The Manual Trigger node is provided as an example, but you can replace it with other triggers such as a webhook The included Baserow SOP template works perfectly as a base schema to try out this workflow. Requirements Baserow account (cloud or self-hosted) A Baserow database with a table that has a Date field and a Link to Table field Customising this workflow Change the date field used to generate the calendars (e.g., deadline → appointment date). Adjust the filters to match your context (staff, customer, product, etc.). Configure which fields are shown using the /api/database/view/{view_id}/field-options/ endpoint. Check the Baserow API documentation for further details. Add or remove optional steps such as coloring by status or sharing the ics feed. Extend the workflow to notify staff when a new view has been created for them.

🌐 Crypto + FX Micro-API (Webhook JSON) 📌 Overview Spin up a tiny, serverless-style API from n8n that returns BTC/ETH prices & 24h changes plus USD→EUR and USD→NGN from public, no-key data sources. Ideal for dashboards, low-code apps, or internal tools that just need a simple JSON feed. ⚙️ How it works Webhook (GET /crypto-fx) — entrypoint for your client/app. HTTP: ExchangeRate-API — USD-base FX rates (no API key). HTTP: CoinGecko — BTC/ETH prices + 24h % change (no API key). Merge — combines payloads. Code (v2) — shapes a clean JSON: btc.price, btc.change_24h eth.price, eth.change_24h usd_eur, usd_ngn, ts (ISO timestamp) Respond to Webhook — returns the JSON with HTTP 200. 🛠 Setup Guide 1) Webhook path & URL In the Webhook node, confirm HTTP Method = GET and Path = crypto-fx. Use the Test URL while building; switch to Production URL for live usage. 2) Test the endpoint Curl: curl -s https://<your-n8n-host>/webhook/crypto-fx Browser / fetch(): fetch('https://<your-n8n-host>/webhook/crypto-fx') .then(r => r.json()) .then(data => console.log(data)) 3) Response mapping (already wired) Respond to Webhook → Response Body is set to {{$json}}. The Code node outputs the exact JSON structure shown above, so no extra mapping is required. 🔐 Security (recommended) Add a Webhook Secret (query header check in Code node) or IP allowlist via your reverse proxy. If embedding in public sites, proxy through your backend and apply rate-limit/cache headers there. 🚀 Usage ideas Frontend dashboards (Chart.js, ECharts). HomeAssistant / Node-RED info panels. Google Apps Script to store the JSON into Sheets on a timer. 🎛 Customization More coins: extend CoinGecko ids= (e.g., bitcoin,ethereum,solana). More FX: read additional codes from fx.rates and add to the payload. Timestamps: convert ts to your preferred timezone on client side. CORS: if calling from browsers, add CORS headers in Respond (options → headers). 🧩 Troubleshooting Empty/partial JSON: run the two HTTP nodes once to verify responses. 429s / rate limiting: add a short Wait node or cache outputs. Wrong URL: ensure you’re using Production URL outside the n8n editor. Security errors: if you add a secret, return 401 when it’s missing/invalid.

Automated workflow to remove video backgrounds and composite foreground video on static image backgrounds. Perfect for creating branded content, professional presentations, and consistent visual branding across your videos. How it works • Upload inputs: Provide foreground video URL and background image URL (both must be publicly accessible) • Remove background: API automatically removes video background with AI-powered segmentation • Composite on image: Video is centered on custom image background with aspect ratio preserved • Save to Drive: Final composed video is automatically uploaded to Google Drive with shareable link Set up steps ⏱️ Total setup time: ~7 minutes • Get VideoBGRemover API Key (~2 min): Visit https://videobgremover.com/api-management, sign up, and copy your API key • Add API key to n8n (~2 min): Go to Settings → Variables, add VIDEOBGREMOVER_KEY with your API key as value. Find the api key -> https://videobgremover.com/n8n • Connect Google Drive (~2 min): Click "Upload to Google Drive" node, click "Connect", and authorize n8n • Test workflow (~1 min): Use manual trigger with sample URLs provided in the "Sample URLs (Edit Here)" node Use cases: Branded content with company backgrounds and logos Product demos with custom imagery or brand colors AI avatars on professional office/studio backgrounds Social media content requiring consistent visual branding Profile videos with custom scenes or patterns Presentation videos with company branding Pricing: VideoBGRemover API charges $0.50-$2.00 per minute of video processed. Free trial credits available. Triggers: Webhook (for automation) or Manual (for testing) Processing time: Typically 3-5 minutes per minute of video