@Aggarwal What do you want to to in your workflow? 

You could only work with the update trigger and once you closed the survey trigger some updates (e.g., set a dummy embedded data field) via the update response API for each of the responses. 

This way you would have all the response details available in each execution. 

As mentioned - it depends a little bit on what you want to do with your workflow. Might be that you could work with scheduled workflows. 

Best
Christian

@Aggarwal You could also work with an ETL workflow which extracts the responses from the survey and loops each response. In the loop you could implement your desired logic.

If implementing the logic within the loop is somehow restricted, you could pass each response data to a separate JSON event. The loop would then only contain a webservice request.

With the “Run Immediately” you could execute it one time once you have implemented your logic.

Best
Christian

@Aggarwal Another options is to just keep your workflow as it is “when respondent finish the survey” and keep them from finish until you want to.

1. Create a fake End of Survey, a goodbye at the end of the survey and use some code to hide the button How can I hide the previous and next buttons on my survey? | XM Community (qualtrics.com)
   This keep the respondent from reaching the actual End of Survey
2. Make sure the setting for unfinished response is set to record and the time is maybe 1 year (to keep them from finished prematurely)Incomplete Survey Responses (qualtrics.com)
3. When the time come, just go to Responses in Progress in Data & Analysis and finish all of the responses at once.

Hope this helps

Good point @Nam Nguyen  So there is different options for you @Aggarwal: 

1. Avoid that the survey gets actually completed using a fake end of survey to be able to manually close all responses once you decide to close your project - see @Nam Nguyen’s comment. 
2. Create an ETL workflow which loads the survey responses and loops through each of them as described here. Execute it one-time. 
3. Trigger the workflow for API updates and trigger some dummy updates once you are ready as described here. 

Best
Christian

Hi,

I think what you want is the survey definition event. You can use it to trigger it on survey publication, activation or, in your case, closure. See https://www.qualtrics.com/support/survey-platform/actions-page/survey-definition-events/

Use desired ETL tasks after that to do what you need to do with your data.

Best,

@vgayraud Hadn’t this on my list. Good to know… Thank you!

@vgayraud Somehow I forgot about that triggering option. Great find