N8N español - Tratamiento de textos
Este workflow es para trabajar con tratamiento de texto usando n8n y poder iniciarte en como funciona. How To, Paso a Paso: https://comunidad-n8n.com/tratamiento-de-textos/ Comunidad de telegram: https://t.me/comunidadn8n
By The { AI } rtistAutomated DHL shipment tracking bot for web forms and email inquiries
This n8n template automates responses to customer inquiries about DHL shipment status, handling requests from both web forms and emails. Use cases Automate Customer Support: Provide 24/7 instant answers to the common "Where is my order?" question without human intervention. Reduce Support Tickets: Decrease the volume of repetitive tracking inquiries by providing customers with immediate, self-service information. Enhance Customer Experience: Offer a consistent and rapid response across multiple channels (your website and email), allowing customers to use their preferred method of contact. Good to know DHL API Key is required: You'll need to register on the DHL Developer Portal to get your API key. This workflow requires Gmail credentials (OAuth2) to monitor incoming emails and send replies. The webhook URL must be configured in your website's contact or tracking form to receive submissions. How it works The workflow is initiated by one of two triggers: a Webhook (from a website form) or a Gmail Trigger (when a new email arrives). A Merge node combines the data from both triggers into a single, unified flow. The "Extract Tracking Number" Code node intelligently parses the tracking number from either the form data or the email body. It also extracts the customer's name and email address. The HTTP Request node sends the extracted tracking number to the DHL API to fetch the latest shipment status. The "Format Response Message" Code node takes the API response and composes a user-friendly message for the customer. It also handles cases where tracking information is not found. An If node checks the original source of the inquiry to determine whether it came from the webhook or email. If the request came from the webhook, a Respond to Webhook node sends the tracking data back as a JSON response. If the request came from an email, the Gmail node sends the formatted message as an email reply to the customer. How to use Configure the Triggers: Webhook Trigger: Copy the Test URL and set it as the action endpoint for your web form. Once you activate the workflow, use the Production URL. Webhook URL: https://your-n8n-instance.com/webhook/dhl-tracking-inquiry Gmail Trigger: Connect your Gmail account using OAuth2 credentials and set the desired filter conditions (e.g., unread emails with a specific subject). Set up the DHL API: Open the "Get DHL Tracking Status" (HTTP Request) node and navigate to the "Headers" tab. Replace YOURDHLAPI_KEY with your actual DHL API key. json { "DHL-API-Key": "YOURDHLAPI_KEY" } Configure the Gmail Send Node: Connect the same Gmail credentials to the "Send Gmail Response" node. Customize options like the replyTo address as needed. Activate the workflow. Requirements A DHL Developer Portal account to obtain an API key. A Gmail account configured with OAuth2 in n8n. Customising this workflow Add More Carriers: Duplicate the HTTP Request node and response formatting logic to support other shipping carriers like FedEx or UPS. Log Inquiries: Add a node to save inquiry details (tracking number, customer email, status) to a Google Sheet or database for analytics. Advanced Error Handling: Implement more robust error handling, such as sending a Slack notification to your support team if the DHL API is down or returns an unexpected error.
By Yusuke YamamotoEnd-to-end Ai blog research and writer with Gemini AI, Supabase and Nano-Banana
Blog Research and Writer n8n Workflow - Ai Blog Writer Fully automated blog creation system using n8n + AI Agents + Image Generation Example Blog Overview This workflow automates the entire blog creation pipeline—from topic research to final publication. Three specialized AI agents collaborate to produce publication-ready blog posts with custom images, all saved directly to your Supabase database. How It Works Research Agent (Topic Discovery) Triggers: Runs on schedule (default: daily at 4 AM) Process: Fetches existing blog titles from Supabase to avoid duplicates Uses Google Search + RSS feeds to identify trending topics in your niche Scrapes competitor content to find content gaps Generates detailed topic briefs with SEO keywords, search intent, and differentiation angles Output: Comprehensive research document with SERP analysis and content strategy Writer Agent (Content Creation) Triggers: Receives research from Agent 1 Process: Writes full blog article based on research brief Follows strict SEO and readability guidelines (no AI fluff, natural tone, actionable content) Structures content with proper HTML markup Includes key sections: hook, takeaways, frameworks, FAQs, CTAs Places image placeholders with mock URLs (https://db.com/image_1, etc.) Output: Complete JSON object with title, slug, excerpt, tags, category, and full HTML content Image Prompt Writer (Visual Generation) Triggers: Receives blog content from Agent 2 Process: Analyzes blog content to determine number and type of images needed Generates detailed 150-word prompts for each image (feature image + content images) Creates prompts optimized for Nano-Banana image model Names each image descriptively for SEO Output: Structured prompts for 3-6 images per blog post Image Generation Pipeline Process: Loops through each image prompt Generates images via Nano-Banana API (Wavespeed.ai) Downloads and converts images to PNG Uploads to Supabase storage bucket Generates permanent signed URLs Replaces mock URLs in HTML with real image URLs Output: Blog HTML with all images embedded Publication Final blog post saved to Supabase blogs table as draft Ready for immediate publishing or review Key Features ✅ Duplicate Prevention: Checks existing blogs before researching new topics ✅ SEO Optimized: Natural language, proper heading structure, keyword integration ✅ Human-Like Writing: No robotic phrases, varied sentence structure, actionable advice ✅ Custom Images: Generated specifically for each blog's content ✅ Fully Structured: JSON output with all metadata (tags, category, excerpt, etc.) ✅ Error Handling: Automatic retries with wait periods between agent calls ✅ Tool Integration: Google Search, URL scraping, RSS feeds for research Setup Requirements API Keys Needed Google Gemini API: For Gemini 2.5 Pro/Flash models (content generation/writing) Groq API (optional): For Kimi-K2-Instruct model (research/writing) Serper.dev API: For Google Search (2,500 free searches/month) Wavespeed.ai API: For Nano-Banana image generation Supabase Account: For database and image storage Supabase Setup Create blogs table with fields: title, slug, excerpt, category, tags, featured_image, status, featured, content Create storage bucket for blog images Configure bucket as public or use signed URLs Workflow Configuration Update these placeholders: RSS Feed URLs: Replace [your website's rss.xml] with your site's RSS feed Storage URLs: Update Supabase storage paths in "Upload object" and "Generate presigned URL" nodes API Keys: Add your credentials to all HTTP Request nodes Niche/Brand: Customize Research Agent system prompt with your industry keywords Writing Style: Adjust Writer Agent prompt for your brand voice Customization Options Change Image Provider Replace the "nano banana" node with: Gemini Imagen 3/4 DALL-E 3 Midjourney API Any Wavespeed.ai model Adjust Schedule Modify "Schedule Trigger" to run: Multiple times daily Specific days of week On-demand via webhook Alternative Research Tools Replace Serper.dev with: Perplexity API (included as alternative node) Custom web scraping Different search providers Output Format json { "title": "Your SEO-Optimized Title", "slug": "your-seo-optimized-title", "excerpt": "Compelling 2-3 sentence summary with key benefits.", "category": "Your Category", "tags": ["tag1", "tag2", "tag3", "tag4"], "author_name": "Your Team Name", "featured": false, "status": "draft", "content": "<article>...complete HTML with embedded images...</article>" } Performance Notes Average runtime: 15-25 minutes per blog post Cost per post: ~$0.10-0.30 (depending on API usage) Image generation: 10-15 seconds per image with Nano-Banana Retry logic: Automatically handles API timeouts with 5-15 minute wait periods Best Practices Review Before Publishing: Workflow saves as "draft" status for human review Monitor API Limits: Track Serper.dev searches and image generation quotas Test Custom Prompts: Adjust Research/Writer prompts to match your brand Image Quality: Review generated images; regenerate if needed SEO Validation: Check slugs and meta descriptions before going live Workflow Architecture 3 Main Phases: Research → Writer → Image Prompts (Sequential AI Agent chain) Image Generation → Upload → URL Replacement (Loop-based processing) Final Assembly → Database Insert (Single save operation) Error Handling: Wait nodes between agents prevent rate limiting Retry logic on agent failures (max 2 retries) Conditional checks ensure content quality before proceeding --- Result: Hands-free blog publishing that maintains quality while saving 3-5 hours per post.
By Muhammad AsadullahGenerate structured company descriptions with Bedrijfsdata Web RAG & OpenAI
This workflow contains community nodes that are only compatible with the self-hosted version of n8n. This template generates structured synthetic company content using live web data from the Bedrijfsdata.nl API combined with an LLM. Provide a company domain (directly or via a Bedrijfsdata.nl ID) and the workflow retrieves relevant website and search engine content, then produces ready-to-use descriptions of the company, its offerings, and its target audience. ✨ Features Create high-quality Dutch-language company descriptions on demand Automatically pull live web content via Bedrijfsdata.nl RAG Domain & RAG Search Structured JSON output for consistent downstream use (e.g., CRM updates, lead qualification) Flexible trigger: run from ProspectPro ID, domain input, or another workflow Secure, modular, and extendable structure (error handling included) 🏢 Example Output The workflow produces structured content fields you can directly use in your sales, marketing, or enrichment flows: company_description – 1-2 paragraph summary of the company productsandservices – detailed overview of offerings target_audience – specific characteristics of ideal customers (e.g., industry, location, company size, software usage) Example: { "company_description": "Bedrijfsdata.nl B.V. is een Nederlands bedrijf dat uitgebreide data levert over meer dan 3,7 miljoen bedrijven in Nederland...", "productsandservices": "Het bedrijf biedt API-toegang tot bedrijfsprofielen, sectoranalyses, en SEO-gegevens...", "target_audience": "Nederlandse MKB's die behoefte hebben aan actuele bedrijfsinformatie voor marketing- of salesdoeleinden..." } ⚙ Requirements n8n instance or cloud workspace Install the Bedrijfsdata.nl n8n Verified Community Node OpenAI API credentials (tested with gpt-4.1-mini and gpt-3.5-turbo) Bedrijfsdata.nl developer account (14-day free trial, 500 credits) 🔧 Setup Instructions Trigger configuration Use Bedrijfsdata.nl ID (default) or provide a domain directly Can be called from another workflow using “Execute Workflow” Configure API credentials Bedrijfsdata.nl API key OpenAI API key Customize Output (Optional) Adjust prompt in the LLM node to create other types of synthetic content Extend structured output schema for your use case Integrate with Your Stack Example node included to update HubSpot descriptions Replace or extend to match your CRM, database, or messaging tools 🔐 Security Notes Input validation for required domain Dedicated error branches for invalid input, API errors, LLM errors, and downstream integration errors RAG content checks before running the LLM 🧪 Testing Run workflow with a Bedrijfsdata.nl ID linked to a company with a known website Review generated JSON output Verify content accuracy before production use 📌 About Bedrijfsdata.nl Bedrijfsdata.nl operates the most comprehensive company database in the Netherlands. With real-time data on 3.7M+ businesses and AI-ready APIs, we help Dutch SMEs enrich their CRM, workflows, and marketing automation. Built on 25+ years of experience in data collection and enrichment, our technology brings corporate-grade data quality to every organisation. Website: https://www.bedrijfsdata.nl Developers: https://developers.bedrijfsdata.nl API docs: https://docs.bedrijfsdata.nl 📞 Support Email: klantenservice@bedrijfsdata.nl Phone: +31 20 789 50 50 Support hours: Monday–Friday, 09:00–17:00 CET
By OlivierCreating SEO-optimized blogs for WordPress using specific tools
✍️ AI-Powered High-Quality Blog Automation Automate SEO-optimized blog creation, publishing, and internal linking — designed for Lovable.dev or seamless WordPress integration. Proven to boost impressions by +15% weekly on real websites. 📌 Example: AI Applications in Real Estate Playbook — fully generated, optimized, and published with this automation. --- 🚀 What This Workflow Does Bring Your Own Keywords You provide the keyword list — the workflow applies a scoring formula to rank them by relevance and competition for maximum SEO impact. Keyword Scoring & Logging Scores primary and secondary keywords, logs them in PostgreSQL, and prevents reuse until strategically relevant. Deep Research & Blog Planning Uses Perplexity AI and other AI models to outline, plan, and enrich each article with authoritative external sources. SEO-Optimized Redaction Writes multi-part, long-form blogs with integrated internal links (to your existing content) and external links to reputable sites. Image Generation & Selection Creates or selects high-quality header and in-article images, optimized for your topic. Full Blog Infrastructure Internal & external linking logic Blog card + metadata updates Sitemap updates & Google indexing submission Post logging for future reference Publishing Flexibility Direct GitHub commits for Lovable.dev WordPress-ready export Optional Slack approval before publishing --- 🔗 Integrated Services PostgreSQL – Keyword & content database Perplexity AI – Research & planning OpenAI / OpenRouter Models – Multi-part blog writing Lovable.dev / GitHub – Direct publishing WordPress-ready JSON output – Easy CMS import Slack – Approval workflow before going live --- 💼 What You Get Detailed Setup Guide Workflow Description --- 📥 Perfect For Website owners wanting consistent SEO growth Agencies handling multiple client sites Marketers running content-heavy campaigns Lovable.dev or WordPress users who want hands-off publishing --- 💡 Why You’ll Love It This is more than a blog writer — it’s a complete content infrastructure. From keyword prioritization to publishing and indexing, it keeps your site growing in reach and authority while you focus on your business.
By Paul