Workflow Templates

Monitor Clutch categories for new agencies to Slack With BrowserAct and Gemini Introduction This workflow automates the discovery of new B2B service providers entering the market. It scrapes a specific category on Clutch.co weekly, standardizes the data using AI, and compares it against a historical database to identify only the fresh "new entrants." These leads are then sent to Slack as a "Hot Alert." Target Audience Sales Development Representatives (SDRs), partnership managers, and lead generation agencies looking for new agencies or service providers before their competitors find them. How it works Scheduling: A Weekly Trigger initiates the scan to ensure regular monitoring of the market. Targeting: A Set node defines the specific Clutch category URL to monitor (e.g., https://clutch.co/developers). Data Extraction: The BrowserAct node runs the "The New Entrant Asset Finder" template. It navigates to the target category and scrapes the current list of companies. Data Cleaning: An AI Agent (using OpenRouter/Gemini) processes the raw scraped data. It fixes formatting issues, such as converting "$10,000+" to integers and splitting "City, Country" strings into separate fields. Staging: The cleaned data is written to a temporary "Second Extraction" sheet in Google Sheets. Change Detection: The workflow retrieves the previous week's data ("Database") and the current week's data. A second AI Agent compares the two lists to identify companies that exist in the new scan but not the old one. Notification: If new companies are found, a Slack node posts a formatted alert with details like "Company Name," "Rate," and "Website." Database Update: The workflow clears the old database and replaces it with the latest scan, establishing a new baseline for the next week's comparison. How to set up Configure Credentials: Connect your BrowserAct, OpenRouter, Google Sheets, and Slack accounts in n8n. Prepare BrowserAct: Ensure the The New Entrant Asset Finder template is active in your BrowserAct library. Prepare Google Sheet: Create a Google Sheet with two tabs: Database (First Extarction) Second Extraction Define Target: Open the Clutch Category Link node and paste the URL of the Clutch category you want to track. Configure IDs: Update the Google Sheets nodes to point to your specific spreadsheet file and the respective tabs mentioned above. Google Sheet Headers To use this workflow, ensure your Google Sheet tabs use the following headers: company_name website_url min_project_value_usd hourly_rate_low hourly_rate_high employees_range city country short_description Requirements BrowserAct Account:* Required for scraping. Template: *The New Entrant Asset Finder**. OpenRouter Account:** Required for cleaning data and detecting changes. Google Sheets:** Acts as the historical database. Slack Account:** Used for receiving lead alerts. How to customize the workflow Change the Source: Modify the Clutch Category Link and the BrowserAct template to scrape a different directory, such as G2, Capterra, or Upwork. Filter Logic: Update the system prompt in the Detect data changes AI node to only alert on companies with a specific hourly rate (e.g., >$100/hr) or employee count. Enrichment: Add a Clearbit or Apollo node after the change detection step to find email addresses for the new companies before sending them to Slack. Need Help? How to Find Your BrowserAct API Key & Workflow ID How to Connect n8n to BrowserAct How to Use & Customize BrowserAct Templates Workflow Guidance and Showcase Video AI-Powered Lead Finder: Target New & Growing Companies (n8n + AI Tutorial)

How it works This workflow automatically generates and sends personalized sales proposals when a new row is added to Google Sheets. It uses AI to create proposal content, updates contact details in HubSpot, and generates a formatted document. The document is converted into a PDF and emailed to the client. This eliminates manual proposal writing and ensures fast, consistent delivery. Step-by-step Capture lead and generate AI content** Google Sheets Trigger – Detects new form submissions in your sheet. Loop Over Items – Processes each new entry individually. Message a model – Uses Gemini AI to generate the proposal content. Code in JavaScript – Cleans and splits AI output into structured fields. Create contact and generate document** Create or update a contact – Stores or updates client data in HubSpot. Copy file – Duplicates a proposal template from Google Drive. Update a document – Replaces placeholders with real client and AI data. Download file – Converts the final document into a PDF file. Send proposal to client** Send a message – Emails the generated PDF proposal to the client. Why use this? Automatically generates professional proposals without manual writing Ensures consistent formatting using templates and placeholders Saves time by combining CRM, AI, and document creation Improves response speed for leads and increases conversion chances Scales easily for handling multiple client requests simultaneously

Stop spending hours manually pulling paid ads data. This workflow connects to Databox via MCP, auto-discovers every connected paid platform, fetches 6 key metrics, and delivers a consolidated weekly report to Slack and email - every Monday at 9 AM, completely hands-free. Who's it for Performance marketers** managing campaigns across multiple platforms Marketing managers** who need a weekly cross-platform overview Agencies** automating paid ads reporting for clients How it works Schedule Trigger fires every Monday at 9 AM AI Agent connects to Databox via MCP and discovers all connected paid platforms (Google Ads, Facebook Ads, LinkedIn Ads, TikTok Ads, and 6 more) Fetches Spend, Clicks, CPC, CTR, Impressions, and Conversions for this week and last week Calculates week-over-week changes and formats two outputs - a Slack summary and a color-coded HTML email Delivers both simultaneously Requirements Databox account** with at least one paid ads platform connected (free plan works) OpenAI API key (or Anthropic) Slack account Gmail account How to set up Click Databox MCP Tool - set Authentication to OAuth2 and authorize Add your OpenAI API key to the Chat Model node Connect Slack and update the channel ID in the Send to Slack node Connect Gmail and set the recipient address in the Send Email node Activate - your first report arrives next Monday

How It Works This workflow automates end-to-end audio translation with quality assurance for content creators, educators, and international teams managing multilingual content. It solves the challenge of translating audio into multiple languages while ensuring accuracy and maintaining organized delivery. The system receives audio files via webhook, splits them into target languages (Arabic, French, Spanish, Chinese, Hindi), and processes each through NVIDIA's Parakeet TDT translation model. OpenAI validates translation quality, and results are enhanced with comprehensive metadata. Successfully translated files are uploaded to Google Drive with organized naming, combined into a summary spreadsheet, and delivered via email notification. Failed translations trigger quality alerts, ensuring reliable output while minimizing manual oversight and reducing translation turnaround time from hours to minutes. Setup Steps Configure NVIDIA API credentials in the "Generate Audio with ElevenLabs" Add OpenAI API key for quality evaluation in the "OpenAI Chat Model" node Set up Google Drive OAuth connection and specify target folder ID for uploads Configure Gmail SMTP credentials for notification delivery Update webhook URL in source applications to trigger workflow Customize target languages in "Split Languages" node if needed Prerequisites Active accounts: NVIDIA (build.nvidia.com), OpenAI, Google Drive, Gmail. API credentials for all services. Use Cases International podcast distribution, e-learning course localization Customization Modify target languages in Split node, adjust quality thresholds in OpenAI evaluation Benefits Reduces translation time by 90%, eliminates manual quality checks through automated validation Here are clear, professional subheadings for each What / Why pair. They’re concise, action-oriented, and fit well in technical workflow documentation.

How It Works Scheduled processes retrieve customer feedback from multiple channels. The system performs sentiment analysis to classify tone, then uses OpenAI models to extract themes, topics, and urgency indicators. All processed results are stored in a centralized database for trend tracking. Automated rules identify high-risk or negative sentiment items and trigger alerts to the relevant teams. Dashboards and workflow automation then visualize insights and support follow-up actions. Setup Instructions Data Sources: Connect social media APIs, survey tools, and customer support platforms. AI Analysis: Configure the OpenAI API with sentiment and theme-extraction prompts. Database: Set up a feedback storage schema in your utility database. Alerts: Configure email notifications and CRM triggers for priority issues. Dashboards: Link your analytics and reporting tools for real-time insights. Prerequisites Social media/survey API credentials; OpenAI API key; database access; CRM system credentials; email notification setup Use Cases Customer sentiment tracking; product feedback aggregation; support ticket prioritization; brand monitoring; trend identification Customization Adjust sentiment thresholds; add new feedback sources; modify categorization rules Benefits Reduces analysis time 85%; captures actionable insights; enables rapid response to issues

AI-Powered Timesheet → Invoice Automation (Gmail + OCR + AI + Google Sheets + QuickBooks) > Note: This workflow uses sticky notes extensively to document each logical section of the automation. Sticky notes are mandatory and already included to explain OCR, AI parsing, folder logic, duplicate handling, and QuickBooks steps. This workflow automates the full lifecycle of timesheet-based invoicing — from emailed timesheets to structured Google Sheets records and finalized invoices in QuickBooks Online. It is designed for real-world billing scenarios, including split weeks across months, zero-hour months, duplicate prevention, and first-week-of-year edge cases. What This Workflow Does Listens to Gmail for timesheet emails with attachments Splits and processes each attachment independently Extracts text using OCR (no hardcoded API keys) Uses AI to parse month-wise billable hours Correctly splits weeks spanning multiple months Looks up Customer and PO details from Google Sheets Organizes files in Client → Employee → Year folders in Google Drive Reuses existing invoice sheets or creates new ones Prevents duplicate invoice rows Automatically finds or creates customers in QuickBooks Creates invoices in QuickBooks using validated data High-Level Workflow Stages Gmail Intake and Attachment Loop OCR Text Extraction AI-Based Timesheet Parsing Month Normalization and Validation Customer & PO Lookup Drive Folder Discovery and Creation Invoice Sheet Reuse or Creation Duplicate and Edge-Case Handling Append Invoice Rows to Google Sheets Create / Update Customers in QuickBooks Create Invoices in QuickBooks Each of these stages is clearly documented with sticky notes inside the workflow canvas. Quick Setup Instructions Import the workflow JSON into your n8n instance Configure credentials for: Gmail Google Drive Google Sheets OpenAI or Google Gemini QuickBooks Online Verify the OCR HTTP node: Default URL: https://universal-file-to-text-extractor.vercel.app/extract No hardcoded API keys are used Configure Get Customer Info From PO Sheet: Spreadsheet ID Sheet name and column mappings Ensure the Client Invoices root folder exists in Google Drive Send a test timesheet email Execute the workflow once manually Activate the workflow Who This Workflow Is For Agencies and consultancies billing from emailed timesheets Finance and operations teams using Google Workspace + QuickBooks Staffing firms with monthly or bi-weekly contractor billing Teams that want a fully auditable, zero-manual invoice process Requirements n8n instance Gmail account receiving timesheet emails Google Drive and Google Sheets OpenAI or Google Gemini API OCR API endpoint (configurable) QuickBooks Online account Customer PO Google Sheet containing: Email Customer Name Company Name Customer Account Number PO Number Item Folder Name Invoice range Due Date Calculation How It Works (Detailed) 1. Email Intake and Attachment Loop Gmail Trigger polls for timesheet emails Attachments are split so each file is processed independently Sticky notes explain the intake and loop logic 2. OCR Extraction Each attachment is sent to the OCR API PDFs and images are converted to plain text OCR logic is documented via sticky notes 3. AI Timesheet Parsing (Month-Wise) AI extracts data only from BILLABLE HOURS sections Outputs strict JSON: Employee Name Client Name Month Year Week Start Date Week End Date Total Billable Hours Special handling included: Split weeks across months Zero-hour months still included No guessed or inferred dates 4. Month Normalization and Validation AI output is normalized into a month array Each month is processed independently Invalid or zero-hour entries are skipped 5. Customer and PO Lookup Sender email is matched in the PO sheet Retrieved values drive: Folder structure Invoice logic Due date calculation 6. Google Drive Folder Structure The workflow enforces a strict hierarchy: Client Invoices └── Client └── Employee └── Year Missing folders are created automatically. 7. Invoice Sheet Naming and Search Sheet names are generated using: Employee Name Month Year Existing sheets are reused when found Supports monthly and 15-day billing cycles 8. Duplicate Prevention and Edge Cases Duplicate invoice rows are detected and skipped January first-week edge case is handled explicitly Safe re-runs are supported 9. Google Sheets Invoice Rows Each appended row includes: Customer Account Number Invoice Date Due Date PO Number Item Name Quantity (Total Hours) Period description 10. QuickBooks Integration Searches for existing customers in QuickBooks Creates customers automatically if missing Creates invoices using: Customer reference Item Quantity Invoice date Due date All QuickBooks logic is documented with sticky notes. How To Customize Swap AI model (OpenAI ↔ Gemini) Extend prompts to extract: Project Cost center Approval status Add tax codes, currency, or unit pricing Modify folder naming rules Insert approval steps before invoice creation Common Use Cases Monthly contractor invoicing Agency billing across multiple clients Finance automation with audit-ready records Eliminating manual timesheet-to-invoice work Troubleshooting | Issue | Likely Cause | |------|-------------| | No invoices created | Gmail filter mismatch or email already read | | OCR output empty | Unsupported file or OCR endpoint issue | | Wrong month split | Review AI prompt and month logic | | Duplicate rows | Duplicate detection conditions | | Invoice missing in QuickBooks | Customer or item configuration issue | Notes on Community Guidelines Sticky notes are used throughout the workflow No hardcoded API keys are present Markdown is used (no HTML tags) This workflow is original and not copied Need Help or Customization? Digital Biz Tech can help tailor this workflow to your business. We offer free setup support, including credential configuration and deployment. Contact: rajeet.nair@digitalbiz.tech Website: https://www.digitalbiz.tech LinkedIn: https://www.linkedin.com/company/digital-biz-tech/ You can also DM us on LinkedIn for any help. You can also DM us on LinkedIn.

Event Registration + Auto-Enrichment Intelligence Who is this for? Event organizers, conference planners, and marketing teams fighting registration drop-off who want 4-field forms with LinkedIn-level attendee intelligence. What problem is this workflow solving? Multi-page forms kill conversions: 80-90% drop-off on page 2 No attendee insights post-reg Manual enrichment wastes hours Abandoned carts = lost revenue This captures 4 fields but enriches 15+ data points automatically. What this workflow does 3 Webhook Intelligence Suite: POST /event-registration**: 4-field form → enrichment → HubSpot POST /reg-beacon**: Abandoned cart tracking pixel POST /validate-promo**: AJAX promo code validation Requires 2 sub-workflows: 1) Abandoned Cart Recovery 2) Participant Re-engager Enrichment Waterfall: Clearbit → LinkedIn (Proxycurl) → Google+AI → Full profile Outputs: HubSpot contacts with company/role/title Data Tables: enriched_profiles / reg_analytics Slack alerts + email confirmations Setup (12 minutes) Data Tables**: enriched_profiles, reg_analytics, promo_codes HubSpot**: API key + custom properties APIs**: Clearbit, Proxycurl, SerpAPI, Gemini Host**: reg-page/index.html (update webhook URLs) SMTP/Slack**: Notifications Fully configurable, no code changes needed. How to customize to your needs Forms**: Swap HTML for Typeform/Webflow Enrichment**: Add Apollo/Hunter for emails CRM**: HubSpot → Salesforce → Airtable Promos**: Tiered discounts / early-bird Companion**: Abandoned Cart + Re-engager templates ROI: 3x registration completion** (4 fields vs 12+) 65% enriched profiles** (company/role/title) 20% revenue recovery** (abandoned carts) Need help customizing?: Contact me for consulting and support: LinkedIn / Message Keywords: event registration, attendee enrichment, abandoned cart recovery, conference automation, HubSpot

How It Works This workflow automates platform trust and safety operations by deploying a multi-agent AI system that detects abuse signals, investigates behaviour, scores risk, checks policy compliance, and enforces actions automatically. Designed for platform safety teams, content moderation managers, and compliance officers, it eliminates manual triage delays and ensures high-severity violations are actioned immediately. An abuse signal webhook triggers behaviour analysis via OpenAI, classifying signals by severity. A routing node directs cases to a Governance Agent, which orchestrates Investigation, Risk Scoring, and Policy Compliance Checker sub-agents. Enforcement data is prepared, then routed by action type-logging to abuse records, alerting the security team via Slack, sending escalation emails, or triggering auto-enforcement actions based on threshold checks—before all outcomes are logged. Setup Steps Configure Abuse Signal Webhook URL and authenticate incoming POST requests. Add OpenAI API credentials to all OpenAI Model nodes. Connect Google Sheets for abuse records and enforcement action logging. Configure Slack credentials and set security team alert channel. Add Gmail/SMTP credentials to Send Escalation Email node. Prerequisites Slack workspace with bot token Gmail or SMTP credentials Google Sheets for abuse and enforcement logging Use Cases Real-time abuse detection and auto-suspension on social platforms Customization Replace OpenAI with Anthropic Claude or NVIDIA NIM models Benefits Eliminates manual abuse triage with real-time AI signal processing

How It Works This workflow automates comprehensive risk signal detection and regulatory compliance management across financial and claims data sources. Designed for risk management teams, compliance officers, and financial auditors, it solves the critical challenge of identifying potential risks while ensuring timely regulatory reporting and stakeholder notifications. The system operates on scheduled intervals, fetching data from multiple sources including financial APIs and claims databases, then merging these streams for unified analysis. It employs an AI-powered risk signal agent to detect anomalies, regulatory violations, and compliance issues. The workflow intelligently routes findings based on risk severity, orchestrating parallel processes for critical risks requiring immediate escalation and standard risks needing documentation. It manages multi-channel notifications through Slack and email, generates comprehensive compliance documentation, and maintains detailed audit trails. By coordinating regulatory analysis, exception handling, and evidence collection, it ensures complete risk visibility while automating compliance workflows. Setup Steps Configure Schedule Trigger with risk monitoring frequency Connect Workflow Configuration node with data source parameters Set up Fetch B2B Data and Fetch Claims Data nodes with respective API credentials Configure Merge Financial Data node for data consolidation Connect Calculate Risk Metrics node with risk scoring algorithms Set up Risk Signal Agent with OpenAI/Nvidia API credentials for anomaly detection Configure parallel output parsers Connect Check Critical Risk node with severity routing logic Set up Route by Risk Level node for workflow branching Prerequisites OpenAI or Nvidia API credentials for AI-powered risk analysis, financial data API access Use Cases Insurance companies monitoring claims fraud patterns, financial institutions detecting transaction anomalies Customization Adjust risk scoring algorithms for industry-specific thresholds Benefits Reduces risk detection time by 80%, eliminates manual compliance monitoring

Terms of Service Change Watcher with AI Summaries Automatically monitors Terms of Service, Privacy Policy, and other legal pages for changes. When content changes are detected, GPT-4o analyzes the old vs new text and emails you a plain-English summary with an impact rating. How it works Every day at 8 AM, the workflow reads your list of URLs from a Google Sheet Each page is fetched and stripped to plain text The text is compared against the previously stored version If a change is detected, the old and new content are sent to GPT-4o for analysis You receive an email with a summary of exactly what changed and how it impacts you All changes are logged to a Change Log sheet for a historical record Setup Create a Google Sheet with two tabs: Pages (columns: url, page_name, last_content, last_checked) and Change Log (columns: date, page_name, url, summary) Add the URLs you want to monitor in the Pages tab — leave last_content and last_checked empty Connect your Google Sheets OAuth2, Gmail OAuth2, and OpenAI API credentials Update the Google Sheet document in all four Google Sheets nodes Set your email address in the Send Change Alert node Run once to save baselines, then activate the workflow

How it works Runs every morning at 8:00 using the Schedule Trigger. Sets a stale_days value and queries Salesforce for Opportunities where Stage_Unchanged_Days__c equals that value and the stage is not Closed Won / Closed Lost. For each “stale” Opportunity, loads full deal details and sends them to an OpenAI model. The model uses the query_soql tool to pull recent Notes, the primary Contact, and the Opportunity Owner, then returns a single JSON object with: a personalized follow-up email for the client, a short SMS template, a concise Slack summary for the sales team, and a ready-to-use Task payload for Salesforce. n8n parses that JSON, sends the email via SMTP, posts the Slack message to your chosen channel, and creates a Salesforce Task assigned to the Opportunity Owner so every stalled deal has a clear next step. Setup steps Estimated setup time: ~30–45 minutes if your Salesforce, OpenAI, SMTP and Slack credentials are ready. Create Stage_Unchanged_Days__c on Opportunity (Salesforce) Field Type: Formula (Number, 0 decimal places) Formula: IF( ISBLANK(LastStageChangeDate), TODAY() - DATEVALUE(CreatedDate), TODAY() - DATEVALUE(LastStageChangeDate) ) This field tracks how many days the Opportunity has been in the current stage. Connect credentials in n8n Salesforce OAuth2 for the Salesforce nodes and the query_soql HTTP Tool. OpenAI (or compatible) credential for the “Message a model” node. SMTP credential for the customer email node. Slack credential for the internal notification node. Configure your follow-up rules In Edit Fields (Set), set stale_days to the threshold that defines a stalled deal (e.g. 7, 14, 30). In Perform a query, optionally refine the SOQL (record types, owners, minimum amount, etc.) to match your pipeline. Update the Send Email SMTP Customer node with your real “from” address and tweak the wording if needed. Point Send Message To Internal Team (Slack) to the right channel or user. Test safely Turn off the Schedule Trigger and run the workflow manually with a few test Opportunities. Inspect the AI output in Message a model and Parse JSON to confirm the structure (email, sms, slack, task.api_body). Check that the email and Slack messages look good and that Salesforce Tasks are created, assigned to the right Owner, and linked to the correct Opportunity. Go live Re-enable the Schedule Trigger. Monitor the first few days to confirm that follow-ups, Slack alerts, and Tasks all behave as expected, then let the automation quietly keep your pipeline clean and moving.

Automatically publish blog content to WordPress with AI-generated branded images, internal linking, and client reporting using Google Sheets, OpenAI, and Gemini What this workflow does This workflow receives written blog content from your content creation automation and handles the complete WordPress publishing process. It adds internal links to your content based on target keywords, generates 3 AI-powered branded images (thumbnail + 2 content images), uploads them to WordPress, inserts them into your article, publishes the complete blog with proper categories, updates tracking sheets, and notifies clients automatically. Perfect for agencies managing multiple client blogs who want to eliminate manual publishing tasks while maintaining brand consistency and SEO optimization. Key features Intelligent internal linking: Automatically analyzes your target keywords and adds up to 3 natural anchor links within the content to improve site SEO and user navigation AI image generation: Creates 3 professional branded images using DALL-E based on your blog topic and brand colors - one thumbnail with overlay text and two supporting content images Automated WordPress publishing: Publishes blogs with proper categories, sets featured images, and handles all WordPress REST API interactions without manual intervention Multi-client management: Processes different projects based on individual client settings including image preferences, brand colors, and reporting requirements Tracking and reporting: Updates Google Sheets with live URLs and publish dates, sends Discord notifications to project managers, and triggers client reporting workflows How it works Receives content from writing automation: Triggered by your blog content creation workflow with title, body content, focus keyword, and client details Fetches project configuration: Loads client-specific settings from Google Sheets including website URL, WordPress API credentials, image creation preferences, and brand guidelines Adds internal links: Retrieves target keywords and URLs from project sheets, filters valid links, and uses Gemini AI to intelligently insert 3 contextual anchor links Generates branded images (if enabled): Uses OpenAI GPT to create detailed image prompts based on blog topic and brand colors, then generates 3 images with DALL-E (thumbnail with text overlay + 2 content images) Uploads to WordPress media library: Processes each image through a loop, uploads to WordPress, stores metadata including URLs and alt text Inserts images into content: Uses Gemini AI to intelligently place images at strategic positions within the article while preserving existing HTML structure and anchor links Publishes to WordPress: Creates the blog post with proper title, content, categories, and sets the thumbnail as featured image via REST API Updates tracking sheets: Records the live blog URL and publish date in Google Sheets for project management Sends notifications: Triggers Discord alerts for project managers and executes the Reporting Manager workflow for client communication via email, Slack, or WhatsApp Setup requirements Tools you'll need: Active n8n instance (self-hosted or n8n Cloud) Google Sheets with OAuth access for project management WordPress site with REST API enabled and proper authentication OpenAI API key (for DALL-E image generation) Google Gemini API key (for content processing) Discord bot (optional, for team notifications) Blog Content Creation workflow (Part 1 - sold separately or built independently) Estimated setup time: 30-40 minutes Configuration steps Add credentials in n8n: Google Sheets OAuth API OpenAI API (for DALL-E image generation) Google Gemini API (for AI content processing) Discord Bot API (for notifications) WordPress credentials (API tokens) Set up Project Central Sheet: Create a master Google Sheet with these columns: Client ID Website URL Blog API (WordPress auth token) GMB Name (business name) Image Creation (Yes/No) Image Instructions (specific image guidelines) Color and Font (brand colors in hex format) Discord Channel ID Project Manager Discord ID On Page Sheet (URL to client's tracking sheet) Project Information Sheet (URL to internal linking keywords sheet) Categories (WordPress category IDs) Update the sheet URL in the "Fetch Project Configuration" node Create client-specific sheets: For each client, maintain two sheets: Sheet 1: TGT Keywords (for internal linking) Keywords column: Target keywords to link Target Pages column: Full URLs to link to Sheet 2: Content Requirement & Posting (for tracking) row_number: Unique identifier Focus Keyword: Target SEO keyword Content Topic: Blog title Publish URLs: Live blog URL (auto-filled) Published Date: Publish date (auto-filled) Configure WordPress authentication: Enable REST API on your WordPress site Generate API authentication tokens Update authorization values in these nodes: "Upload to WordPress Media" "Publish Blog with Featured Image" "Set Thumbnail as Featured Image" "Publish Blog without Images" Connect to Blog Creation workflow: Ensure your Blog Content Creation workflow (Part 1) triggers this workflow The trigger should pass these workflow inputs: Client ID Blog S.NO. (row number) Blog Title Content (HTML formatted) OnPage SEO (tracking sheet URL) Focus Keyword Set up Reporting Manager (optional): Create or connect your client reporting workflow Update the workflow ID in "Trigger Client Reporting Workflow" node This sends automated reports to clients via email, Slack, or WhatsApp Test the workflow: Run your Blog Creation workflow manually with test data Verify images generate correctly with brand colors Check WordPress post publishes with featured image Confirm tracking sheet updates Test Discord notification delivery Use cases Marketing agencies: Manage blog publishing for 10+ clients with different brand guidelines and WordPress sites from a single automation Content teams: Eliminate 2-3 hours of manual work per blog by automating image creation, internal linking, and WordPress publishing SEO specialists: Ensure consistent internal linking and proper category assignment across all published content Freelance writers: Offer end-to-end blog services including branded image creation and WordPress publishing without manual intervention SaaS companies: Maintain consistent blog publishing schedule across multiple product blogs with automated tracking and reporting Customization options Modify image generation: Edit the "Generate Image Prompts with AI" node to change image style, dimensions, or prompt instructions Change DALL-E model or image size in "Generate Image with DALL-E" node Adjust internal linking: Modify the "Add Internal Links to Content" agent prompt to change linking strategy (more/fewer links, different placement rules) Change notification channels: Replace Discord with Slack, email, or webhook notifications Add multiple notification channels in parallel WordPress customization: Add custom fields, tags, or metadata to published posts Integrate with WordPress plugins via REST API extensions Troubleshooting Images not generating: Check OpenAI API key validity and account credits. Verify image prompt node receives content properly. WordPress publish fails: Confirm REST API is enabled, authentication tokens are correct, and site URL is properly formatted with trailing slash. Internal links not appearing: Ensure "TGT Keywords" sheet has valid URLs starting with "http" and filter node is working correctly. Tracking sheet not updating: Verify Google Sheets OAuth connection and that row_number matches between sheets. Discord notification fails: Check Discord bot permissions and channel ID accuracy. Resources n8n documentation WordPress REST API guide OpenAI DALL-E API Google Gemini API Google Sheets API Important notes This workflow is specifically for blog publishing. To use it correctly, you must first have a Blog Content Creation workflow that generates the blog title, content, and required metadata. I have already shared a Blog Writing Automation workflow, which you can use directly for content creation before running this publishing workflow. Make sure the content creation workflow runs before this publishing workflow, as this setup depends on the generated output. Support Need help or custom development? 📧 Email: info@isawow.com 🌐 Website: https://isawow.com/