Back to Catalog

Automate lead ranking & task creation with Google Sheets + ClickUp

Rahul JoshiRahul Joshi
171 views
2/3/2026
Official Page

Description

Stop losing warm leads in the noise. This automation analyzes your lead engagement data, calculates priority scores based on activity and last contact date, and automatically queues your top 10 leads for follow-up in ClickUp โ€” complete with suggested send times based on timezone. โšก

What This Template Does

Pulls lead data from Google Sheets (e.g., name, engagement, last contact date, timezone). ๐Ÿ“„ Calculates days since last contact to measure lead freshness. โฐ Combines engagement score and recency into a weighted priority score. ๐Ÿ“Š Sorts and filters top 10 leads for immediate follow-up. ๐Ÿ” Suggests best time to reach out based on each leadโ€™s timezone. ๐ŸŒ Creates corresponding ClickUp tasks with lead details. ๐Ÿ—‚๏ธ Updates the Google Sheet to mark leads as queued. โœ…

Key Benefits

  • Automatically identify high-priority leads daily. ๐ŸŽฏ
  • Increase conversion rates with timely, personalized follow-ups. โฑ๏ธ
  • Eliminate manual sorting and spreadsheet filtering. ๐Ÿšซ
  • Keep sales teams organized with ClickUp task automation. ๐Ÿ’ผ
  • Works perfectly for SDRs, account managers, and B2B teams. ๐Ÿค

Features

  • Google Sheets integration for real-time lead updates. ๐Ÿ“Š
  • Smart recency calculator (days since last contact). โฐ
  • Weighted priority formula (70% engagement, 30% recency). ๐Ÿงฎ
  • ClickUp task creation for seamless team coordination. ๐Ÿ”—
  • Timezone-based follow-up time suggestion. ๐ŸŒ
  • Configurable limit (Top 10 leads โ€” adjustable). โš™๏ธ
  • Automatic sheet update with queue status tracking. ๐Ÿ“‹

Requirements

  1. n8n instance (cloud or self-hosted). ๐Ÿงฐ
  2. Google Sheet with columns: Lead Name, Engagement_Score, Last_Contact_Date, Timezone, Email. ๐Ÿ“‘
  3. Connected Google Sheets and ClickUp credentials in n8n. ๐Ÿ”
  4. Active ClickUp workspace with accessible list or space ID. ๐Ÿงญ

Target Audience

  • Sales and marketing teams managing large lead lists. ๐Ÿ“ˆ
  • B2B organizations using ClickUp for pipeline tracking. ๐Ÿงฉ
  • SDRs who need to prioritize outreach daily. ๐Ÿ—“๏ธ
  • Agencies managing multiple clients and follow-up cadences. ๐Ÿค

Step-by-Step Setup Instructions (Concise)

  • Create or connect a Google Sheet with all required headers. ๐Ÿ“‹
  • Update node credentials for Google Sheets and ClickUp. ๐Ÿ”‘
  • Adjust weightage logic or maxItems count if needed. โš™๏ธ
  • Test workflow using the manual trigger. โ–ถ๏ธ
  • (Optional) Schedule it to run daily for auto-prioritization. โฐ
  • Review ClickUp tasks and follow up with top leads. ๐Ÿ“จ

Security Best Practices

  • Share the Google Sheet only with the n8n Google account (Editor). ๐Ÿ”’
  • Keep ClickUp API credentials encrypted within n8n. ๐Ÿ›ก๏ธ
  • Review ClickUp task creation permissions before activation. โœ…
  • Regularly clean archived leads from the Google Sheet. ๐Ÿงน

Automate Lead Ranking & Task Creation with Google Sheets & ClickUp

This n8n workflow streamlines the process of managing new leads by automatically ranking them and creating corresponding tasks in ClickUp. It listens for new entries in a Google Sheet, processes the lead data, and then creates an organized task in your project management tool.

What it does

  1. Triggers Manually: The workflow is initiated manually by clicking "Execute workflow".
  2. Retrieves Google Sheet Data: It fetches all data from a specified Google Sheet.
  3. Processes Lead Data: A Function node is used to apply custom logic, likely for lead ranking or data transformation, based on the Google Sheet entries.
  4. Limits Data (Optional): A Limit node is present, which can be configured to restrict the number of items processed, useful for testing or handling large datasets in batches.
  5. Sorts Data (Optional): A Sort node is included, allowing the workflow to order the processed lead data based on specific criteria before further actions.
  6. Creates ClickUp Task: For each processed lead, it creates a new task in ClickUp, likely populating task details with information derived from the Google Sheet and the ranking process.

Prerequisites/Requirements

  • Google Sheets Account: With a spreadsheet containing your lead data.
  • ClickUp Account: With a space, folder, and list where tasks will be created.
  • n8n Instance: Running and accessible.

Setup/Usage

  1. Import the Workflow: Import the provided JSON into your n8n instance.
  2. Configure Google Sheets Node:
    • Select your Google Sheets credential or create a new one.
    • Specify the "Spreadsheet ID" and "Sheet Name" from which to read lead data.
    • Ensure the "Operation" is set to "Read All".
  3. Configure Function Node (if necessary):
    • Review the JavaScript code within the Function node. This is where custom lead ranking logic or data transformation should be implemented. Adjust it to fit your specific lead qualification criteria.
  4. Configure Limit Node (optional):
    • If you only want to process a certain number of leads at a time, configure the "Limit" value. Otherwise, you can set it to a high number or remove it.
  5. Configure Sort Node (optional):
    • If you want to sort your leads before creating tasks (e.g., by priority), configure the "Field" and "Order" in the Sort node.
  6. Configure ClickUp Node:
    • Select your ClickUp credential or create a new one.
    • Set the "Resource" to "Task" and "Operation" to "Create".
    • Map the data from the previous nodes to the ClickUp task fields (e.g., Task Name, Description, Priority, Due Date, Assignee). This will typically involve using expressions like {{ $json.leadName }}.
  7. Activate the Workflow: Once configured, activate the workflow.
  8. Execute Manually: Click "Execute workflow" on the "When clicking โ€˜Execute workflowโ€™" trigger node to run the workflow.

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