Browse 12,955 Workflows

By Incrementors

Quick overview This workflow exposes a webhook-powered document Q&A chatbot that searches a Pinecone vector database with OpenAI embeddings, reranks results with Cohere, optionally falls back to Google Gemini, and returns an answer with quoted sources plus Google Drive view and download links for the referenced files. How it works Receives a POST request via webhook with the user’s question in the message field. Searches a Pinecone knowledge base using OpenAI embeddings, reranks the top matches with Cohere, and uses an OpenAI chat model (with Google Gemini as fallback) to produce an answer that includes the document name, page number, and an exact supporting quote. Sends the generated answer to a second OpenAI-based agent that extracts only the referenced source file names into structured JSON. Splits the extracted file-name list into individual items and searches Google Drive for each file to retrieve its file ID. Builds Google Drive view and direct download URLs for the matched files and packages them together with the AI answer. Responds to the original webhook request with the answer content and the assembled source links. Setup Add credentials for OpenAI (chat model and embeddings), Pinecone, Cohere, and Google Gemini (fallback model). Connect Google Drive OAuth credentials and ensure the workflow has access to the Drive location containing your source PDFs. Replace YOUR_PINECONE_INDEX_NAME with your Pinecone index name and confirm your PDFs are already embedded and stored in that index. Activate the workflow, copy the webhook URL, and configure your client (website widget, Slack app, etc.) to POST JSON containing a message field. An n8n automation workflow template by Incrementors.

By WeblineIndia

Quick overview This workflow receives an RFx completion webhook, scores suppliers against cost, risk, lead time, and rating constraints, generates award scenarios, and uses Groq (LangChain agent) to produce a structured procurement recommendation, then stores results in Notion and posts success or failure alerts to Slack. How it works Receives an HTTP POST webhook with an RFx ID, a suppliers array, and optional evaluation constraints. Validates that at least one supplier is provided, and if not, posts an error to Slack and returns an “invalid input” webhook response. Filters and scores suppliers using weighted cost, risk, lead time, and rating factors, then selects three scenarios (best cost, lowest risk, and balanced) and returns a ranked supplier list. Sends the scenario data to a Groq-hosted LLM via a LangChain agent to generate a JSON-only executive summary, insights, trade-off analysis, and a final recommendation. Parses and validates the AI JSON output, and if it fails, posts an error to Slack and returns an “AI error” webhook response. Stores the recommendation and insights in a Notion database, posts a completion message to a Slack channel, and returns a success response to the original webhook request. Setup Copy the webhook URL from the Webhook trigger and configure your RFx system to POST rfx_id, suppliers[] (with cost, risk, lead_time, rating), and optional constraints to that endpoint. Add Groq API credentials for the LangChain Groq Chat Model used by the AI analysis step. Add Notion credentials and select the target database, ensuring it has properties for RFx ID, Best Supplier, Executive Summary, Cost Insight, Risk Insight, Trade-off, and Final Recommendation. Add Slack credentials and set the target channel for both success and failure notifications. Review and adjust the scoring weights and constraint defaults in the supplier scoring logic to match your award criteria. Additional info Customization Change scoring weights in code node Add new constraints (e.g., location, certifications) Modify AI prompt Customize Slack message format Extend Notion fields Add-ons Email alerts ERP integration Approval workflows Historical supplier tracking Dashboard reporting Use Cases RFQ supplier selection Vendor comparison automation Risk-based sourcing Procurement analytics AI-driven decision making Troubleshooting Guide | Issue | Possible Cause | Solution | | -------------------------- | ----------------------- | ------------------------------------------ | | No suppliers processed | Empty suppliers array | Ensure suppliers are passed correctly | | Workflow stops early | Validation failure | Check webhook payload | | Incorrect scoring | Missing supplier fields | Ensure cost, risk, lead_time, rating exist | | AI output invalid | Improper JSON response | Adjust AI prompt formatting | | Slack not sending messages | Invalid credentials | Reconnect Slack API | | Notion not saving data | Wrong database mapping | Verify database fields | | API returns error | AI validation failed | Check AI output node | | Unexpected results | Constraints too strict | Relax constraints | Need Help? WeblineIndia can help you build advanced automation workflows, integrate AI, scale procurement systems and provide n8n workflows developers for hire. Contact us to build smarter automation solutions. An n8n automation workflow template by WeblineIndia.

By Incrementors

Quick Overview This workflow exposes a webhook that accepts long-form text and uses OpenAI (via an n8n AI Agent) to repurpose it into a summary, key points, a Twitter thread, a LinkedIn post, and an Instagram caption, returning the results as JSON in the webhook response. How it works Receives a POST request on a webhook endpoint containing a content field in the request body. Sends the incoming content to an OpenAI chat model with instructions to generate multiple social-ready formats as a single JSON object. Parses the model’s response into structured JSON and returns an error payload if the response is not valid JSON. Responds to the original webhook request with the generated JSON payload. Setup Add an OpenAI credential to the OpenAI Chat Model used by the AI Agent and select the model you want to run. Copy the webhook’s Production URL and configure your source app to POST JSON with a content field to that endpoint. If using the included internal test call, paste the Production URL into the HTTP Request step’s YOUR_PRODUCTION_WEBHOOK_URL value before executing the test flow. An n8n automation workflow template by Incrementors.

By Scale On Fajar

End-to-End Event e-Ticket Generator & Email Dispatcher This workflow provides a complete, hands-off solution for managing event registrations (perfect for seminars, workshops, or community gatherings). It automatically generates personalized PDF e-tickets complete with dynamic QR codes, securely archives them, and immediately emails the tickets to the registrants. By handling everything from data entry to inbox delivery, this template eliminates manual ticketing bottlenecks for event organizers. How it works Trigger: The workflow listens for new participant registrations added to a Google Sheet. Duplicate & Personalize: It creates a fresh copy of a master Google Doc template and seamlessly replaces text placeholders with the participant's specific data (Name, Ticket ID, etc.). Inject Dynamic QR: It generates a unique QR code via the QuickChart API and injects the image directly into the document using a targeted HTTP Request. Convert & Archive: The customized document is converted into a high-quality PDF and saved to a designated Google Drive folder for the organizer's records. Automated Dispatch: Finally, it triggers an Email node (using Mailketing) to send a personalized welcome email to the participant. The email includes their unique Ticket ID and a direct, accessible link to download their PDF e-Ticket. Set up steps Prepare the Database: Create a Google Sheet to collect participant data (ensure you have columns for Ticket ID, Name, and Email). Design the Template: Create your e-ticket design in Google Docs. Add text placeholders (e.g., {kode_qr}) that match the mapping in the 'Change Custom Variables' node. Configure Google Credentials: Connect your Google account to the Sheets, Docs, and Drive nodes. Update the documentId and folderId to point to your specific files. Set Drive Permissions (Crucial): Ensure the Google Drive folder where your PDFs are saved is set to "Anyone with the link can view". This ensures the download link inside the email works flawlessly for your attendees. Configure Email: Connect your Mailketing API credentials. (Note: You can easily swap this out for n8n's built-in 'Send Email' SMTP node or Gmail node if preferred). Requirements A Google Workspace account (Google Sheets, Docs, and Drive). A Mailketing account (or a standard SMTP / Gmail account). Basic understanding of mapping JSON data between nodes. An n8n automation workflow template by Scale On Fajar.

By Mateusz Skorupa

Quick overview Gemini reads every Contact Form 7 submission and sorts it into lead, support or spam. Leads are scored from 1 to 5 and saved to HubSpot with a note, support requests go to their own Slack channel, and spam never reaches your CRM. How it works New Lead Webhook receives the form fields as JSON from WordPress, for example {"your-name": "Ada Lovelace", "your-email": "ada@example.com", "your-message": "..."}. WordPress calls it once per submission, right after Contact Form 7's own spam check. Header Auth keeps the endpoint private. Settings holds a one-line description of your business, the score that counts as a hot lead, your two Slack channels and the names of your form's email, name and message fields. Lead Fields is a short Code node that reads those fields, splits the name for HubSpot and collects every other field (phone, subject, consent boxes) for the alerts. Qualify Lead sends the submission and your business description to Gemini Chat Model and gets back a category (lead, support or spam), a score from 1 to 5 and a one-line summary, checked against a JSON schema. Lead Verdict adds the verdict to the lead. If Gemini fails or answers outside the schema, the lead goes to sales unscored, so a model outage never loses a lead. A submission with no email and no message is sent to sales as a setup warning instead of being called spam. Route Lead sends leads to HubSpot, support requests to Notify Support and spam to Ignore Spam. Has Email sends leads without an email address straight to the alert, since HubSpot needs one. Save to HubSpot creates the contact, or updates it when the email is already there. When Contact Saved sees a contact ID, Add Note attaches the verdict and the full message as a HubSpot note, so a returning visitor's earlier messages are kept. Sales Alert and Notify Sales post the lead to your sales channel with the score, a :fire: for hot leads, the link to the HubSpot record, and a warning if HubSpot rejected the lead or the note failed. The whole submission is always in the alert. Setup Open Settings. Describe your business in one sentence in business, since Gemini scores leads against it. Set sales_channel and support_channel, and adjust hot_score (default 4). If your form renamed the default fields, enter the new names for email_field, name_field and message_field. For an EU-hosted HubSpot account, change hubspot_app_url to https://app-eu1.hubspot.com. Open New Lead Webhook, add a Header Auth credential (for example X-Webhook-Token with a long random value) and copy the production URL. Create a Gemini API key and connect it on Gemini Chat Model. The template uses gemini-3.1-flash-lite, a small, fast model that is enough for sorting enquiries. In HubSpot, create a private app with the crm.objects.contacts.read and crm.objects.contacts.write scopes and connect its access token as a HubSpot App Token credential on Save to HubSpot and Add Note. Create a Slack app with the chat:write scope, connect its bot token on Notify Sales and Notify Support, and invite the app to both channels (/invite @your-app), or Slack answers not_in_channel. In WordPress, send the form fields as JSON to the webhook URL on the wpcf7_before_send_mail hook. The free Webhook Actions plugin does it without code: new webhook on wpcf7_before_send_mail, map args.2.fields.your-name, args.2.fields.your-email and args.2.fields.your-message to the same names, add args.0.title as form_title and args.2.meta.url as page_url, and attach the header credential. Or import the ready-made build with exactly this setup. A short PHP snippet that does the same is under Additional info. Activate the workflow and send a realistic enquiry through your form. A message that only says "test" is sorted as spam and stops at Ignore Spam, which you can see in the execution list. Requirements WordPress with Contact Form 7 A Gemini API key, a HubSpot account (a free CRM account works) and a Slack workspace Customization Change what counts as a lead, support or spam by editing the category descriptions in Qualify Lead's schema, for example to add a "job application" category and a fourth output on Route Lead. Swap Gemini Chat Model for OpenAI, Anthropic or a local model; Qualify Lead works with any chat model node. Store the score in HubSpot: create a custom contact property and set it in Save to HubSpot from score. Send support requests to your help desk instead of Slack by replacing Notify Support; ai_summary and summary are ready to use. Additional info Who is this for. Small businesses and agencies whose leads arrive through a Contact Form 7 form on WordPress, and who are tired of sorting sales enquiries from support questions and SEO pitches by hand. Contact Form 7 saves nothing to the database, so there is no list to poll: without a webhook, the notification email is the only copy of a lead. Why before_send_mail. Contact Form 7 validates the fields and runs its spam check first, then fires wpcf7_before_send_mail, and only then sends the email. Hooking in there means obvious spam never reaches the workflow, and a broken mail setup no longer loses leads. Gemini then catches the human-written spam that gets past Contact Form 7. WordPress side without a plugin. Put this in functions.php or a custom plugin. List your form's field names in $fields, and replace the URL and the token with yours (the token must match the Header Auth credential in n8n): add_action( 'wpcf7_before_send_mail', function () { // Contact Form 7 has validated the fields and passed its spam check by now. $fields = [ 'your-name', 'your-email', 'your-subject', 'your-message' ]; $payload = []; foreach ( $fields as $field ) { $payload[ $field ] = sanitize_textarea_field( wp_unslash( $_POST[ $field ] ?? '' ) ); } $payload['form_id'] = absint( $_POST['_wpcf7'] ?? 0 ); $payload['page_url'] = get_permalink( absint( $_POST['_wpcf7_container_post'] ?? 0 ) ) ?: ''; $args = []; $args'headers' = 'application/json'; $args'headers' = 'YOUR-TOKEN'; $args['body'] = wp_json_encode( $payload ); $args['blocking'] = false; // do not make the visitor wait for n8n wp_remote_post( 'https://YOUR-N8N/webhook/wordpress-cf7-lead', $args ); } ); `. An n8n automation workflow template by Mateusz Skorupa.

By Ali Amin

Quick overview This workflow searches Google Places via Serper.dev for local businesses across multiple areas, enriches and scores each lead using website email extraction and Hunter.io, and appends the results to Google Sheets with an optional HMAC-signed webhook sync back to your CRM. How it works Runs manually or starts from an optional webhook request that can pass a run ID and maximum number of leads to capture. Builds area-based Google Places queries and calls Serper.dev to fetch place results for each area, then filters by name rules and deduplicates overlapping matches. Caps the lead list to the requested maximum and removes businesses whose Place ID already exists in your Google Sheets to avoid reprocessing. For each remaining business, fetches the website homepage and contact page and extracts a contact email limited to the business’s own domain. If no email is found on the site, queries Hunter.io domain search to find an email and enrich the record with contact name and position when available. Scores the lead (email/phone/website/named contact), assigns a Hot/Warm/Cold tier, appends the row to Google Sheets, and optionally batches qualified leads to send to your CRM with an HMAC-SHA256 signature. Setup Add a Serper.dev API key as an HTTP Header Auth credential (header name X-API-KEY) and attach it to the Serper request. Add a Hunter.io API key as an HTTP Query Auth credential (query parameter api_key) and attach it to the Hunter.io request. Connect Google Sheets OAuth for both Google Sheets nodes, select your target spreadsheet and sheet, and ensure row 1 includes headers like Company, Email, Phone, Website, Address, Place ID, and Captured On. Update the search configuration in the code block (business type, areas, name include/exclude keywords, optional extra email domains, and default max leads). If using CRM sync, set your shared secret for HMAC signing, replace the CRM webhook URL, and copy the workflow’s incoming webhook URL into your CRM to start runs by POSTing { run_id, maxLeads }. Requirements A free Serper.dev API key for Google Places search (header auth: X-API-KEY) A free Hunter.io API key for email finding and enrichment (query auth: api_key) A Google account with a spreadsheet for the lead log (headers: Company, Email, Phone, Website, Address, Place ID, Captured On) Optional: your own CRM webhook endpoint and a shared secret if you want signed lead batches pushed back Customization Set BUSINESS_TYPE and AREAS in the CONFIGURE block to target any niche and any city or postcode districts Use NAME_KEYWORDS and EXCLUDE_NAMES to keep results on-topic and skip national chains and franchises Adjust the lead scoring weights (email +45, phone +25, website +20, named contact +10) and the Hot/Warm/Cold thresholds to match your qualification criteria Delete the CRM branch to run Sheets-only, or keep it and connect your endpoint for HMAC-signed lead batches Swap Google Sheets for Airtable, HubSpot or Pipedrive as the lead store Additional info About the creator: Built and maintained by Ali Amin, founder of IhsanOps (https://ihsanops.ai) — a UK-based AI automation consultancy building lead generation, enrichment and CRM automations for agencies and SME service businesses. Want this adapted to your niche, data sources or CRM? Get in touch via ali@ihsanops.ai or https://linkedin.com/in/ali-tm-amin. An n8n automation workflow template by Ali Amin.

By Lead

Quick Overview This workflow searches Google Maps via Apify, extracts business websites, finds and verifies email addresses from those sites, and then appends or updates the resulting lead records in Google Sheets. How it works Starts manually when you execute the workflow. Sends the configured search term, location, result limit, and minimum review count to Apify’s Google Maps Scraper to collect businesses that have websites. Builds a unique list of the collected business websites and passes it to Apify’s Website Email Finder to extract email addresses from each site. Deduplicates the discovered email addresses and sends them to Apify’s Bulk Email Verifier to check deliverability. Joins Google Maps business data with the found emails and verification results, filters out duplicates and non-deliverable emails (optionally keeping catch-all results), and formats rows for export. Appends new rows to Google Sheets or updates existing ones by matching on the email address. Setup Add an Apify API token credential, and select it in the three Apify nodes (Google Maps Scraper, Website Email Finder, and Bulk Email Verifier). Add a Google Sheets OAuth credential, then select the target spreadsheet and sheet in the Google Sheets node. Ensure the sheet has headers that match the output fields (for example: business, category, email, email_status, phone, website, address, rating, reviews, maps_url, email_source, found_at). Update the search parameters (searchTerm, location, maxBusinesses, minReviews, and keepCatchAll) to match the leads you want to collect. An n8n automation workflow template by Lead.

By Abu Bakar

Quick overview Our workflow takes product data, generates AI images and voiceover, stores assets in Google Drive, then combines everything into a 9:16 video with automatic captions using JSON2Video. How it works Receives a product description and product image from an n8n Form Trigger submission. Uploads the submitted image to Google Drive and sends the description to Groq to generate three cinematic scene prompts. Downloads a sample reference image from Google Drive and uses OpenAI image editing (gpt-image-1-mini) to generate three scene images from the prompts, uploading each generated image back to Google Drive. Uses Groq to write a single-paragraph voiceover script based on the three scenes, then generates an audio voiceover with OpenAI and uploads the audio file to Google Drive. Lists and downloads the uploaded scene images from a Google Drive folder, then compiles a JSON2Video project payload that assembles the three images into timed scenes with audio and subtitle settings. Sends the payload to JSON2Video to render the video, waits briefly, checks rendering status, downloads the final video file, and returns it as the form completion response. Setup Add Groq API credentials for the two Groq chat model steps (openai/gpt-oss-120b and openai/gpt-oss-20b). Add OpenAI credentials (or enable n8n’s AI Gateway) for image generation and audio generation. Connect a Google Drive OAuth2 account, ensure the target Drive folder used for scenes/audio exists and is accessible, and update any file/folder IDs if you don’t want to use the provided ones. Create a JSON2Video account, replace the hardcoded x-api-key header value with your own API key, and adjust the project JSON (resolution, scene durations, subtitles) if needed. Requirements Product information Google Drive account OpenAI account Groq account JSON2Video API key Publicly accessible Google Drive files n8n Cloud workflow Internet connection Customization Product information Google Drive account OpenAI account Groq account JSON2Video API key Publicly accessible Google Drive files n8n Cloud workflow Internet connection Additional info Branding, colors, fonts, logo, background music, transitions, animations, call-to-action text, product positioning, scene order, video duration, and export format. An n8n automation workflow template by Abu Bakar.

By Paras Gediya

Quick overview This workflow connects WhatsApp and Telegram to six specialist OpenAI agents for sales, supplier management, inventory, invoices, appointments and customer support. It retrieves business knowledge from Google Sheets, records validated actions in PostgreSQL, and supports Telegram administrator approvals and automated customer replies. How it works Receives incoming WhatsApp Business Cloud API and Telegram messages, or starts with a manual sample event for testing. Normalizes message text, sender information and attachment metadata. Loads the configured business profile, identifies trusted suppliers and prevents duplicate event processing using PostgreSQL. Recognizes authorized Telegram administrator approval or rejection commands and processes the corresponding pending proposals. For regular messages, retrieves approved business knowledge and recent conversation history from PostgreSQL. Uses a central OpenAI orchestrator to coordinate six specialist AI agents: Sales & Leads, Supplier & Products, Inventory, Invoices, Appointments and Customer Support. Each specialist can query relevant Google Sheets data. Validates proposed actions against enabled agents, sender roles, permitted operations and data requirements before recording validated outcomes in PostgreSQL. Synchronizes supported product changes to Google Sheets, sends Telegram administrator notifications when required and optionally replies to the original WhatsApp or Telegram sender. Setup Create a PostgreSQL database and run the supplied SQL setup script to install the required uam_* tables and functions. Create a Google Spreadsheet using the supplied templates, including BusinessFAQ, Products, Inventory, InvoiceRules and BookingRules. Configure the PostgreSQL, OpenAI, Google Sheets, Telegram and WhatsApp credentials in your n8n instance. Edit the Configure Business Profile node. Set the business ID and name, industry, spreadsheet ID, administrator Telegram chat ID, trusted supplier identifiers, enabled agents and automatic-reply preference. Connect your WhatsApp Business Cloud API account and Telegram bot. Ensure your n8n instance has a publicly accessible HTTPS webhook endpoint for live message delivery. Run the manual sample trigger to verify database processing. Test both messaging channels, product updates, administrator approvals and customer replies before activating the workflow for production use. Requirements An n8n instance supporting AI Agent Tool nodes, PostgreSQL and the native WhatsApp and Telegram integrations. PostgreSQL database with the supplied SQL schema and functions. OpenAI API credentials and an account with access to the configured chat model. Google Sheets credentials and a spreadsheet containing the required knowledge-base tabs. Telegram bot and administrator chat ID; WhatsApp Business Cloud API credentials for WhatsApp integration. Public HTTPS webhook access and the permissions required by each connected account. Customization Enable or disable specialist AI agents based on your business requirements. Customize the business profile, industry, supplier allowlists and automatic-response settings. Replace the sample Google Sheets data with your own FAQs, product information, inventory records, invoice rules and booking policies. Modify each specialist agent's system instructions to reflect your business terminology and operating procedures. Configure administrator notifications and approval rules for sensitive actions. Adapt the workflow for retail, e-commerce, wholesale, manufacturing, professional services and other supported business operations. Additional info This template is designed for a single business installation and can be customized for different industries. It processes text messages and attachment metadata. Full image, video, audio transcription and PDF-content analysis are not included in this version. Product synchronization supports one product variant per incoming message and requires reliable product identifiers for duplicate prevention. Appointments are recorded as unconfirmed requests. Automatic calendar bookings, marketplace listing publication and invoice payments are not implemented. Administrator approval is required for supported sensitive changes. Complete live integration and security testing before production deployment. An n8n automation workflow template by Paras Gediya.

By Hồ Đình Huy

Quick overview This workflow runs daily (or manually) to pull attendance logs for all users in a Lark department via the Lark Open Platform APIs, then writes each user’s first check-in and last check-out into a Lark Base (Bitable) table in batches. How it works Runs on a daily schedule at 23:30 or starts manually for testing. Requests a Lark tenant access token using your Lark app ID and app secret. Fetches the list of users in the configured Lark department. Calculates the current day’s start and end timestamps in the configured timezone and prepares one query per user. Queries Lark Attendance for each user’s check-in/out flows within the day window. Consolidates results per user per day, keeping the first check-in and last check-out and deriving on-time/late and early-out statuses. Batch-creates records in the target Lark Base (Bitable) table with the attendance details. Setup Create a Lark app with access to Contact, Attendance, and Bitable APIs, then fill in app_id and app_secret in Template Config. Set your department_id (open_department_id) in Template Config and adjust departmentPageSize if needed. Create or choose a Lark Base (Bitable) app and table, then set bitable_AppToken and bitable_TableId in Template Config. Ensure the target Bitable table has the required fields (Employee, Check In/Out Time, comments, location, Employee Code, and the two status single-select fields with the specified values). Optionally adjust timezone, bitableBatchSize, and the check-in/check-out cutoff times in Template Config to match your attendance rules. An n8n automation workflow template by Hồ Đình Huy.

By nexum

Quick Overview This workflow runs every Monday at 08:00, reads invoices from Google Sheets, filters for unpaid invoices with no prior follow-up and more than 7 days overdue, sends an HTML reminder email via Gmail, and updates the sheet to mark the invoice as followed up. How it works Runs every Monday at 08:00 on a schedule. Reads all invoice rows from a Google Sheets spreadsheet. Keeps only invoices where the status is “Impayé” and the “Date de relance” field is empty, then calculates the number of days overdue from the invoice date. Filters to invoices that are more than 7 days overdue. Sends a formatted HTML payment reminder email via Gmail with the invoice date, amount, and days overdue. Updates the matching Google Sheets row to set the status to “Relancé” and writes today’s follow-up date. Setup Add Google Sheets credentials and ensure the target spreadsheet contains columns like Statut, Date de relance, Date_Facture, Client, and Montant. Add Gmail credentials for the mailbox that sends reminders. Update the Google Sheets document URL/sheet selection and set the recipient address in the Gmail “sendTo” field (and optionally adapt the subject/body text). An n8n automation workflow template by nexum.

By Incrementors

Quick overview This workflow collects a customer review via an n8n form, uses OpenAI to analyze and score it, then either generates a 7-piece content pack and emails it to you or sends a short “below threshold” note, while logging every submission to Google Sheets. How it works Receives a review submission through an n8n Form (review text, reviewer details, and your business info). Uses OpenAI to extract structured “review intelligence” (tone, transformation, best quote, credibility signals) and assign a content opportunity score. Routes the submission based on whether the score meets the threshold (7+). For high-scoring reviews, uses OpenAI to generate seven platform-ready assets (LinkedIn long/short posts, X post, website testimonial, newsletter feature, thank-you email, and case study invite). Compiles the generated content into a single email body and appends the key fields to a Google Sheets “Review Content Log” tab. Sends the full content package to the configured recipient via Gmail. For below-threshold reviews, logs a “not generated” entry to Google Sheets and emails a brief explanation with suggestions to improve the testimonial. Setup Add an OpenAI API credential and connect it to both OpenAI chat model steps used for analysis and content generation. Add Google Sheets OAuth2 credentials, create a spreadsheet tab named “Review Content Log” with the required headers, and set your Google Sheet ID in the configuration values. Add Gmail OAuth2 credentials for sending emails and set the recipient email and sender name values in the configuration step. Activate the workflow and share or embed the generated form URL so your team can submit reviews. An n8n automation workflow template by Incrementors.