HumationHuman + Automation
Back to Catalog

Generate event speaker recommendations with Claude AI and Google Sheets

Oneclick AI SquadOneclick AI Squad
116 views
2/3/2026
GMailGoogle DriveAutomationAttachmentsEmail
Official Page

Simplify event planning with this automated n8n workflow. Triggered by incoming requests, it fetches speaker and audience data from Google Sheets, analyzes profiles and preferences, and generates optimized session recommendations. The workflow delivers formatted voice responses and updates tracking data, ensuring organizers receive real-time, tailored suggestions. 🎙️📊

Key Features

  • Real-time analysis of speaker and audience data for personalized recommendations.
  • Generates optimized session lineups based on profiles and preferences.
  • Delivers responses via voice agent for a seamless experience.
  • Logs maintain a detailed recommendation history in Google Sheets.

Workflow Process

  • The Webhook Trigger node initiates the workflow upon receiving voice agent or external system requests.
  • Parse Voice Request processes incoming voice data into actionable parameters.
  • Fetch Database retrieves speaker ratings, past sessions, and audience ratings from Google Sheets.
  • Calculate & Analyze combines voice request data with speaker profiles and audience insights for comprehensive matching.
  • AI Optimization Engine analyzes speaker-audience fit and recommends optimal session lineups.
  • Format Recommendations structures the recommendations for voice agent response.
  • Voice Agent Response returns formatted recommendations to the user with natural language summary and structured data.
  • Update Tracking Sheet saves recommendation history and analytics to Google Sheets.
  • If errors occur, the Check for Errors node branches to:
    • Format Error Response prepares an error message.
    • Send Error Response delivers the error notification.

Setup Instructions

  • Import the workflow into n8n and configure Google Sheets OAuth2 for data access.
  • Set up the Webhook Trigger with your voice agent or external system's API credentials.
  • Configure the AI Optimization Engine node with a suitable language model (e.g., Anthropic Chat Model).
  • Test the workflow by sending sample voice requests and verifying recommendations.
  • Adjust analysis parameters as needed for specific event requirements.

Prerequisites

  • Google Sheets OAuth2 credentials
  • Voice agent API or integration service
  • AI/LLM service for optimization (e.g., Anthropic)
  • Structured speaker and audience data in a Google Sheet

Google Sheet Structure:

  1. Create a sheet with columns:
    • Speaker Name
    • Rating
    • Past Sessions
    • Audience Rating
    • Preferences
    • Updated At

Modification Options

  • Customize the Calculate & Analyze node to include additional matching criteria (e.g., topic expertise).
  • Adjust the AI Optimization Engine to prioritize specific session formats or durations.
  • Modify voice response templates in the Voice Agent Response node with branded phrasing.
  • Integrate with event management tools (e.g., Eventbrite) for live data feeds.
  • Set custom error handling rules in the Check for Errors node.

Discover more workflows – Get in touch with us

Generate Event Speaker Recommendations with Claude AI and Google Sheets

This n8n workflow automates the process of generating event speaker recommendations using Claude AI, triggered by a webhook, and potentially interacting with Google Sheets. It provides a flexible framework for integrating AI-powered suggestions into your event planning.

What it does

This workflow is designed to:

  1. Receive a Trigger: It starts by listening for incoming data via a Webhook. This data likely contains information relevant to generating speaker recommendations (e.g., event topic, desired speaker profiles).
  2. Process Data with AI: It utilizes an AI Agent, specifically configured with an Anthropic Chat Model (like Claude), to process the incoming data and generate speaker recommendations.
  3. Conditional Logic (Optional): An "If" node is present, suggesting the workflow can incorporate conditional logic to branch based on certain criteria from the input or AI output.
  4. Respond to Webhook: It sends a response back to the originating webhook, likely containing the generated speaker recommendations or a status update.
  5. Interact with Google Sheets (Optional): A Google Sheets node is included, indicating the potential to read from or write speaker-related data to a Google Sheet.
  6. Custom Code Execution (Optional): A Code node allows for custom JavaScript logic to be executed at some point in the workflow, offering advanced data manipulation or integration possibilities.

Prerequisites/Requirements

To use this workflow, you will need:

  • n8n Instance: A running n8n instance to import and execute the workflow.
  • Webhook: An external system or application capable of sending HTTP requests to the n8n webhook URL.
  • Anthropic API Key: Credentials for an Anthropic account to use their Chat Model (e.g., Claude).
  • Google Sheets Account: If you intend to use the Google Sheets functionality, you will need a Google account with access to the relevant spreadsheet.
  • n8n Credentials: Configure your n8n instance with the necessary credentials for Anthropic and Google Sheets.

Setup/Usage

  1. Import the Workflow: Download the provided JSON and import it into your n8n instance.
  2. Configure Webhook:
    • Activate the "Webhook" trigger node.
    • Copy the generated webhook URL. This URL will be used by your external system to trigger the workflow.
  3. Set Up Anthropic Credentials:
    • In the "Anthropic Chat Model" node, select or create a new Anthropic API credential.
    • Enter your Anthropic API Key.
  4. Configure Google Sheets (if applicable):
    • In the "Google Sheets" node, select or create a new Google Sheets credential.
    • Grant n8n the necessary permissions to access your Google Sheets.
    • Configure the node to read from or write to your desired spreadsheet and sheet.
  5. Configure AI Agent:
    • Review the "AI Agent" node settings. Ensure it's correctly configured to use the "Anthropic Chat Model" and any specific instructions or tools required for generating speaker recommendations.
  6. Customize "If" and "Code" Nodes (if applicable):
    • Adjust the conditions in the "If" node based on your specific routing logic.
    • Modify the JavaScript code in the "Code" node for any custom data processing or logic.
  7. Activate the Workflow: Once all configurations are complete, activate the workflow in n8n.
  8. Trigger the Workflow: Send an HTTP POST request to the webhook URL from your external system with the relevant data to initiate the speaker recommendation process.
  9. Review Output: The workflow will respond to the webhook with the generated recommendations. You can also inspect the execution history in n8n to see the data flow and AI outputs.

Related Templates

Track competitor SEO keywords with Decodo + GPT-4.1-mini + Google Sheets

This workflow automates competitor keyword research using OpenAI LLM and Decodo for intelligent web scraping. Who this is for SEO specialists, content strategists, and growth marketers who want to automate keyword research and competitive intelligence. Marketing analysts managing multiple clients or websites who need consistent SEO tracking without manual data pulls. Agencies or automation engineers using Google Sheets as an SEO data dashboard for keyword monitoring and reporting. What problem this workflow solves Tracking competitor keywords manually is slow and inconsistent. Most SEO tools provide limited API access or lack contextual keyword analysis. This workflow solves that by: Automatically scraping any competitor’s webpage with Decodo. Using OpenAI GPT-4.1-mini to interpret keyword intent, density, and semantic focus. Storing structured keyword insights directly in Google Sheets for ongoing tracking and trend analysis. What this workflow does Trigger — Manually start the workflow or schedule it to run periodically. Input Setup — Define the website URL and target country (e.g., https://dev.to, france). Data Scraping (Decodo) — Fetch competitor web content and metadata. Keyword Analysis (OpenAI GPT-4.1-mini) Extract primary and secondary keywords. Identify focus topics and semantic entities. Generate a keyword density summary and SEO strength score. Recommend optimization and internal linking opportunities. Data Structuring — Clean and convert GPT output into JSON format. Data Storage (Google Sheets) — Append structured keyword data to a Google Sheet for long-term tracking. Setup Prerequisites If you are new to Decode, please signup on this link visit.decodo.com n8n account with workflow editor access Decodo API credentials OpenAI API key Google Sheets account connected via OAuth2 Make sure to install the Decodo Community node. Create a Google Sheet Add columns for: primarykeywords, seostrengthscore, keyworddensity_summary, etc. Share with your n8n Google account. Connect Credentials Add credentials for: Decodo API credentials - You need to register, login and obtain the Basic Authentication Token via Decodo Dashboard OpenAI API (for GPT-4o-mini) Google Sheets OAuth2 Configure Input Fields Edit the “Set Input Fields” node to set your target site and region. Run the Workflow Click Execute Workflow in n8n. View structured results in your connected Google Sheet. How to customize this workflow Track Multiple Competitors → Use a Google Sheet or CSV list of URLs; loop through them using the Split In Batches node. Add Language Detection → Add a Gemini or GPT node before keyword analysis to detect content language and adjust prompts. Enhance the SEO Report → Expand the GPT prompt to include backlink insights, metadata optimization, or readability checks. Integrate Visualization → Connect your Google Sheet to Looker Studio for SEO performance dashboards. Schedule Auto-Runs → Use the Cron Node to run weekly or monthly for competitor keyword refreshes. Summary This workflow automates competitor keyword research using: Decodo for intelligent web scraping OpenAI GPT-4.1-mini for keyword and SEO analysis Google Sheets for live tracking and reporting It’s a complete AI-powered SEO intelligence pipeline ideal for teams that want actionable insights on keyword gaps, optimization opportunities, and content focus trends, without relying on expensive SEO SaaS tools.

Ranjan DailataBy Ranjan Dailata
161

Generate song lyrics and music from text prompts using OpenAI and Fal.ai Minimax

Spark your creativity instantly in any chat—turn a simple prompt like "heartbreak ballad" into original, full-length lyrics and a professional AI-generated music track, all without leaving your conversation. 📋 What This Template Does This chat-triggered workflow harnesses AI to generate detailed, genre-matched song lyrics (at least 600 characters) from user messages, then queues them for music synthesis via Fal.ai's minimax-music model. It polls asynchronously until the track is ready, delivering lyrics and audio URL back in chat. Crafts original, structured lyrics with verses, choruses, and bridges using OpenAI Submits to Fal.ai for melody, instrumentation, and vocals aligned to the style Handles long-running generations with smart looping and status checks Returns complete song package (lyrics + audio link) for seamless sharing 🔧 Prerequisites n8n account (self-hosted or cloud with chat integration enabled) OpenAI account with API access for GPT models Fal.ai account for AI music generation 🔑 Required Credentials OpenAI API Setup Go to platform.openai.com → API keys (sidebar) Click "Create new secret key" → Name it (e.g., "n8n Songwriter") Copy the key and add to n8n as "OpenAI API" credential type Test by sending a simple chat completion request Fal.ai HTTP Header Auth Setup Sign up at fal.ai → Dashboard → API Keys Generate a new API key → Copy it In n8n, create "HTTP Header Auth" credential: Name="Fal.ai", Header Name="Authorization", Header Value="Key [Your API Key]" Test with a simple GET to their queue endpoint (e.g., /status) ⚙️ Configuration Steps Import the workflow JSON into your n8n instance Assign OpenAI API credentials to the "OpenAI Chat Model" node Assign Fal.ai HTTP Header Auth to the "Generate Music Track", "Check Generation Status", and "Fetch Final Result" nodes Activate the workflow—chat trigger will appear in your n8n chat interface Test by messaging: "Create an upbeat pop song about road trips" 🎯 Use Cases Content Creators: YouTubers generating custom jingles for videos on the fly, streamlining production from idea to audio export Educators: Music teachers using chat prompts to create era-specific folk tunes for classroom discussions, fostering interactive learning Gift Personalization: Friends crafting anniversary R&B tracks from shared memories via quick chats, delivering emotional audio surprises Artist Brainstorming: Songwriters prototyping hip-hop beats in real-time during sessions, accelerating collaboration and iteration ⚠️ Troubleshooting Invalid JSON from AI Agent: Ensure the system prompt stresses valid JSON; test the agent standalone with a sample query Music Generation Fails (401/403): Verify Fal.ai API key has minimax-music access; check usage quotas in dashboard Status Polling Loops Indefinitely: Bump wait time to 45-60s for complex tracks; inspect fal.ai queue logs for bottlenecks Lyrics Under 600 Characters: Tweak agent prompt to enforce fuller structures like [V1][C][V2][B][C]; verify output length in executions

Daniel NkenchoBy Daniel Nkencho
601

Automate invoice processing with OCR, GPT-4 & Salesforce opportunity creation

PDF Invoice Extractor (AI) End-to-end pipeline: Watch Drive ➜ Download PDF ➜ OCR text ➜ AI normalize to JSON ➜ Upsert Buyer (Account) ➜ Create Opportunity ➜ Map Products ➜ Create OLI via Composite API ➜ Archive to OneDrive. --- Node by node (what it does & key setup) 1) Google Drive Trigger Purpose: Fire when a new file appears in a specific Google Drive folder. Key settings: Event: fileCreated Folder ID: google drive folder id Polling: everyMinute Creds: googleDriveOAuth2Api Output: Metadata { id, name, ... } for the new file. --- 2) Download File From Google Purpose: Get the file binary for processing and archiving. Key settings: Operation: download File ID: ={{ $json.id }} Creds: googleDriveOAuth2Api Output: Binary (default key: data) and original metadata. --- 3) Extract from File Purpose: Extract text from PDF (OCR as needed) for AI parsing. Key settings: Operation: pdf OCR: enable for scanned PDFs (in options) Output: JSON with OCR text at {{ $json.text }}. --- 4) Message a model (AI JSON Extractor) Purpose: Convert OCR text into strict normalized JSON array (invoice schema). Key settings: Node: @n8n/n8n-nodes-langchain.openAi Model: gpt-4.1 (or gpt-4.1-mini) Message role: system (the strict prompt; references {{ $json.text }}) jsonOutput: true Creds: openAiApi Output (per item): $.message.content → the parsed JSON (ensure it’s an array). --- 5) Create or update an account (Salesforce) Purpose: Upsert Buyer as Account using an external ID. Key settings: Resource: account Operation: upsert External Id Field: taxid_c External Id Value: ={{ $json.message.content.buyer.tax_id }} Name: ={{ $json.message.content.buyer.name }} Creds: salesforceOAuth2Api Output: Account record (captures Id) for downstream Opportunity. --- 6) Create an opportunity (Salesforce) Purpose: Create Opportunity linked to the Buyer (Account). Key settings: Resource: opportunity Name: ={{ $('Message a model').item.json.message.content.invoice.code }} Close Date: ={{ $('Message a model').item.json.message.content.invoice.issue_date }} Stage: Closed Won Amount: ={{ $('Message a model').item.json.message.content.summary.grand_total }} AccountId: ={{ $json.id }} (from Upsert Account output) Creds: salesforceOAuth2Api Output: Opportunity Id for OLI creation. --- 7) Build SOQL (Code / JS) Purpose: Collect unique product codes from AI JSON and build a SOQL query for PricebookEntry by Pricebook2Id. Key settings: pricebook2Id (hardcoded in script): e.g., 01sxxxxxxxxxxxxxxx Source lines: $('Message a model').first().json.message.content.products Output: { soql, codes } --- 8) Query PricebookEntries (Salesforce) Purpose: Fetch PricebookEntry.Id for each Product2.ProductCode. Key settings: Resource: search Query: ={{ $json.soql }} Creds: salesforceOAuth2Api Output: Items with Id, Product2.ProductCode (used for mapping). --- 9) Code in JavaScript (Build OLI payloads) Purpose: Join lines with PBE results and Opportunity Id ➜ build OpportunityLineItem payloads. Inputs: OpportunityId: ={{ $('Create an opportunity').first().json.id }} Lines: ={{ $('Message a model').first().json.message.content.products }} PBE rows: from previous node items Output: { body: { allOrNone:false, records:[{ OpportunityLineItem... }] } } Notes: Converts discount_total ➜ per-unit if needed (currently commented for standard pricing). Throws on missing PBE mapping or empty lines. --- 10) Create Opportunity Line Items (HTTP Request) Purpose: Bulk create OLIs via Salesforce Composite API. Key settings: Method: POST URL: https://<your-instance>.my.salesforce.com/services/data/v65.0/composite/sobjects Auth: salesforceOAuth2Api (predefined credential) Body (JSON): ={{ $json.body }} Output: Composite API results (per-record statuses). --- 11) Update File to One Drive Purpose: Archive the original PDF in OneDrive. Key settings: Operation: upload File Name: ={{ $json.name }} Parent Folder ID: onedrive folder id Binary Data: true (from the Download node) Creds: microsoftOneDriveOAuth2Api Output: Uploaded file metadata. --- Data flow (wiring) Google Drive Trigger → Download File From Google Download File From Google → Extract from File → Update File to One Drive Extract from File → Message a model Message a model → Create or update an account Create or update an account → Create an opportunity Create an opportunity → Build SOQL Build SOQL → Query PricebookEntries Query PricebookEntries → Code in JavaScript Code in JavaScript → Create Opportunity Line Items --- Quick setup checklist 🔐 Credentials: Connect Google Drive, OneDrive, Salesforce, OpenAI. 📂 IDs: Drive Folder ID (watch) OneDrive Parent Folder ID (archive) Salesforce Pricebook2Id (in the JS SOQL builder) 🧠 AI Prompt: Use the strict system prompt; jsonOutput = true. 🧾 Field mappings: Buyer tax id/name → Account upsert fields Invoice code/date/amount → Opportunity fields Product name must equal your Product2.ProductCode in SF. ✅ Test: Drop a sample PDF → verify: AI returns array JSON only Account/Opportunity created OLI records created PDF archived to OneDrive --- Notes & best practices If PDFs are scans, enable OCR in Extract from File. If AI returns non-JSON, keep “Return only a JSON array” as the last line of the prompt and keep jsonOutput enabled. Consider adding validation on parsing.warnings to gate Salesforce writes. For discounts/taxes in OLI: Standard OLI fields don’t support per-line discount amounts directly; model them in UnitPrice or custom fields. Replace the Composite API URL with your org’s domain or use the Salesforce node’s Bulk Upsert for simplicity.

Le NguyenBy Le Nguyen
942