Webhook Trigger Creating Multiple Records from Single Event

Ask for Help
1

Hi Glide Community! :waving_hand:

I’m experiencing an issue where my webhook trigger is saving multiple duplicate records to my table, even though I’m only sending the webhook once.

image
image830×834 70.4 KB

Any insights would be greatly appreciated! :folded_hands:
Thanks in advance!

1 Like
2

Can you show us a sample log where it would write multiple records?

What conditions are you using for your Users loop?

1 Like
3

I’m seeing a strange issue:

  • Webhook log table shows only 1 entry (correct)
  • User profile table shows multiple duplicate entries (problem)

The webhook is triggering only once according to logs, but somehow creating duplicate records in my user profile table. Not sure why this is happening.

4

My requirement:

  • Receive data from external source via webhook
  • Check if email already exists in user profile table
  • Save the record accordingly
1 Like
5

Can you show me how you’re setting up the Loop part? I assume you’re just adding values to the newly added row?

1 Like
6

Yes,
I want to store data into my user profile table but can’t find the source table reference in my workflow setup.

As a workaround, I’m using a loop flow to achieve this. Is this the correct approach, or is there a better way to directly reference and update the user profile table?

Can anyone advise on the proper method?

1 Like
7

image
image1602×664 57 KB

1 Like
8

image
image1597×688 71.7 KB

1 Like
9

Can I access the user table directly without using a loop in my workflow?

1 Like
10

So can you explain what is the end goal here? You add a row, and then use a n8n scenario to enrich the info?

1 Like
11

Just sharing my current workflow setup:

  1. Receive data via webhook
  2. Save it into user profile table
  3. Pass the data to n8n platform
1 Like
12

Why do you need to having seemingly two scenarios here? Is one intended to add the row, and the other to process with n8n? Are they both enabled or just the “copy” version?

1 Like
13

whenever we receive data via webhook, we need to store it in the user profile table and then pass it to the N8N platform.

1 Like
14

So the data received from webhook should always create a new users row, then you pass that data to n8n to do more stuff, and receive data back to set to the same users row?

1 Like
15

Yes,

1 Like
16

I would build on the idea using only one webhook workflow:

  • Receive info through the webhook.
  • Create a new users row.
  • Pass the info to n8n, I assume you wait for a response here.
  • Parse the response.
  • Loop through the Users table, filter by rowID is the added row above’s rowID (or if you can loop directly with the output of the add row, it’s better, I haven’t used this before).
  • Set the fields from the n8n response to the row.
1 Like