Search Skool community posts with Claude and Google Docs analysis

Open on n8n.io

$20/month : Unlimited workflows

2500 executions/month

Try free

THE #1 IN WEB SCRAPING

Scrape any website without limits

Try free

HOSTINGER

Early Deal
DISCOUNT 20%

Self-hosted n8n

Unlimited workflows - from $4.99/mo

Try free

#1 hub for scraping, AI & automation

6000+ actors - $5 credits/mo

Try free

Important notice

This workflow is provided as-is. Please review and test before using in production.

1. Workflow Overview

How it works 1. Form Trigger accepts a question and optional settings (folder ID, search depth) 2. Cookie Validation checks if Skool session is still active 3. BuildId Extraction dynamically extrac...

Best for

Market Research automation workflows
AI RAG automation workflows
advanced n8n builders looking for reusable templates

Tools used

n8n-nodes-base.stickynote, n8n-nodes-base.formtrigger, n8n-nodes-base.code, n8n-nodes-base.httprequest, n8n-nodes-base.if, n8n-nodes-base.respondtowebhook, n8n-nodes-base.googledocs

Source and attribution

This workflow is cataloged by N8N Workflows and links back to its original n8n.io source page by Nitin Garg.

Original n8n.io source

1.1 Workflow description

Title: Search Skool community posts with Claude and Google Docs analysis
Workflow name: Search Skool community posts with Claude and Google Docs analysis

How it works

Form Trigger accepts a question and optional settings (folder ID, search depth)
Cookie Validation checks if Skool session is still active
BuildId Extraction dynamically extracts Skool's build ID from homepage
Keyword Extraction uses Claude Haiku to extract 1-2 search keywords
Multi-Page Search fetches 1-10 pages of Skool search results
Post Aggregation collects all posts with content and comments
AI Analysis uses Claude Sonnet to analyze posts and answer your question
Google Doc Report creates a detailed research document in your Drive
HTML Response returns a beautiful summary page

Key Features

Auto BuildId Detection - No manual updates when Skool changes
Cookie Expiration Handling - Clear error messages when session expires
Configurable Search Depth - Search 1-10 pages (default: 5)
Token Protection - Limits content to control API costs
Dual AI Models - Haiku for keywords (cheap), Sonnet for analysis (powerful)

Set up steps

Time required: 10-15 minutes

Get your Skool session cookie from browser DevTools
Get an Anthropic API key from console.anthropic.com
Set up Google Docs OAuth2 credential in n8n
Create a Google Drive folder for research docs
Update the Config node with your values:
- COOKIE - Your Skool session cookie
- ANTHROPIC_API_KEY - Your Claude API key
- DEFAULT_FOLDER_ID - Your Google Drive folder ID
- COMMUNITY - Your Skool community slug

Who is this for?

Members of Skool communities searching past discussions
Community managers researching common questions
Anyone building knowledge bases from Skool content

Estimated costs

Per search: $0.02-0.10 (Claude Haiku + Sonnet)
Skool cookies expire every 7-14 days (requires refresh)


---

## 🏷️ Suggested Tags

skool, community, search, ai, claude, anthropic, google-docs, research, knowledge-base, form

1.2 Logical Blocks

This catalog entry is organized from the workflow JSON. The node-level section below shows the executable blocks available for review before importing the template.

2. Block-by-Block Analysis

Block 1 - Sticky Note - Overview

Type / Role: n8n-nodes-base.stickyNote - stickyNote
Config choices: Version 1

Block 2 - Sticky Note - Input

Type / Role: n8n-nodes-base.stickyNote - stickyNote
Config choices: Version 1

Block 3 - Sticky Note - Errors

Type / Role: n8n-nodes-base.stickyNote - stickyNote
Config choices: Version 1

Block 4 - Sticky Note - Keywords

Type / Role: n8n-nodes-base.stickyNote - stickyNote
Config choices: Version 1

Block 5 - Sticky Note - Search

Type / Role: n8n-nodes-base.stickyNote - stickyNote
Config choices: Version 1

Block 6 - Sticky Note - No Results

Type / Role: n8n-nodes-base.stickyNote - stickyNote
Config choices: Version 1

Block 7 - Sticky Note - Analysis

Type / Role: n8n-nodes-base.stickyNote - stickyNote
Config choices: Version 1

Block 8 - Sticky Note - Output

Type / Role: n8n-nodes-base.stickyNote - stickyNote
Config choices: Version 1

Block 9 - Form Trigger

Type / Role: n8n-nodes-base.formTrigger - formTrigger
Config choices: Version 2.1

Block 10 - Config

Type / Role: n8n-nodes-base.code - code
Config choices: Version 2

Block 11 - Fetch Skool Homepage

Type / Role: n8n-nodes-base.httpRequest - httpRequest
Config choices: Version 4.1

Block 12 - Extract BuildId

Type / Role: n8n-nodes-base.code - code
Config choices: Version 2

Block 13 - Cookie Valid?

Type / Role: n8n-nodes-base.if - if
Config choices: Version 2

Block 14 - Cookie Error Response

Type / Role: n8n-nodes-base.code - code
Config choices: Version 2

Block 15 - Respond with Error

Type / Role: n8n-nodes-base.respondToWebhook - respondToWebhook
Config choices: Version 1.1

Block 16 - Build Keyword Request

Type / Role: n8n-nodes-base.code - code
Config choices: Version 2

Block 17 - Claude - Extract Keywords

Type / Role: n8n-nodes-base.httpRequest - httpRequest
Config choices: Version 4.1

Block 18 - Build Page URLs

Type / Role: n8n-nodes-base.code - code
Config choices: Version 2

Block 19 - Fetch All Pages

Type / Role: n8n-nodes-base.httpRequest - httpRequest
Config choices: Version 4.1

Block 20 - Aggregate All Posts

Type / Role: n8n-nodes-base.code - code
Config choices: Version 2

Block 21 - Has Results?

Type / Role: n8n-nodes-base.if - if
Config choices: Version 2

Block 22 - No Results Response

Type / Role: n8n-nodes-base.code - code
Config choices: Version 2

Block 23 - Respond No Results

Type / Role: n8n-nodes-base.respondToWebhook - respondToWebhook
Config choices: Version 1.1

Block 24 - Build Analysis Request

Type / Role: n8n-nodes-base.code - code
Config choices: Version 2

Showing the first 24 of 31 workflow blocks. Download the JSON for the full node graph.

3. Summary Table

Workflow	Search Skool community posts with Claude and Google Docs analysis
Complexity	advanced
Nodes	31
Categories	Market Research, AI RAG
Author	Nitin Garg
Published	26 Dec 2025

4. Reproducing the Workflow from Scratch

1. Download the workflow JSON

Use the JSON export at /data/workflows/12180/12180.json as the source template for this automation.
2. Import the template into n8n

Open n8n, import the downloaded JSON, and review each node before activating the workflow.
3. Configure credentials and variables

Replace placeholder credentials, API keys, webhook URLs, account IDs, and environment-specific values with your own settings.
4. Test with sample data

Run the workflow manually or in a staging workspace, inspect node output, and confirm downstream systems receive the expected data.
5. Activate and monitor

Enable the workflow only after testing, then monitor executions, errors, and rate limits during the first production runs.

5. General Notes & Resources

Review imported nodes carefully before activation. This catalog entry is intended to help you inspect the workflow structure, understand required services, and find related templates faster.

Node names, credentials, schedules, webhook paths, and external service limits may need adjustment for your workspace.

Download workflow JSON Original n8n.io source Market Research workflows AI RAG workflows

Frequently asked questions

What does Search Skool community posts with Claude and Google Docs analysis do?

What do I need before importing this workflow?

Review the workflow JSON, configure any required credentials in n8n, and test the automation in a safe workspace before using it in production.

Can I customize this workflow?

Yes. Use the block-by-block analysis and the downloadable JSON to inspect each node, then adjust credentials, prompts, schedules, filters, or destinations for your Market Research, AI RAG use case.

Nitin Garg

4 workflows

Nodes

n8n-nodes-base.stickynote n8n-nodes-base.formtrigger n8n-nodes-base.code n8n-nodes-base.httprequest n8n-nodes-base.if n8n-nodes-base.respondtowebhook n8n-nodes-base.googledocs

Complexity

advanced

Published 26 Dec 2025

Likes 0

View on n8n.io Download Workflow

Install path: /data/workflows/12180/12180.json

Share Your Workflow

Have a useful automation to share? Publish it and help the community.

Submit Your Template How to Submit

Related Workflows

Answer BigQuery questions in Microsoft Teams with Claude 3.5 dual agents

## Quick overview Turn Microsoft Teams into a natural language BI tool. This dual-agent Claude workflow intelligently classifies user questions, generates safe BigQuery SQL, executes the query, and returns a plain-English summary alongside a data preview directly to your Teams channel. ## How it works 1. The workflow listens for new messages in a designated Microsoft Teams channel or chat. 2. It checks a 24-hour static data cache for your BigQuery schema. If the cache is missing or expired, it automatically fetches the latest INFORMATION_SCHEMA metadata. 3. A main Claude 3.5 Sonnet agent classifies the user's intent (analytical, conversational, or unsafe) and identifies the relevant database tables. 4. If the intent is analytical, a specialized Claude SQL sub-agent generates a read-only SELECT query tailored exactly to your schema. 5. The workflow executes the query against BigQuery (safely constrained to a maximum of 100 rows). 6. A final Claude agent translates the raw query results into a concise, plain-English summary. 7. The answer is posted back to Teams as an Adaptive Card, complete with a formatted data preview and the generated SQL code. 8. Non-analytical questions or pipeline errors are intelligently routed to receive standard conversational replies in Teams. ## Setup 1. CRITICAL SECURITY: Restrict your Google Cloud Service Account IAM roles to BigQuery Data Viewer and BigQuery Job User ONLY. Do not use a highly privileged account. 2. Configure your Microsoft Teams trigger and posting credentials, specifying the target team and channel for the bot to operate in. 3. Configure your Google BigQuery credentials to allow reading metadata and executing queries. 4. Configure your Anthropic credentials for the three Claude LangChain nodes. 5. Update the "Configure Variables" node with your specific GCP Project ID and BigQuery Dataset ID. ## Requirements - A Google Cloud project with BigQuery enabled and existing structured datasets. - An Anthropic API key with access to the Claude 3.5 Sonnet model. - Microsoft Teams administrator access to authorize the n8n integration. ## Customization - Distributed Environments: If you are running n8n with multiple worker nodes (Queue Mode), you must swap the $getWorkflowStaticData() schema cache logic to read/write from a dedicated Key-Value store (like Redis or Supabase) to ensure state synchronization. - UI Layout: Modify the Create Teams Adaptive Card node to add corporate branding, custom colors, or alter the FactSet data preview structure. ## Additional info This architecture features built-in pipeline protections, including strict 40,000-character payload limits to prevent LLM context window blowouts, and fallback handling for "zero-row" query results to ensure users are never left without a response.

View

Evaluate LinkedIn profiles with Apify and Groq Llama chat model

## Quick overview This workflow collects a LinkedIn profile URL via an n8n form, scrapes the public profile data using the Apify LinkedIn Profile Scraper actor, analyzes the results with a Groq-hosted Llama model, and displays an HTML-formatted evaluation back to the user. ## How it works 1. Receives a LinkedIn Profile URL when a user submits the n8n form. 2. Prepares the LinkedIn URL along with the Apify API token and Groq API key used for downstream requests. 3. Sends the profile URL to the Apify `harvestapi/linkedin-profile-scraper` actor and retrieves the scraped dataset items. 4. Passes the scraped profile JSON to a Groq chat model via an LLM chain to generate an HTML evaluation with a score and recommendations. 5. Displays the generated HTML evaluation to the user as the form completion message. ## Setup 1. Add a valid Apify API token and ensure the Apify actor endpoint (`harvestapi/linkedin-profile-scraper`) is accessible for your account. 2. Add Groq API credentials in n8n and confirm the selected model (meta-llama/llama-4-scout-17b-16e-instruct) is available to your Groq account. 3. Replace the placeholder API key values in the workflow (or move them to n8n credentials/environment variables) and verify the form field label matches `LinkedIn Profile URL`.

View

Validate startup ideas with Google Gemini, Groq, and Gmail

## Quick overview This workflow collects a startup idea via an n8n form, uses Google Gemini to generate a SWOT-style analysis, assigns a viability score, uses Groq to turn the results into a structured validation report, and emails the final report through Gmail. ## How it works 1. Receives a startup idea, industry, and target audience from an n8n Form trigger. 2. Sends the submission to Google Gemini to generate a professional analysis covering the problem, business model, and SWOT factors. 3. Generates a startup viability score (currently a random value from 80–100) and packages it with the Gemini analysis. 4. Sends the score and analysis to Groq (Llama 3.3 70B) to compile a full validation report with an executive summary, market potential, recommendations, and final verdict. 5. Emails the generated validation report to the configured recipient using Gmail. ## Setup 1. Add credentials for Google Gemini (PaLM) API, Groq API, and a Gmail OAuth2 connection. 2. Replace the placeholder recipient address in the Gmail step ("[email protected]") with your target email address before activating the workflow. 3. Publish the n8n form, then share the form URL with the users who should submit their startup ideas for validation.

View

Need Custom Automation?

Get help designing a custom n8n workflow that connects your stack and fits your process.

Search Skool community posts with Claude and Google Docs analysis

Workflow preview

Important notice

1. Workflow Overview

Best for

Tools used

Source and attribution

1.1 Workflow description

How it works

Key Features

Set up steps

Who is this for?

Estimated costs

1.2 Logical Blocks

2. Block-by-Block Analysis

Block 1 - Sticky Note - Overview

Block 2 - Sticky Note - Input

Block 3 - Sticky Note - Errors

Block 4 - Sticky Note - Keywords

Block 5 - Sticky Note - Search

Block 6 - Sticky Note - No Results

Block 7 - Sticky Note - Analysis

Block 8 - Sticky Note - Output

Block 9 - Form Trigger

Block 10 - Config

Block 11 - Fetch Skool Homepage

Block 12 - Extract BuildId

Block 13 - Cookie Valid?

Block 14 - Cookie Error Response

Block 15 - Respond with Error

Block 16 - Build Keyword Request

Block 17 - Claude - Extract Keywords

Block 18 - Build Page URLs

Block 19 - Fetch All Pages

Block 20 - Aggregate All Posts

Block 21 - Has Results?

Block 22 - No Results Response

Block 23 - Respond No Results

Block 24 - Build Analysis Request

3. Summary Table

4. Reproducing the Workflow from Scratch

1. Download the workflow JSON

2. Import the template into n8n

3. Configure credentials and variables

4. Test with sample data

5. Activate and monitor

5. General Notes & Resources

Frequently asked questions