GOHIGHLEVEL ANSWERS & PROMPTS: PLAYBOOK T43 · WEBHOOK CONCURRENCY & N8N MEMORY GUARDS
AUTHOR: DANIEL HALLMAN
KEYWORD: N8N MEMORY
PLAYBOOK T43 · Webhook Concurrency & n8n Memory Guards KEYWORD: N8N MEMORY

How Do You Stop Self-Hosted n8n Out-of-Memory Crashes When Multiple Webhook and GoHighLevel Workflows Run at Once?

Answer: When a self-hosted n8n instance on a 2GB VPS runs 40 workflows and crashes with an Out of Memory (node) error whenever three heavy jobs fire at once, adding Redis and worker containers onto the same 2GB server will still run out of RAM. Upgrade the VPS to 4GB to 8GB RAM, set N8N_CONCURRENCY_PRODUCTION_LIMIT=2 and EXECUTIONS_DATA_PRUNE=true (72 hours) so heavy scraping jobs cannot spike memory simultaneously, and capture client leads inside GoHighLevel Contacts first before firing outbound webhooks to n8n.

STEP-BY-STEP INSTRUCTIONS + ANNOTATED GHL SCREENSHOTS

Steps in GoHighLevel

  1. STEP 1
    In Settings > Custom Fields (and Contacts), store incoming form and ad leads directly on the GoHighLevel contact record first, adding a Webhook Sync Status field (Pending, Synced) so the lead is saved before any external n8n job runs.
    REAL GHL SCREEN · SETTINGS > CUSTOM FIELDS ANNOTATED GHL SCREENSHOT
    Annotated GoHighLevel Custom Fields screenshot showing Settings > Custom Fields menu, Contact/Opportunity/Company object filters, and + Create field button
    1Open Settings > Custom Fields 2Filter by Contact or Opportunity Object 3Click + Create Field
  2. STEP 2
    In Automation > Workflow Builder, place a Drip step (10 contacts per minute) ahead of your Outbound Webhook action to n8n, and configure N8N_CONCURRENCY_PRODUCTION_LIMIT=2 plus EXECUTIONS_DATA_PRUNE=true (EXECUTIONS_DATA_MAX_AGE=72) on a 4GB+ VPS so parallel scraping jobs queue cleanly instead of crashing Node.
    REAL GHL SCREEN · AUTOMATION > WORKFLOW BUILDER CANVAS ANNOTATED GHL SCREENSHOT
    Annotated GoHighLevel Workflow Builder canvas screenshot showing If/Else condition branch, priority routing steps, and Builder/Settings/Execution logs tabs
    1Add If/Else Condition & Tag Guard 2Chain Priority & Wait Steps 3Switch to Settings or Execution Logs
  3. STEP 3
    In Automation > Workflow > Execution Logs, filter by Webhook actions to trace any 502 or timeout responses during server maintenance and re-enroll contacts whose Webhook Sync Status is still Pending.
    REAL GHL SCREEN · WORKFLOW > EXECUTION LOGS ANNOTATED GHL SCREENSHOT
    Annotated GoHighLevel Workflow Execution Logs screenshot showing Execution logs tab, All actions and All statuses filters, and populated contact run rows
    1Open Execution Logs Tab 2Filter by Action Type or Status 3Search Contact to Trace Runs
MODE: AGENT PROMPT
PASTE INTO CLAUDE CODE, CURSOR, CHATGPT, OR GOHIGHLEVEL ASK AI AGENT PROMPT
Protect GoHighLevel-to-n8n webhook workflows from out-of-memory drops in sub-account <YOUR_LOCATION_ID>:
1. In Settings > Custom Fields, create a Webhook Sync Status field on the Contact object.
2. In Automation > Workflow Builder, save the contact and send the immediate SMS confirmation in GoHighLevel first, then add a Drip throttle before firing the Outbound Webhook to n8n (with N8N_CONCURRENCY_PRODUCTION_LIMIT=2 on the server).
3. In Automation > Workflow > Execution Logs, filter by failed webhook steps to retry any pending contacts.
Cause
  • Running 40 active webhook and scraping workflows on a 2GB VPS leaves almost zero headroom once Postgres, Docker, and Node load into memory.
  • If three browser or large-JSON workflows trigger at the same time, each execution allocates 300MB+ of heap until the Linux OOM killer terminates the Node process and drops incoming client webhooks.
GoHighLevel Configuration
  • Cap active production runs with N8N_CONCURRENCY_PRODUCTION_LIMIT=2, prune execution history every 72 hours, stagger scheduled scraping jobs
  • and land raw ad or form submissions in GoHighLevel (Contacts and Automation > Workflow Builder) before calling n8n so a busy worker never loses a lead.
MENU PATH REFERENCE

GoHighLevel Menu Paths

Step Menu Path in GHL Action
Step 1 Settings > Custom Fields Store incoming form and ad leads directly on the GoHighLevel contact record first, adding a Webhook Sync Status field (Pending, Synced) so the lead is saved before any external n8n job runs.
Step 2 Automation > Workflow Builder Place a Drip step (10 contacts per minute) ahead of your Outbound Webhook action to n8n, and configure N8N_CONCURRENCY_PRODUCTION_LIMIT=2 plus EXECUTIONS_DATA_PRUNE=true (EXECUTIONS_DATA_MAX_AGE=72) on a 4GB+ VPS so parallel scraping jobs queue cleanly instead of crashing Node.
Step 3 Automation > Workflow > Execution Logs Filter by Webhook actions to trace any 502 or timeout responses during server maintenance and re-enroll contacts whose Webhook Sync Status is still Pending.
3-step diagram showing Cap active runs to limit concurrent executions to 2, Prune run history after 72 hours, and Save leads first in the CRM before firing webhooks.
VISUAL PLAYBOOK · PLAYBOOK T43 (WEBHOOK CONCURRENCY & N8N MEMORY GUARDS) Back to Annotated GHL Screenshots ↑
DEFAULT SETUP VS. AUTOMATED WORKFLOW

Operational Comparison

Speed to Lead & Callback Safety
Default 0s Checkbox: Collides with Rep
45s Guard Workflow: Zero Collision
Caller Reply & Booking Rate
Generic 'We Missed You' SMS: 12%
Question-First Workflow SMS: 64%

Related Questions

BUILD FASTER IN GOHIGHLEVEL · FREE TRIAL BONUSES + MCP SERVER

Build this directly inside your GoHighLevel sub-account

Connect Claude Code, Cursor, or OpenAI Codex to our ghl-tools MCP Server & Rust CLI to build workflows, forms, and funnels from your editor, or start your GoHighLevel plan through our partner link to unlock $612+ in ready-to-import kits (including GHL & n8n Webhook Queue Reliability Pack) and weekly live clinics.