Auto-Generate Competitive Battlecards with AI, Slack & Notion (Klue Alternative)

70 views

2/3/2026

OpenAI Automation Attachments Email Summarization

Enterprise Competitive Intelligence System (Klue+Crayon Alternative)

One-Line Description

Build your own Klue/Crayon alternative: Auto-generate comprehensive competitive battlecards with AI research agents for ~$50/month instead of $1,500+

Detailed Description

What it does:

This workflow replicates enterprise competitive intelligence platforms (Klue, Crayon, Kompyte) at 5% of the cost. When sales teams mention a competitor in Slack, AI agents automatically research the company, scrape websites, analyze customer reviews, generate SWOT analysis, and compile everything into structured 9-section battlecards stored in Notion. The system then powers real-time Q&A, letting teams ask "What's their biggest weakness?" and get instant, citation-backed answers—just like Klue's "Ask Klue" feature.

Why build vs. buy?

| Platform | Annual Cost | Licensing | |----------|-------------|-----------| | Klue | $16,000+ | Per-user fees | | Crayon | $30,000+ | Enterprise-only | | Playwise HQ | $3,000+ | Pro plan | | This workflow | $500-800 | Unlimited users |

Who it's for:

Startups & scale-ups ($1-10M ARR) that can't justify $15K+ for Klue
Sales enablement teams building competitive intelligence without enterprise budgets
Product marketing managers maintaining battlecard databases that stay updated
Founder-led sales teams needing instant competitive insights without dedicated CI headcount
Companies already using n8n looking to add competitive intelligence to their stack

Key Features (vs. Enterprise Alternatives)

| Feature | This Workflow | Klue | Crayon | |---------|---------------|------|--------| | AI Battlecard Generation | ✅ 9 sections | ✅ 4-6 sections | ✅ 5-7 sections | | Slack Q&A Agent | ✅ Real-time | ✅ "Compete Agent" | ❌ Manual | | Customer Review Analysis | ✅ G2, Capterra | ✅ Multi-source | ✅ Multi-source | | SWOT Analysis | ✅ Auto-generated | ✅ Manual/AI hybrid | ✅ Manual | | Data Ownership | ✅ 100% yours | ❌ Vendor-hosted | ❌ Vendor-hosted | | Per-User Fees | ✅ None | ❌ ~$1K/user/year | ❌ Custom | | Setup Time | 45-60 min | Weeks | Weeks | | Annual Cost | ~$500-800 | $16,000+ | $30,000+ |

Core Capabilities:

✅ Automatic research pipeline - Scrapes competitor websites, reviews (G2, Capterra), LinkedIn, and product pages
✅ AI-powered analysis - Generates SWOT analysis, positioning insights, feature comparisons, and competitive attack surfaces using Claude Sonnet
✅ Intelligent Q&A agent - Sales reps ask questions in Slack and get contextual answers with proper citations (replicates Klue's "Ask Klue")
✅ Structured battlecard format - Creates 9-section competitive profiles including messaging analysis, discovery questions, and supporting quotes
✅ Multi-source intelligence - Combines website content, customer reviews, market research, and sentiment analysis
✅ Database synchronization - Maintains competitor registry in n8n Data Tables with auto-updated Notion pages

How it works:

Phase 1: Competitor Detection & Routing

Sales rep mentions competitor in Slack (e.g., @bot create battlecard for Salesforce or @bot what's HubSpot's biggest weakness?)
AI detection agent parses message, extracts competitor name, and queries n8n Data Table using fuzzy matching
Workflow routes to battlecard creation (new competitor) or Q&A agent (existing competitor)

Phase 2: Research & Data Collection

For new competitors, five parallel research streams activate:

Company identification via Perplexity (official name, website, LinkedIn)
Website scraping via Jina AI (4+ key pages: homepage, features, pricing, about)
Customer review analysis via Perplexity (G2, Capterra, Reddit for complaints and pain points)
Feature research via Perplexity (core features, integrations, pricing model)
Market positioning via Perplexity (competitive positioning, target market, differentiators)

Phase 3: AI Battlecard Generation

Five parallel Claude Sonnet 4.5 agents generate distinct sections:

Company Overview + Basic Information
Positioning & Messaging Analysis
Feature Comparison + Product Analysis
SWOT Analysis (strengths, weaknesses, opportunities, threats)
Competitive Attack Surfaces + Discovery Questions

Supporting quotes agent extracts tactical customer quotes from reviews. Content merger combines all sections into unified markdown document.

Phase 4: Storage & Access

Complete battlecard saves to Notion database and competitor registry. Slack confirmation sent with link to new battlecard.

Phase 5: Real-Time Q&A

For existing competitors, Q&A agent:

Retrieves battlecard from Notion
Uses Claude to answer questions with battlecard data
Optionally supplements with Perplexity for breaking news
Posts formatted answer in Slack with section citations

What makes this different:

vs. DIY Google Docs:

✅ Automated research (no manual copying/pasting)
✅ Consistent structure across all battlecards
✅ Real-time Q&A without searching folders

vs. Enterprise Tools:

💰 95%+ cheaper than Klue/Crayon ($500 vs. $16K-30K)
🔧 Full customization of research sources and battlecard structure
📁 Complete data ownership (your Notion/n8n, not vendor platform)
👥 No per-user fees (unlimited team access)

Setup Requirements

Prerequisites:

Slack workspace with bot permissions (app mentions, message posting)
Notion workspace with database for battlecard storage
n8n instance (Cloud or self-hosted) with Data Table module
Anthropic API key (Claude Sonnet 4.5 for generation, 3.5 for detection)
Perplexity API key (Sonar Pro for research)
Jina AI API key (web scraping)

Estimated Setup Time:

⏱️ 45-60 minutes including API configuration, Slack bot setup, and Notion database template creation

Installation Notes

1. Slack Configuration:

Create Slack app with scopes: app_mentions:read, chat:write, channels:history
Subscribe to app_mention event pointing to n8n webhook

2. Notion Setup:

Use provided template (30 rich text properties for battlecard sections)
Create integration and share database with it
Copy database ID from URL

3. n8n Configuration:

Create Data Table "Competitors" with columns: Competitor_Name (text), Notion_URL (text)
Import workflow JSON and update credentials
Store your company's Notion profile page ID in "Get Our Page" tool node

4. Testing:

Test battlecard creation with small company
Verify fuzzy matching with typos (salesforce.com → Salesforce)
Test Q&A agent on existing battlecard

⚠️ Common Issues:

Perplexity rate limits: Space calls 30+ seconds apart
Slack formatting: Use single asterisks *bold* not double
Notion properties: Requires 30-property minimum (do not reduce)

Customization Options

Research Sources

Swap Perplexity for OpenAI/Tavily, add YouTube/GitHub scrapers, integrate Crunchbase API

Storage Backend

Replace Notion with Airtable, Google Docs, Confluence, or PostgreSQL

Battlecard Structure

Add/remove sections (pricing analysis, customer case studies, security comparison), reorder based on priorities

Q&A Enhancements

Add threaded replies, create slash commands, schedule weekly competitor news digests

Advanced Features

Quarterly auto-refresh, CRM integration (show battlecards in Salesforce deals), Gong integration (auto-generate from sales calls)

Who This Workflow Replaces

Direct Alternatives:

✅ Klue - Competitive enablement platform ($16K+/year)
✅ Crayon - Competitive intelligence platform ($30K+/year)
✅ Kompyte - Competitive tracking tool ($300-5K/year)
✅ Playwise HQ - AI battlecard generator ($3K-5K/year)
✅ Contify - Market intelligence platform (Enterprise pricing)

Use Case Examples

🎯 B2B SaaS Sales Team

Generate battlecards when new competitors emerge in deals. Sales leader mentions @bot create battlecard for Airtable—60 seconds later, entire team has comprehensive competitive profile with attack angles and discovery questions.

📊 Product Marketing at Startup

Maintain living competitor database that eliminates manual quarterly research (saving 20+ hours/quarter). PM uses Q&A mid-presentation: @bot what's Linear's current pricing? gets instant answer.

🚀 RevOps & Enablement Team

Provide instant Slack Q&A for reps mid-call (@bot what questions expose Salesforce's pricing gaps?). New hires onboard faster with centralized, AI-maintained knowledge base versus outdated PDFs.

💼 Founder-Led Sales

Solo founder can't afford $16K for Klue but needs professional competitive intelligence. Build battlecard library organically over months for ~$50/month in API fees.

🏢 Enterprise Replacing Klue/Crayon

Company with 100+ reps spent $35K/year on Crayon but only used battlecards. Migrated to this workflow, saved $33K annually, maintained same adoption with identical Slack integration.

💡 Pro Tip

Start with 5-10 most common competitors to build core library, then add others as they appear in deals. This workflow pays for itself after creating just 3-4 battlecards versus hiring freelance researchers or buying enterprise tools.

AI-Powered Competitive Battlecard Generator (Slack & Notion)

This n8n workflow automates the creation of competitive battlecards using AI, triggered by messages in Slack. It's designed to provide quick, AI-generated insights into competitors, storing them in Notion for easy access. This workflow acts as a powerful alternative to tools like Klue, enabling your team to stay informed and agile.

What it does

This workflow streamlines the process of generating and managing competitive intelligence:

Listens for Slack Messages: It triggers when a specific message pattern or mention is detected in a designated Slack channel.
Extracts Competitor Information: The message content is processed to identify the competitor in question.
Researches Competitor Data (AI-Powered): An AI Agent, leveraging an Anthropic Chat Model and various tools (Jina AI, Perplexity, Think Tool), performs research to gather competitive intelligence.
Generates Battlecard Content: The AI synthesizes the gathered information into a structured battlecard format.
Creates Notion Page: The generated battlecard content is then used to create a new page in a specified Notion database.
Notifies Slack Channel: A summary or link to the newly created Notion battlecard is posted back to the original Slack channel, informing the team.

Prerequisites/Requirements

To use this workflow, you will need:

n8n Instance: A running instance of n8n.
Slack Account: With an app configured to allow the n8n Slack Trigger and Slack node to post messages.
Notion Account: With a database set up to store the competitive battlecards.
Anthropic API Key: For the Anthropic Chat Model.
Jina AI API Key: For web research capabilities.
Perplexity API Key: For enhanced search and information retrieval.

Setup/Usage

Import the Workflow: Download the provided JSON and import it into your n8n instance.
Configure Credentials:
- Set up your Slack API credentials for both the Slack Trigger and the Slack node.
- Configure your Notion API credentials.
- Add your Anthropic API Key to the Anthropic Chat Model node.
- Add your Jina AI API Key to the Jina AI node.
- Add your Perplexity API Key to the Perplexity node.
Customize Slack Trigger:
- Specify the Slack channel(s) or keywords that should trigger the workflow.
Configure Notion Node:
- Select the Notion database where battlecards should be created.
- Map the AI-generated battlecard content to the appropriate properties in your Notion database.
Activate the Workflow: Once all credentials and configurations are set, activate the workflow.

Now, whenever a relevant message is posted in Slack, the AI will automatically generate and store a competitive battlecard in Notion, keeping your team informed and competitive.

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.

By 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

By 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.

By Le Nguyen

942