by WeblineIndia
Extract a key–value pair by index from JSON to fields in n8n This template takes a JSON object and a row index and returns exactly one key–value pair at that index. It’s a handy helper when you only need a single entry from a structured JSON payload (e.g., picking one form field for downstream logic). Who’s it for Makers who want a quick JSON picker without writing full parsing logic. Developers testing API payloads or building proofs of concept. Ops/analysts who need to pluck a single field for emails, documents or notifications. How it works Manual Trigger (When clicking ‘Test workflow’) starts the flow. Set → Input JSON Node holds your sample payload with: myData: an object of key → value pairs. rowIndex: a 0‑based index indicating which pair to extract. Code (Python) → Find Key‑Value Pair iterates myData and returns [key, value] at rowIndex as result. Set → Key maps result[0] to a field named result. Set → Value maps result[1] to a field named result[1]. The selected key and value are then available to any downstream nodes. How to set up Open the workflow and select Input JSON Node. Replace the sample with your own JSON: { "myData": { "name": "Alice", "age": "30", "city": "Paris" }, "rowIndex": "1" } Click Execute Workflow. Check the Key and Value nodes for the outputs. Requirements n8n running (cloud or self‑hosted). Code node (Python)** enabled in your n8n version. Input payload structure: myData: object with keys/values rowIndex: integer (0‑based) How to customize Pick by key name** (instead of index): adjust the Python code to look up a specific key. Handle nested objects/arrays**: walk or flatten the structure before selecting. Change output shape**: return { "key": ..., "value": ... } or write directly to next‑node fields. Validate inputs**: add checks for out‑of‑range rowIndex, non‑object myData, or empty objects. Add‑ons Webhook intake**: Replace Manual Trigger with a Webhook to accept live JSON. Schema guard**: Add an If/Function step to ensure myData is an object and rowIndex is numeric. Audit log**: Append the selected key/value to Google Sheets or a database. Use Case Examples Pull one field from a large API response to include in an email. Extract a specific answer from a form submission for conditional routing. Read a configuration pair from a settings object to control a downstream step. Common troubleshooting | Issue | Possible Cause | Solution | |---|---|---| | “Index out of range” | rowIndex is larger than the number of keys | Use a valid 0‑based index; add a guard in the Code node to clamp or default. | | Wrong key returned | Object key order differs from expectations | Object key order isn’t guaranteed across sources—prefer pick by key name for reliability. | | Empty/invalid output | myData is not an object or is empty | Ensure myData is a flat object with at least one key. | | Python errors | Code node’s Python runtime not available | Enable Python in the Code node or convert the snippet to JavaScript. | | Value type mismatch | Value isn’t a string | Cast as needed in the Set node or normalize types in the Code node. | Need Help? If you’d like this to pick by key, handle nested JSON, accept data via Webhook or fully customized to your needs, write to us and we’ll adapt the template to your exact use case.
by Sulieman Said
Overview This workflow automatically collects the latest articles from Google News RSS feeds, cleans and deduplicates them, and stores them neatly in a Google Sheet. It runs on a set schedule (every Monday at 09:00 by default) and helps you build a fresh pool of content ideas for newsletters, blogs, or social media. What you can do with it 🔎 Research faster – pull in fresh articles from multiple RSS sources without manual searching. 🧼 Clean & normalize – extract the real article URL (instead of Google redirects), keep only the title, summary, and date. 🗑 No duplicates – filter out empty or repeated entries before they ever reach your sheet. 📊 Central storage – append all new, unique links into a Google Sheet for review or further automation. How it works Trigger – Cron starts the flow every Monday at 09:00 (you can change the schedule). RSS Read – Fetches articles from multiple Google News queries (e.g., “AI”, “AI Automation”). Merge – Combines all feed results into one list. Set (Clean URL) – Extracts the real URL, title, summary, and publication date. Filter – Ensures only items with a valid title and URL continue. Unique by URL – Removes duplicate articles across feeds. Google Sheets Append – Saves new links into your chosen Sheet for review and later use. Setup Instructions Import workflow into your n8n instance. Update RSS feeds: Replace the example Google News RSS URLs (AI, AI Automation) with your own queries. Format: https://news.google.com/rss/search?q=YOUR_QUERY&hl=de&gl=DE&ceid=DE:de Connect Google Sheets: Add your Google Sheets credentials. Select the documentId (the spreadsheet) and sheetName (the tab) in the Append new Links node. Recommended columns: date, title, url, summary. Adjust schedule: In the Trigger: Montag 09:00 node, change the cron expression to daily or multiple times per day if you want. Run test: Execute once manually. Check your sheet for the first rows. Tips & Extensions ✅ Add more RSS Read nodes for additional sources (blogs, media outlets, niche topics). ✅ Chain this workflow with an AI node (OpenAI/GPT) to automatically generate post ideas from the collected articles. ✅ Notify yourself in Slack/Telegram when new articles are added. ✅ Use a status column (Draft, Approved, Posted) to manage a simple content pipeline directly from the sheet. 👉 With this template you’ll never run out of content ideas – everything flows into one place, ready to inspire your next posts, newsletters, or campaigns.
by WeblineIndia
Auto-Generate GitHub Release Notes and Notify via Slack (n8n Workflow) This n8n workflow automates the process of: Generating structured GitHub release notes from merged pull requests since the last tag. Creating a draft GitHub release using the latest tag and PR info. Sending a formatted summary to a Slack channel. All of this is triggered manually via a form, where the user inputs the repository, owner and target branch. Who's It For This flow is perfect for: Open-source maintainers** looking to automate changelog management. DevOps engineers** handling release cycles. Engineering teams** maintaining structured, consistent GitHub releases. Technical writers** who prepare release notes. How It Works Node Summary: | Node No | Node Name | Description | |---------|------------------------------------|---------------------------------------------------------------| | 1 | GitHub Release Input Form | Takes user inputs (owner, repo, branch). | | 2 | Config | Extracts input and defines PR label grouping config. | | 3 | Get Latest Git Tag | Fetches latest Git tag (used as reference point). | | 4 | Get Commit Date of Latest Tag | Gets the exact timestamp of the latest tag's commit. | | 5 | Fetch All Merged PRs Since Last Tag | Queries GitHub for PRs merged after that timestamp. | | 6 | Group PRs & Generate Release Notes | Organizes PRs by label and generates markdown notes. | | 7 | GitHub Pre-release | Creates a draft GitHub release with those notes. | | 8 | Send Message to Slack | Sends the final release summary to Slack. | How to Set Up Clone or import this workflow into your n8n instance. Configure the following credentials: GitHub OAuth or PAT (Personal Access Token) Slack Webhook URL or OAuth credentials Open the form node and fill in: owner: GitHub username/org repo: GitHub repository name branch: Base branch (e.g., main) Run the workflow manually and observe the release note being: Created as a draft on GitHub Sent to Slack Requirements | Requirement | Description | |-----------------|-----------------------------------------------------| | n8n version | Cloud or Self-Hosted | | GitHub Access | A token with repo and write:repo_hook permissions | | Slack Access | Webhook URL or Slack OAuth app | | Git Tags | Semantic versioning tags pushed to the repo | | Labels | PRs should be labeled (e.g., feature, bug, other) for grouping | How to Customize | Feature | How to Customize | |---------------------|---------------------------------------------------------------| | Label Grouping | Modify the config map in the Config node (step 2). | | PR Filtering | Adjust the search query in node 5 to fit your repo's conventions. | | Markdown Template | Tweak markdown generation logic in node 6. | | Slack Message Format| Customize the Slack text in node 8. | | Tag Format | Switch from semantic versioning if needed in node 3 logic. | | Release Type | Change draft: true to false in node 7 for immediate publishing. | Add‑ons You can extend the flow by: Adding a cron scheduler for periodic releases. Sending release notes via email (use the Email node). Publishing directly to Jira or Confluence. Posting GitHub release links to Discord. Use Case Examples | Scenario | Description | |---------------------------|---------------------------------------------------------------| | OSS Team Weekly Releases | Automatically publish weekly release notes summarizing merged PRs. | | Sprint Review Reports | Use it at the end of each sprint to generate change summaries. | | CI/CD Pipelines | Integrate with GitHub Actions or Jenkins for automated tagging + release. | Common Troubleshooting | Issue | Possible Cause | Solution | |----------------------------------------|-------------------------------------------|----------------------------------------------------------------------| | No data found for item-index: "1" | GitHub Search returned no PRs | Ensure PRs were merged after the last tag and branch name is correct | | Cannot access $node in code | Wrong script execution context | Ensure JavaScript is selected and variables are accessed properly | | draft must be boolean | Draft field passed as string | Use true (not "true") in JSON input of HTTP node | | PR labels not grouped | PRs have no matching labels | Update your label config map or ensure labels exist on PRs | | Empty Slack message | Slack node not receiving data | Ensure $json.release_notes is being passed correctly | Need Help? Need help setting this up for your team or extending it for more features (e.g., JIRA, auto-tagging, changelog export)? We're here to help you customize, debug and scale this flow. Feel free to reach out WeblineIndia if you need: One-on-one setup assistance. Custom n8n nodes or scripts. Advanced GitHub/Slack integrations.
by System Admin
Tagged with: , , , ,
by System Admin
Tagged with: , , , ,
by System Admin
Tagged with: , , , ,
by Rosh Ragel
Automatically Forward Email Receipts to QuickBooks Online What It Does Are you tired of manually uploading email receipts to QuickBooks Online (QBO)? Are your email forwarding rules difficult to set up or unreliable? This n8n workflow automatically forwards your email receipts to QuickBooks Online with minimal configuration. Example Use Cases Online purchase and subscription receipts E-transfer confirmations Bills and invoices received from suppliers Expense reports sent by vendors Payment confirmation emails Send other people's emails to QBO, bypassing the forwarding restrictions Prerequisites To use this workflow, you'll need: A Gmail account with credentials configured in n8n QuickBooks Online account with receipt forwarding enabled How to Set Up Gmail Search for emails that contain receipts (e.g., subject contains "Interac E-transfer") Create a Gmail filter that automatically applies a specific label to those emails (e.g., "New E-Transfer") Create another label for processed emails to prevent duplicate processing (e.g., "Processed") How It Works Trigger: The workflow runs when a new receipt is received; a scheduled trigger acts as a failsafe to catch missed emails. The first Gmail node retrieves emails with the "new receipt" label. The second Gmail node forwards the exact email contents to QuickBooks Online, mimicking a forwarded email. The workflow removes the original "new receipt" label and applies the "processed" label to avoid duplicate forwarding. How to Use Configure each Gmail node with your Gmail credentials in n8n. Enter your QuickBooks Online receipt forwarding email address in the second Gmail node (e.g., example@qbdocs.com). Set up the appropriate labels in each Gmail node to match your Gmail filter and workflow logic. Customization Options Modify the Gmail nodes to download and forward attachments if necessary. Create separate workflows for different types of emails; for example, include vendor information in the subject line (e.g., "Your Instacart Order Receipt") to help QuickBooks categorize expenses. Add error handling and notifications to monitor workflow execution. Why It's Useful Saves time by automating manual forwarding of receipts to QuickBooks Online. Reduces errors and missed receipts that can occur with manual processing. Keeps your QuickBooks records up-to-date automatically. Provides a scalable solution for handling various receipt types and vendors. Easily customizable to fit your specific email and accounting workflows.
by System Admin
Tagged with: , , , ,
by System Admin
Tagged with: , , , ,
by Oneclick AI Squad
This automated n8n workflow provides real-time currency conversion by capturing GET requests via a webhook, parsing exchange rate data from Google Search, and returning a formatted response. The system handles query parameter validation and error cases to ensure reliable conversions. What is Real-Time Currency Conversion? Real-time currency conversion involves fetching the latest exchange rates from Google Search via HTTP requests, processing the data, and delivering a user-friendly conversion result based on a provided query parameter. Good to Know The workflow requires a valid query parameter (q) for conversion requests Google Search parsing depends on the availability and structure of search results Error handling is included for missing query parameters Responses are formatted for easy integration How It Works Webhook* - Captures GET requests with query parameter *q** Check Query Parameter** - Validates that the required query parameter exists Fetch Exchange Rate** - Makes HTTP request to Google search for exchange rates Error Response** - Handles missing query parameter errors Extract Conversion Data** - Processes HTML response to extract conversion data Format Currency Response** - Formats the result into a user-friendly response Send Conversion Response** - Returns the formatted response How to Use Import the workflow into n8n Configure the webhook to receive GET requests with a query parameter (q) Test the workflow with sample conversion queries (e.g., "1 USD to INR") Monitor for error responses and adjust query handling if needed Requirements Webhook configuration Internet access for Google Search requests Customizing This Workflow Adjust the query parameter validation in the Check Query Parameter node to support additional formats Modify the Format Currency Response node to change the output format based on user needs
by Yaron Been
This workflow provides automated access to the Bytedance Omni Human AI model through the Replicate API. It saves you time by eliminating the need to manually interact with AI models and provides a seamless integration for video generation tasks within your n8n automation workflows. Overview This workflow automatically handles the complete video generation process using the Bytedance Omni Human model. It manages API authentication, parameter configuration, request processing, and result retrieval with built-in error handling and retry logic for reliable automation. Model Description: Turns your audio/video/images into professional-quality animated videos Key Capabilities AI-powered video generation and processing** High-quality video synthesis from inputs** Advanced video manipulation capabilities** Tools Used n8n**: The automation platform that orchestrates the workflow Replicate API**: Access to the Bytedance/omni-human AI model Bytedance Omni Human**: The core AI model for video generation Built-in Error Handling**: Automatic retry logic and comprehensive error management How to Install Import the Workflow: Download the .json file and import it into your n8n instance Configure Replicate API: Add your Replicate API token to the 'Set API Token' node Customize Parameters: Adjust the model parameters in the 'Set Video Parameters' node Test the Workflow: Run the workflow with your desired inputs Integrate: Connect this workflow to your existing automation pipelines Use Cases Video Content Creation**: Generate videos for social media, marketing, and presentations Animation & Motion Graphics**: Create animated content and visual effects Video Editing**: Enhance and transform existing video content Educational Content**: Produce instructional and explainer videos Connect with Me Website**: https://www.nofluff.online YouTube**: https://www.youtube.com/@YaronBeen/videos LinkedIn**: https://www.linkedin.com/in/yaronbeen/ Get Replicate API**: https://replicate.com (Sign up to access powerful AI models) #n8n #automation #ai #replicate #aiautomation #workflow #nocode #videogeneration #aivideo #videoai #motion #videoautomation #videocreation #machinelearning #artificialintelligence #aitools #automation #digitalart #contentcreation #productivity #innovation
by Yaron Been
This workflow provides automated access to the Black Forest Labs Flux Kontext Max AI model through the Replicate API. It saves you time by eliminating the need to manually interact with AI models and provides a seamless integration for image generation tasks within your n8n automation workflows. Overview This workflow automatically handles the complete image generation process using the Black Forest Labs Flux Kontext Max model. It manages API authentication, parameter configuration, request processing, and result retrieval with built-in error handling and retry logic for reliable automation. Model Description: A premium text-based image editing model that delivers maximum performance and improved typography generation for transforming images through natural language prompts Key Capabilities High-quality image generation from text prompts** Advanced AI-powered visual content creation** Customizable image parameters and styles** Tools Used n8n**: The automation platform that orchestrates the workflow Replicate API**: Access to the Black Forest Labs/flux-kontext-max AI model Black Forest Labs Flux Kontext Max**: The core AI model for image generation Built-in Error Handling**: Automatic retry logic and comprehensive error management How to Install Import the Workflow: Download the .json file and import it into your n8n instance Configure Replicate API: Add your Replicate API token to the 'Set API Token' node Customize Parameters: Adjust the model parameters in the 'Set Image Parameters' node Test the Workflow: Run the workflow with your desired inputs Integrate: Connect this workflow to your existing automation pipelines Use Cases Content Creation**: Generate unique images for blogs, social media, and marketing materials Design Prototyping**: Create visual concepts and mockups for design projects Art & Creativity**: Produce artistic images for personal or commercial use Marketing Materials**: Generate eye-catching visuals for campaigns and advertisements Connect with Me Website**: https://www.nofluff.online YouTube**: https://www.youtube.com/@YaronBeen/videos LinkedIn**: https://www.linkedin.com/in/yaronbeen/ Get Replicate API**: https://replicate.com (Sign up to access powerful AI models) #n8n #automation #ai #replicate #aiautomation #workflow #nocode #imagegeneration #aiart #texttoimage #visualcontent #aiimages #generativeart #flux #machinelearning #artificialintelligence #aitools #automation #digitalart #contentcreation #productivity #innovation