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?
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
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
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).
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?
