Hi ​@Mishal Ali! 👋 

If I’m understanding correctly you’d want two Zaps:

• Zap 1 triggers when new staff details are added to a spreadsheet and sends out the onboarding emails. A couple of days later it checks the spreadsheet row to see if the confirmation has been submitted. If it hasn’t then it adds the relevant name and email to a new worksheet in the same spreadsheet and send out a reminder email.

• Zap 2 triggers when the second form is submitted and updates the relevant row in the spreadsheet that the first Zap triggers on.

To handling the conditional logic for the delay and reminder part of Zap one that’s doable with a Delay For action followed by a Lookup Spreadsheet Row (Google Sheets) search action, then you’d use Paths to check if the confirmation field in the row is still empty or not. In the path that runs if the field is empty you could use a Create Worksheet and Create Spreadsheet Row actions to create the worksheet and add the relevant information to it, then use a Send Email type of Email app action to send out a reminder.

That said, if you don’t need to carry out a different action(s) when the confirmation field has been filled then you could use a Filter instead of paths, which would allow you to stop the Zap from continuing if the confirmation field is filled. 

For Zap 2 to update the correct row you’d need to use a Lookup Spreadsheet Row (Google Sheets) search action to locate the original entry by searching for something unique (like the staff member’s email address), then use an Update Spreadsheet Row action to add the confirmation to the relevant row.

Hope that helps to get you pointed in the right direction. If I’ve misunderstood or you run into any trouble on that, let us know! 🙂

Hi ​@SamB 

thank you for your time and super helpful detailed replay

I am new to zaps. sometime I know the functions but dont know how to utilize it in zaps.

I am going to try paths and lookup spreadsheet, which I think will cover what I was missing in my setup

trial is ongoing 

regards :)

Hi ​@Mishal Ali,

Just keep us on the loop so we can assist you further if needed. Thank you.

Hi ​@JammerS 

thank you for your interest in my post. your time and replay is very appreciated

Hi ​@SamB 

I am having problem to send the confirmation to the right field

2 zaps

1st: reads from spreadsheet → sends  email: works fine

2nd: send google form submission confirms the user activation to the targeted field 

in the lookup step, I chose a unique field to search for ( user input from the confirmation google form) but in the next step, update raw,

 it asks for a specific raw and new submissions go to the same field

it should search for the input and update the specific field in the same raw. but in this setting it is a fixed field in fixed raw ( 18 as attached)

I tried making search step and add 1 field in the confirmation form to use as a guide for the epdate raw step but no input to the spreadsheet

I am taking baby steps to master each one after fixed this step I will do the reminder action 

thank you :)

Hi ​@Mishal Ali,

You’d need to map the row ID from the Lookup Spreadsheet Row step to the “Row” field of the Update Spreadsheet Row step. We have a help article on how to do that here: https://help.zapier.com/hc/en-us/articles/8495978803213-Find-and-update-spreadsheet-rows-in-Google-Sheets-on-Zapier

Kindly give it a try and let me know how it goes? I'll keep an eye out for your response!

Thanks for getting back to me, ​@Mishal Ali! Glad to hear the approach I suggested was helpful. 😊

Looks like Ken’s suggestion should help to get the Zap updating the correct row—keep us posted on how you get on with that. We want to make sure you’re all set!

Hi ​@ken.a and ​@SamB 

thank you it is very helpful article.

it was the three dot icon option than I needed 

I am going to test it in separate simple 1 zap from to sheet and apply it to my original one

i am very thankful for your super helpful replies. for the late replay, I was out of town 

regards :) 

Hi ​@Mishal Ali,

I'm glad to hear the article and support from ​@ken.a  and ​@SamB  were helpful! Testing with a simple Zap first is a smart move before scaling up. If you run into any issues or need further help, we're here for you. Feel free to reach out anytime.