Back to Catalog

Automated Competitor Intelligence: CrunchBase to ClickUp Tracking Workflow

Yaron BeenYaron Been
647 views
2/3/2026
Official Page

πŸš€ Automated Competitor Intelligence: CrunchBase to ClickUp Tracking Workflow!

Workflow Overview

This cutting-edge n8n automation is a sophisticated competitive intelligence tool designed to transform market research into actionable insights. By intelligently connecting CrunchBase, ClickUp, and intelligent data processing, this workflow:

  1. Discovers Competitor Insights:

    • Automatically retrieves company data
    • Tracks real-time business updates
    • Eliminates manual research efforts
  2. Intelligent Data Processing:

    • Converts company names to API-compatible formats
    • Fetches comprehensive company information
    • Ensures precise data retrieval
  3. Automated Task Management:

    • Creates instant review tasks in ClickUp
    • Distributes competitive intelligence
    • Enables rapid team response
  4. Seamless Workflow Integration:

    • Cross-platform data synchronization
    • Reduces manual intervention
    • Provides structured competitive insights

Key Benefits

  • πŸ€– Full Automation: Zero-touch competitive tracking
  • πŸ’‘ Smart Data Processing: Intelligent insight generation
  • πŸ“Š Comprehensive Intelligence: Detailed company information
  • 🌐 Multi-Platform Synchronization: Seamless data flow

Workflow Architecture

πŸ”Ή Stage 1: Competitor Identification

  • Manual Trigger: Workflow initiation
  • Competitor Name Setting
  • Slug Generation:
    • Converts names to API-compatible formats
    • Ensures precise data matching

πŸ”Ή Stage 2: Data Retrieval

  • CrunchBase API Integration
  • Comprehensive Company Lookup
  • Real-Time Information Gathering

πŸ”Ή Stage 3: Insight Distribution

  • ClickUp Task Creation
  • Structured Information Sharing
  • Team Notification Mechanism

Potential Use Cases

  • Strategic Planning: Competitive landscape monitoring
  • Sales Teams: Market intelligence gathering
  • Product Managers: Tracking industry innovations
  • Investors: Investment opportunity research
  • Marketing Departments: Competitive analysis

Setup Requirements

  1. CrunchBase API

    • API credentials
    • Configured access permissions
    • Company tracking setup
  2. ClickUp Workspace

    • Connected ClickUp account
    • Task management configuration
    • Team collaboration settings
  3. n8n Installation

    • Cloud or self-hosted instance
    • Workflow configuration
    • API credential management

Future Enhancement Suggestions

  • πŸ€– Multi-competitor tracking
  • πŸ“Š Advanced trend analysis
  • πŸ”” Customizable alert mechanisms
  • 🌐 Expanded data source integration
  • 🧠 Machine learning insights generation

Technical Considerations

  • Implement robust error handling
  • Use secure API authentication
  • Maintain flexible data processing
  • Ensure compliance with API usage guidelines

Ethical Guidelines

  • Respect business privacy
  • Use data for legitimate research
  • Maintain transparent information gathering
  • Provide proper attribution

Hashtag Performance Boost πŸš€

#CompetitiveIntelligence #MarketResearch #BusinessTracking #AIWorkflow #DataAutomation #TechInnovation #StrategicPlanning #BusinessIntelligence #MarketInsights #APIAutomation

Workflow Visualization

[Manual Trigger]
    ⬇️
[Set Competitor Name]
    ⬇️
[Generate Crunchbase Slug]
    ⬇️
[Fetch Crunchbase Data]
    ⬇️
[Create ClickUp Task]

Connect With Me

Ready to revolutionize your competitive intelligence?

πŸ“§ Email: Yaron@nofluff.online

πŸŽ₯ YouTube: @YaronBeen

πŸ’Ό LinkedIn: Yaron Been

Transform your competitive research with intelligent, automated workflows!

Automated Competitor Intelligence: Crunchbase to ClickUp Tracking Workflow

This n8n workflow streamlines the process of tracking competitor intelligence by integrating data from an external API (likely Crunchbase, based on the context) and organizing it within ClickUp. It allows for manual triggering to fetch data, process it, and create or update tasks in ClickUp, ensuring your team has up-to-date information on competitors.

What it does

This workflow performs the following key steps:

  1. Manual Trigger: The workflow is initiated manually, allowing you to control when the competitor intelligence update process runs.
  2. HTTP Request: It makes an HTTP request to an external API to fetch raw competitor data.
  3. Code Execution: The retrieved data is then processed using a Code node, likely to extract specific fields, transform data formats, or apply custom logic before further processing.
  4. Edit Fields (Set): This node is used to manipulate and set specific fields in the data, ensuring it's in the correct structure and format for ClickUp. This could involve renaming fields, combining values, or adding new static data.
  5. ClickUp Task Creation/Update: Finally, the processed data is sent to ClickUp to create new tasks or update existing ones, providing a centralized tracking system for competitor activities.

Prerequisites/Requirements

To use this workflow, you will need:

  • n8n Instance: A running instance of n8n.
  • API Endpoint: Access to an external API (e.g., Crunchbase API) that provides competitor data. You will need the API URL and any necessary authentication details (API keys, tokens).
  • ClickUp Account: A ClickUp account with appropriate permissions to create and manage tasks.
  • ClickUp API Token: A ClickUp API token for authentication within n8n.

Setup/Usage

  1. Import the Workflow:

    • Copy the provided JSON code.
    • In your n8n instance, go to "Workflows" and click "New".
    • Click on the "Import from JSON" button (usually a cloud icon with an arrow pointing down) and paste the JSON code.
    • Click "Import".
  2. Configure Credentials:

    • Locate the "HTTP Request" node (ID: 19) and configure its authentication method and API key/token to connect to your external data source (e.g., Crunchbase).
    • Locate the "ClickUp" node (ID: 129) and set up your ClickUp API credentials. You will need to provide your ClickUp API token.
  3. Customize Nodes:

    • HTTP Request (ID: 19): Adjust the URL, headers, and any request body parameters to match the specific API endpoint you are querying for competitor data.
    • Code (ID: 834): Modify the JavaScript code within this node to parse and transform the data returned by your API into a format suitable for ClickUp. This might involve extracting specific fields like company name, funding rounds, recent news, etc.
    • Edit Fields (Set) (ID: 38): Configure this node to map the transformed data fields to the desired ClickUp task fields (e.g., task name, description, custom fields).
    • ClickUp (ID: 129): Configure the ClickUp node to specify the Workspace, Space, Folder, and List where you want to create or update tasks. Map the incoming data fields to ClickUp task properties like "Task Name", "Description", "Due Date", "Assignees", "Tags", and any custom fields you use for competitor tracking.
  4. Execute the Workflow:

    • Once configured, you can test the workflow by clicking the "Execute Workflow" button on the "Manual Trigger" node (ID: 838).
    • For production use, you can activate the workflow. Since it's a manual trigger, you will need to manually execute it whenever you want to update your competitor intelligence.

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