HumationHuman + Automation
Back to Catalog

Reliable Reddit subreddit search with OAuth2 API authentication

Christian MoisesChristian Moises
292 views
2/3/2026
Inventory SyncAirtableShopifyE-commerceData Sync
Official Page

Since the Get Many Subreddit node often blocks requests because Reddit requires proper authentication headers, this workflow provides a reliable alternative. It uses the Reddit OAuth2 API through the HTTP Request node, processes the results, and outputs cleaned subreddit data.

If you are using Get Many subreddit node and you are getting this error: n8n You've been blocked by network security.To continue, log in to your Reddit account or use your developer token

Usecase: This is especially useful if you want to search multiple subreddits programmatically and apply filtering for members, descriptions, and categories.

How It Works

  1. Trigger Input

    • The workflow is designed to be called by another workflow using the Execute Workflow Trigger node.

    • Input is passed in JSON format with parameters:

      {
  "Query": "RealEstateTechnology",
  "min_members": 0,
  "max_members": 20000,
  "limit": 50
}

  2. Fetch Subreddits

    • The HTTP Request (Reddit OAuth2) node queries the Reddit API (/subreddits/search) with the given keyword and limit.
    • Because it uses OAuth2 credentials, the request is properly authenticated and accepted by Reddit.

  3. Process Results

    • Split Out: Iterates over each subreddit entry (data.children).

    • Edit Fields: Extracts the following fields for clarity:

      • Subreddit URL
      • Description
      • 18+ flag
      • Member count

    • Aggregate: Recombines the processed data into a structured output array.

  4. Output

    • Returns a cleaned dataset with only the relevant subreddit details.(Saves token if Attached to an AI Agent)

How to Use

  1. Import this workflow into n8n.
  2. In your main workflow, replace the Get Many Subreddit node with an Execute Workflow node and select this workflow.
  3. Pass in the required query parameters (Query, min_members, max_members, limit).
  4. Run your main workflow — results will now come through authenticated API requests without being blocked.

Requirements

  • Reddit OAuth2 API Credentials (must be set up in n8n under Credentials).
  • Basic understanding of JSON parameters in n8n.
  • An existing workflow that calls this one using Execute Workflow.

Customizing This Workflow

You can adapt this workflow to your specific needs by:

  • Filtering by member range: Add logic to exclude subreddits outside min_members or max_members.
  • Expanding extracted fields: Include additional subreddit properties such as created_utc, lang, or active_user_count.
  • Changing authentication: Switch to different Reddit OAuth2 credentials if managing multiple Reddit accounts.
  • Integrating downstream apps: Send the processed subreddit list to Google Sheets, Airtable, or a database for storage.

n8n Workflow: Reliable Reddit Subreddit Search with OAuth2 API Authentication

This n8n workflow demonstrates how to make authenticated API requests to a service, specifically designed to be triggered by another workflow. It showcases a common pattern for handling API interactions, including potential data transformation.

What it does

This workflow performs the following key steps:

  1. Triggered by Another Workflow: It starts when explicitly called by another n8n workflow, making it a reusable sub-workflow for API interactions.
  2. Makes an HTTP Request: It executes an HTTP request, likely to an external API (e.g., Reddit, given the directory name context, although the JSON doesn't explicitly define the URL or method). This request is intended to be authenticated using OAuth2, as suggested by the directory name.
  3. Transforms Data (Edit Fields): It uses the "Edit Fields (Set)" node to manipulate or add data to the incoming items. This could be used to prepare data for the HTTP request or to process the response.
  4. Aggregates Data: The "Aggregate" node combines multiple input items into a single item or a structured list, useful for consolidating data before further processing.
  5. Splits Out Data: The "Split Out" node reverses the aggregation, taking a single item (or a list within an item) and splitting it into multiple individual items. This is useful for processing each record separately after an aggregated response.

Prerequisites/Requirements

  • n8n Instance: An active n8n instance to import and run the workflow.
  • API Credentials: While not explicitly defined in the JSON, the workflow is designed for API interaction. If used with Reddit or another service requiring OAuth2, you will need to configure the appropriate OAuth2 credentials within the "HTTP Request" node.

Setup/Usage

  1. Import the Workflow:
    • Copy the provided JSON code.
    • In your n8n instance, click "Workflows" in the left sidebar.
    • Click "New Workflow" or "Add Workflow".
    • Click the three dots menu (...) on the top right and select "Import from JSON".
    • Paste the JSON code and click "Import".
  2. Configure the HTTP Request Node:
    • Open the "HTTP Request" node (Node ID: 19).
    • Configure the URL, Method, and any necessary Headers or Body parameters for your target API.
    • Crucially, if using OAuth2 (as implied by the directory name), select "OAuth2" for the "Authentication" method and configure your credentials.
  3. Configure Edit Fields (Set) Node:
    • Open the "Edit Fields (Set)" node (Node ID: 38).
    • Adjust the fields to be set or modified based on your specific data transformation needs.
  4. Configure Aggregate and Split Out Nodes:
    • Review the "Aggregate" (Node ID: 1236) and "Split Out" (Node ID: 1239) nodes. Their default configurations are usually sufficient for basic aggregation/splitting, but you might need to adjust "Mode" or "Property Name" depending on the structure of your data.
  5. Connect to a Parent Workflow:
    • This workflow is designed to be triggered by another workflow. In your parent workflow, use an "Execute Workflow" node and point it to this workflow. You can pass data into this workflow via the "Execute Workflow" node's input.
  6. Activate the Workflow: Once configured, activate the workflow by toggling the "Active" switch in the top right corner of the workflow editor.

Related Templates

Auto-create TikTok videos with VEED.io AI avatars, ElevenLabs & GPT-4

💥 Viral TikTok Video Machine: Auto-Create Videos with Your AI Avatar --- 🎯 Who is this for? This workflow is for content creators, marketers, and agencies who want to use Veed.io’s AI avatar technology to produce short, engaging TikTok videos automatically. It’s ideal for creators who want to appear on camera without recording themselves, and for teams managing multiple brands who need to generate videos at scale. --- ⚙️ What problem this workflow solves Manually creating videos for TikTok can take hours — finding trends, writing scripts, recording, and editing. By combining Veed.io, ElevenLabs, and GPT-4, this workflow transforms a simple Telegram input into a ready-to-post TikTok video featuring your AI avatar powered by Veed.io — speaking naturally with your cloned voice. --- 🚀 What this workflow does This automation links Veed.io’s video-generation API with multiple AI tools: Analyzes TikTok trends via Perplexity AI Writes a 10-second viral script using GPT-4 Generates your voiceover via ElevenLabs Uses Veed.io (Fabric 1.0 via FAL.ai) to animate your avatar and sync the lips to the voice Creates an engaging caption + hashtags for TikTok virality Publishes the video automatically via Blotato TikTok API Logs all results to Google Sheets for tracking --- 🧩 Setup Telegram Bot Create your bot via @BotFather Configure it as the trigger for sending your photo and theme Connect Veed.io Create an account on Veed.io Get your FAL.ai API key (Veed Fabric 1.0 model) Use HTTPS image/audio URLs compatible with Veed Fabric Other APIs Add Perplexity, ElevenLabs, and Blotato TikTok keys Connect your Google Sheet for logging results --- 🛠️ How to customize this workflow Change your Avatar: Upload a new image through Telegram, and Veed.io will generate a new talking version automatically. Modify the Script Style: Adjust the GPT prompt for tone (educational, funny, storytelling). Adjust Voice Tone: Tweak ElevenLabs stability and similarity settings. Expand Platforms: Add Instagram, YouTube Shorts, or X (Twitter) posting nodes. Track Performance: Customize your Google Sheet to measure your most successful Veed.io-based videos. --- 🧠 Expected Outcome In just a few seconds after sending your photo and theme, this workflow — powered by Veed.io — creates a fully automated TikTok video featuring your AI avatar with natural lip-sync and voice. The result is a continuous stream of viral short videos, made without cameras, editing, or effort. --- ✅ Import the JSON file in n8n, add your API keys (including Veed.io via FAL.ai), and start generating viral TikTok videos starring your AI avatar today! 🎥 Watch This Tutorial --- 📄 Documentation: Notion Guide Need help customizing? Contact me for consulting and support : Linkedin / Youtube

Dr. FirasBy Dr. Firas
39510

Two-way property repair management system with Google Sheets & Drive

This workflow automates the repair request process between tenants and building managers, keeping all updates organized in a single spreadsheet. It is composed of two coordinated workflows, as two separate triggers are required — one for new repair submissions and another for repair updates. A Unique Unit ID that corresponds to individual units is attributed to each request, and timestamps are used to coordinate repair updates with specific requests. General use cases include: Property managers who manage multiple buildings or units. Building owners looking to centralize tenant repair communication. Automation builders who want to learn multi-trigger workflow design in n8n. --- ⚙️ How It Works Workflow 1 – New Repair Requests Behind the Scenes: A tenant fills out a Google Form (“Repair Request Form”), which automatically adds a new row to a linked Google Sheet. Steps: Trigger: Google Sheets rowAdded – runs when a new form entry appears. Extract & Format: Collects all relevant form data (address, unit, urgency, contacts). Generate Unit ID: Creates a standardized identifier (e.g., BUILDING-UNIT) for tracking. Email Notification: Sends the building manager a formatted email summarizing the repair details and including a link to a Repair Update Form (which activates Workflow 2). --- Workflow 2 – Repair Updates Behind the Scenes:\ Triggered when the building manager submits a follow-up form (“Repair Update Form”). Steps: Lookup by UUID: Uses the Unit ID from Workflow 1 to find the existing row in the Google Sheet. Conditional Logic: If photos are uploaded: Saves each image to a Google Drive folder, renames files consistently, and adds URLs to the sheet. If no photos: Skips the upload step and processes textual updates only. Merge & Update: Combines new data with existing repair info in the same spreadsheet row — enabling a full repair history in one place. --- 🧩 Requirements Google Account (for Forms, Sheets, and Drive) Gmail/email node connected for sending notifications n8n credentials configured for Google API access --- ⚡ Setup Instructions (see more detail in workflow) Import both workflows into n8n, then copy one into a second workflow. Change manual trigger in workflow 2 to a n8n Form node. Connect Google credentials to all nodes. Update spreadsheet and folder IDs in the corresponding nodes. Customize email text, sender name, and form links for your organization. Test each workflow with a sample repair request and a repair update submission. --- 🛠️ Customization Ideas Add Slack or Telegram notifications for urgent repairs. Auto-create folders per building or unit for photo uploads. Generate monthly repair summaries using Google Sheets triggers. Add an AI node to create summaries/extract relevant repair data from repair request that include long submissions.

Matt@VeraisonLabsBy Matt@VeraisonLabs
208

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