We have a workflow of a Web Hook to Google Sheets, with data from a website visitor pixel. We are seeing all the resolutions on the Pixel side, and there are multiple resolutions in the webhook that are not showing up in Google Sheets.
Is it a time/speed issue? We are getting a Lot of web traffic - but only 10% are being captured in the Google Sheet.
Webhook in “Respond Immediately” Mode (Race Condition), if the webhook is configured in “Respond Immediately” mode, but the rest of the flow (such as inserting into Sheets) continues to run in the background, it may be canceled prematurely if there is a client timeout or high load. Use “Respond After Workflow” mode in the Node Webhook to ensure it completes before responding.
High incoming inflows = lost executions; n8n has concurrency limitations if not configured for high load. Each webhook creates an execution, and if hundreds arrive per minute and the system is in EXECUTIONS_PROCESS=main mode, it is easier for them to become congested or lose events.
You should run n8n in queue mode with Redis for better performance. Or split the load: have intermediate webhooks that only buffer events (saving them to Redis, S3, or a file), and a separate flow that processes them in batches.
In Google Sheets: throttling or silent errors. The Google Sheets API has limits of ~60 requests per minute per user. Writing to large sheets can slow down or fail without logging the error if there is no failure control.
You should add retry nodes (“Retry on Fail”) with incremental wait. Use SplitInBatches to insert 5–10 rows per cycle. Validate the nodes for errors (Enable “Continue on Fail” to log what failed).