# How to get more information on which items triggered an error?

**URL:** <https://community.n8n.io/t/how-to-get-more-information-on-which-items-triggered-an-error/135360>\
**Category:** Questions\
**Created:** [June 19, 2025, 3:27pm UTC](https://community.n8n.io/t/how-to-get-more-information-on-which-items-triggered-an-error/135360 "2025-06-19T15:27:58Z")\
**Posts on this page:** 11\
**Page:** 1

<div class="post-metadata">

**Author:** ![Alexandre\_Pariente](https://dub1.discourse-cdn.com/n8n/user_avatar/community.n8n.io/alexandre_pariente/32/66599_2.png) [@Alexandre\_Pariente](https://community.n8n.io/u/Alexandre_Pariente)\
**Post date:** [June 19, 2025, 3:27pm UTC](https://community.n8n.io/t/how-to-get-more-information-on-which-items-triggered-an-error/135360/1 "2025-06-19T15:27:58Z")

</div>

I am trying to give access to a drive folders to a bunch of emails. This operation is gonna be repeated in different ways so I cannot activate the email notification to notify users.  
The issue is : some of these emails are not linked to a Google account.  
When this is the case and notification is turned off, it triggers an error.

I’m thinking of the following solution: using the “on error: Continue (using error output)” option, and then running the same node with the notification activated - as you can see in the middle branch.

However the only output I get on the error branch is the error message.

Is there a way to know which items triggered the error so I could grab associated emails to run the request again?  
Any better option I could go with?

Any help greatly appreciated!

self hosted on hostinger, v 1.95.3

---

<div class="post-metadata">

**Author:** ![jabbson](https://dub1.discourse-cdn.com/n8n/user_avatar/community.n8n.io/jabbson/32/87328_2.png) [@jabbson](https://community.n8n.io/u/jabbson)\
**Post date:** [June 19, 2025, 7:10pm UTC](https://community.n8n.io/t/how-to-get-more-information-on-which-items-triggered-an-error/135360/2 "2025-06-19T19:10:12Z")

</div>

In the second gmail node, which receives the error, the “Send Notification Email” option is added, but is not enabled.

---

<div class="post-metadata">

**Author:** ![Alexandre\_Pariente](https://dub1.discourse-cdn.com/n8n/user_avatar/community.n8n.io/alexandre_pariente/32/66599_2.png) [@Alexandre\_Pariente](https://community.n8n.io/u/Alexandre_Pariente)\
**Post date:** [June 20, 2025, 8:22am UTC](https://community.n8n.io/t/how-to-get-more-information-on-which-items-triggered-an-error/135360/3 "2025-06-20T08:22:46Z")

</div>

This node is not configured.  
My issue is I dont know how to get the data I need passed to this node.

This is what I get :

 ![Capture d’écran 2025-06-20 à 10.21.30](https://europe1.discourse-cdn.com/n8n/original/3X/0/6/063d08be1b5b5ab09c4127fdf0553ef12c5023bd.png)

And what I need is to identifiy the emails that match the items that output errors in the previous node.

---

<div class="post-metadata">

**Author:** ![Wouter\_Nigrini](https://dub1.discourse-cdn.com/n8n/user_avatar/community.n8n.io/wouter_nigrini/32/150261_2.png) [@Wouter\_Nigrini](https://community.n8n.io/u/Wouter_Nigrini)\
**Post date:** [June 20, 2025, 8:29am UTC](https://community.n8n.io/t/how-to-get-more-information-on-which-items-triggered-an-error/135360/4 "2025-06-20T08:29:18Z")

</div>

Perhaps you need to use the Loop node here. Iterate over each email, do your validations and processing, then move onto the next. This way you should know which email was flagged and then you can reference the node with the content using a named references like `$('Get Email').first().json`

---

<div class="post-metadata">

**Author:** ![Alexandre\_Pariente](https://dub1.discourse-cdn.com/n8n/user_avatar/community.n8n.io/alexandre_pariente/32/66599_2.png) [@Alexandre\_Pariente](https://community.n8n.io/u/Alexandre_Pariente)\
**Post date:** [June 20, 2025, 9:42am UTC](https://community.n8n.io/t/how-to-get-more-information-on-which-items-triggered-an-error/135360/5 "2025-06-20T09:42:24Z")

</div>

I’ve simplified and duplicated the workflow so it’s clearer.

Are you suggesting something like this ?

I feel like there is something to do with this idea but I’m still stuck 😅

I can see which email was successfully processed if I go through the output by hand but still cant pass the data automatically.

Not sure how to use `$('Get Email').first().json`

Could you precise what you have in mind ?

Thanks for the support!

---

<div class="post-metadata">

**Author:** ![Wouter\_Nigrini](https://dub1.discourse-cdn.com/n8n/user_avatar/community.n8n.io/wouter_nigrini/32/150261_2.png) [@Wouter\_Nigrini](https://community.n8n.io/u/Wouter_Nigrini)\
**Post date:** [June 20, 2025, 12:05pm UTC](https://community.n8n.io/t/how-to-get-more-information-on-which-items-triggered-an-error/135360/6 "2025-06-20T12:05:30Z")

</div>

I actually miss read your initial issue, but I understand it now. You want to give valid google accounts access to a google drive folder. What do you want to do with the failed email accounts? I’ll update your workflow shortly. For now I’ll just list the failed email accounts when the loop is done

---

<div class="post-metadata">

**Author:** ![Alexandre\_Pariente](https://dub1.discourse-cdn.com/n8n/user_avatar/community.n8n.io/alexandre_pariente/32/66599_2.png) [@Alexandre\_Pariente](https://community.n8n.io/u/Alexandre_Pariente)\
**Post date:** [June 20, 2025, 12:43pm UTC](https://community.n8n.io/t/how-to-get-more-information-on-which-items-triggered-an-error/135360/7 "2025-06-20T12:43:15Z")

</div>

With the failed email accounts I want to share the same folder but this time with notification option turned on (this is the condition so Google can send them an invite).

Thanks mate!

---

<div class="post-metadata">

**Author:** ![Wouter\_Nigrini](https://dub1.discourse-cdn.com/n8n/user_avatar/community.n8n.io/wouter_nigrini/32/150261_2.png) [@Wouter\_Nigrini](https://community.n8n.io/u/Wouter_Nigrini)\
**Post date:** [June 20, 2025, 1:03pm UTC](https://community.n8n.io/t/how-to-get-more-information-on-which-items-triggered-an-error/135360/8 "2025-06-20T13:03:49Z")

</div>

Here is my solution:

 ![image](https://europe1.discourse-cdn.com/n8n/original/3X/6/a/6ad27bc1f6b01daf173e3190fce4f2a913863b07.png)

 ![image](https://europe1.discourse-cdn.com/n8n/original/3X/2/0/20936aa2dffb14f5f81a58d18745c3068859f50f.png)

I had 2 valid gmail accounts which worked and 2 fake accounts which failed

---

<div class="post-metadata">

**Author:** ![Wouter\_Nigrini](https://dub1.discourse-cdn.com/n8n/user_avatar/community.n8n.io/wouter_nigrini/32/150261_2.png) [@Wouter\_Nigrini](https://community.n8n.io/u/Wouter_Nigrini)\
**Post date:** [June 20, 2025, 1:07pm UTC](https://community.n8n.io/t/how-to-get-more-information-on-which-items-triggered-an-error/135360/9 "2025-06-20T13:07:53Z")

</div>

> [@Alexandre\_Pariente](#):
>
> With the failed email accounts I want to share the same folder but this time with notification option turned on (this is the condition so Google can send them an invite).
> 
> Thanks mate!

In that case the same thing, just add the Drive node with notification, however, why dont you just have a single drive node with the notificaiton option always enabled? This way everyone will get the notificaiton?

---

<div class="post-metadata">

**Author:** ![Alexandre\_Pariente](https://dub1.discourse-cdn.com/n8n/user_avatar/community.n8n.io/alexandre_pariente/32/66599_2.png) [@Alexandre\_Pariente](https://community.n8n.io/u/Alexandre_Pariente)\
**Post date:** [June 22, 2025, 10:38am UTC](https://community.n8n.io/t/how-to-get-more-information-on-which-items-triggered-an-error/135360/10 "2025-06-22T10:38:49Z")

</div>

That’s perfect thanks a lot mate!

I didn’t know we could call for some data that doesn’t show in the output!

---

<div class="post-metadata">

**Author:** ![system](https://dub1.discourse-cdn.com/n8n/user_avatar/community.n8n.io/system/32/195824_2.png) [@system](https://community.n8n.io/u/system)\
**Post date:** [June 29, 2025, 10:39am UTC](https://community.n8n.io/t/how-to-get-more-information-on-which-items-triggered-an-error/135360/11 "2025-06-29T10:39:28Z")

</div>

Closed on June 29, 2025, 10:39am UTC

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.
