N8n webhook issue

Questions
1

Hi everyone,

I have an Airtable → n8n webhook automation setup.

Workflow:

  • In Airtable, when I change/select a status field, an Airtable Automation triggers.

  • The automation sends the record data to an n8n webhook URL.

  • In Airtable Automation history, all records are showing as “Success” with correct webhook URL and record ID.

Issue:
Today morning, around 20 records were triggered from Airtable, but only 1 record actually reached the n8n webhook workflow. The remaining records never triggered the workflow in n8n.

Important point:

  • Airtable automation history shows successful execution for all 20 records.

  • No webhook errors shown in Airtable.

  • But n8n received only 1 request.

I have build the automation in cloud n8n account.

Please explain why this issue is happened?

Thanks!

2

Please do not do multiple posting on same topic
You still did not provide answer to houda ben’s question

3

Welcome @socialbox to our community! I’m Jay and I am a n8n verified creator.

This is likely a webhook concurrency issue. By default, n8n processes webhooks sequentially on a single worker - when 20 records arrive near-simultaneously, only the first gets through and the rest time out before n8n can queue them. Check two things: first, go to your n8n Executions log and see if there are 20 entries (even failed ones) or just 1 - this tells you if n8n received but dropped them, or never received them at all. If n8n only received 1, the bottleneck is on the ingestion side and you should enable Queue Mode so concurrent webhook calls are properly buffered. If all 20 show in executions but some failed, check the workflow’s error handling instead.

4

Thanks for the explanation.

I tested the same scenario again by selecting and drag-dropping around 24 records in Airtable at once, and this time all 24 records reached n8n and executed successfully without any issue.

That’s why I’m confused — the issue happened only on that particular day where Airtable automation history showed success for all records, but almost none of them reached the n8n webhook.

So I’m wondering:

  • could this have been a temporary network/VPS issue?

  • Airtable-side delivery issue?

  • or maybe n8n webhook was temporarily unavailable at that moment?

In n8n executions, only 1 execution appeared for that failed batch day.

Would Queue Mode still help in this case, or does this sound more like a transient connectivity issue between Airtable and n8n?

5

Since the re-test with 24 records worked perfectly, the original incident was almost certainly a transient issue on that day - either a brief VPS/network hiccup that caused Airtable’s outgoing requests to time out before reaching your webhook, or Airtable itself had a delivery blip. One execution showing up confirms n8n was running fine, just not receiving the others. Queue Mode wouldn’t have helped here since the issue was upstream of n8n. If you want to guard against this going forward, check if Airtable has a retry option for failed automation runs - some plans do.

6

@socialbox Yes this is one of those frustrating ones where everything
looks right but the numbers don’t add up. the “success” status
in airtable just means it sent the request — it doesn’t
confirm n8n actually got it. the drop is almost always one of
these:

  1. test url vs production url — if airtable is calling the
    webhook’s test url (/webhook-test/...), that one only listens
    when you manually click “execute node”. the one record that
    got through was probably during a test session. swap it for
    the production url (/webhook/...) and toggle the workflow
    active.

  2. workflow not active — if the active toggle is off, the
    production url doesn’t listen at all. same silent failure.

  3. n8n cloud concurrency limit — if all 20 hit at once, your
    plan’s concurrent execution cap may have rejected the extras
    (5 on starter, 20 on pro). airtable still logs those as
    success.

quick test — copy the production webhook url, paste it back
into airtable, toggle the workflow active, then update one
record and watch the executions tab. if it lands, try 5 at
once and see how many come through.

were the 20 records updated one-by-one, or all at the same time
from a script or bulk action? changes the likely cause.

7

This is one of the most common “why did only one thing come through?” problems in n8n, and the answer usually comes down to one of three things — so here’s how to diagnose it fast.

First, check your test URL vs. production URL. If Airtable is calling the test URL, only the one that lands while you happen to have the editor open will succeed. Swap to the production URL in Airtable and make sure your workflow is set to Active.

Second, if you’re on n8n Cloud, check your plan’s concurrent execution limit; records beyond your limit get rejected.

Third, if you’re self-hosted, the default single-worker setup processes webhooks sequentially. Enabling Queue Mode (via Redis) lets n8n buffer and process them properly.