Quick overview This workflow runs weekly to query multiple LLMs via OpenRouter with prompts from Google Sheets, analyzes brand mentions and domain citations, aggregates weekly Share of Voice metrics, and emails an HTML visibility report. How it works Runs every week on a schedule trigger. Reads active prompts from a Google Sheets “prompts” tab and expands them into multiple model runs (including repeated runs per model) to create OpenRouter chat completion requests. Sends each request to OpenRouter, normalizes the response into answer text and extracted citation URLs, and appends the results to the Google Sheets “runs” tab. Loads brand definitions from the Google Sheets “brands” tab, scans the latest successful runs for brand mentions and matching citation domains, and writes one mention/citation record per brand-run to the “mentions” tab. Aggregates the mention and citation results into weekly metrics per model (and an “all models” total), including mention rate, citation rate, Share of Voice, and average first-mention position, and appends them to the “weekly_agg” tab.
Tags
Google SheetsWHTTP Request
Send EmailRelated workflows
See all Email Send→WUnique QRcode coupon assignment and validation for Lead Generation with SuiteCRM
This workflow is designed to manage the assignment and validation of unique QR code coupons within a lead generation system with SuiteCRM. How it Works This workflow automates the process of assigning unique QR code coupons to leads generated through a form submission, ensuring no duplicates are created, and validating the usage of coupons. Here's how it operates: Webhook Trigger: The workflow starts with a Webhook node that listens for incoming requests containing QR code data. A Set coupon node extracts the QR code value from the request parameters. Validation of QR Code: An If node checks if the QR code exists in the incoming data. If it does, the process proceeds; otherwise, a "No coupon" response is sent back. Coupon Lookup: The Get Lead node queries a Google Sheets document to check if the QR code corresponds to an existing lead. A subsequent Not used? node verifies whether the coupon has already been used by checking the "USED COUPON?" field in the sheet. Lead Duplication Check: When a new lead submits the form (On form submission), the Duplicate Lead? node checks if the email already exists in the system to prevent duplicates. Coupon Assignment: If the lead is not a duplica
WTrack n8n Community Topics with Keywords and Save to Google Sheets
This template is designed for community managers, developers, and enthusiasts who want to monitor and capture discussions on the n8n community forum by specific keywords. By tracking new topics that match your provided keyword, the workflow automatically logs them into a Google Sheet, helping you keep a pulse on trending discussions and manage community insights effortlessly. How it Works Keyword Monitoring: The workflow continuously monitors the n8n community forum for new topics containing your specified keyword. Data Extraction: When a matching topic is found, relevant details such as id, title, URL, and posting time are extracted. Google Sheets Integration: The extracted information is automatically appended as a new row in your Google Sheet, providing an organized log of community discussions. Alert Option: Optionally, you can add notifications (e.g., Slack messages or emails) to alert you when a new topic is captured, ensuring you never miss an important update. Set Up Steps Import the Workflow: Download and import the workflow into your n8n instance. Configure Keyword Monitoring: In the HTTP Request node, set your desired keyword to filter the n8n community topics. Set Up Go
Docker Registry Cleanup Workflow
Docker Registry Cleanup Template This template is designed to automatically clean up old image tags in the Docker registry and perform garbage collection. Features List all images in the registry Preserve the last 10 tags for each image (latest tag is always preserved) Delete old tags Email notification for Successful/Excused cancellation Registry garbage collection automation Failure notification in error conditions Prerequisites Docker Registry v2 API access Basic Authentication credentials SMTP email settings (for notifications) SSH node installed on n8n (for garbage collection) Installation 1. Identity Information Add the following credentials in n8n: HTTP Basic Auth**: For Registry access SSH Private Key**: For Garbage collection command Email SMTP**: For notifications 2. Set Variables Replace your-registry-url with your actual registry URL on all nodes: ‘url": ‘https://your.registry.com/v2/_catalog’. Customisation Retention Policy: Set the number of tags to be retained by changing the slice(0, 10) value in the Identify Tags to Remove node Schedule: Change the frequency of operation at the Trigger node Notification Content: Customise email templates according to your needs Not