Hi,
Maybe using a web service task and the Import Participants API?
https://api.qualtrics.com/fc78c0194ee54-import-participants
Thanks Vincent!
I had looked in the API guide, but somehow I overlooked the EX categoryThanks for pointing me to it!
@vgayraud , I am testing this out,
It works fine if I call the API with hardcoded values.
But when I try to add it into my Workflow, and fill up the required fields in the API call with variables,
I can find the variables for First Name, Last Name, and Email,
but I can’t find the Employee Unique Identifier.
Do you perhaps know if/how to pipe in the Employee’s Unique Identifier?
Hi @JoycaV ,
I’m not the most familiar with EX, but it indeed seems to be incredibly difficult to retrieve the uniqueId and participantId…
The only place I found it accessible is by setting up a scheduled daily “Extract responses from survey” workflow. The ED field “Participant’s Unique Identifier” is in the list of downloadable fields.
From there, I assume you could load the responses into an IDP (https://www.qualtrics.com/support/survey-platform/actions-page/etl-workflows/data-loader-tasks/load-into-a-data-project-task/) and have a 2nd workflow in the IDP triggered by a “Data Set Record” event (https://www.qualtrics.com/support/survey-platform/actions-page/events/dataset-record-events/).
You could then use the “Get Participant” https://api.qualtrics.com/9f1dc7785bd26-get-participants-post with the uniqueIdentifier piped in the body to retrieve the participantId.
And finally call the “Import Participant” API with the participantId.
I haven’t tested any of this, but I think it might work. As I said, I’m not very familiar with the EX Directory and projects and there might be an easier way to achieve this.
Good luck! :)
After checking your answer @vgayraud, and asking the Qualtrics Support assistant bot, and about to contact the human support team,
I decided to try if I could just “guess” the field name by just typing it.
I tried ${e://Field/UniqueID}, ${e://Field/UniqueIdentifier} and ${e://Field/Unique_Identifier},
and guess what,
${e://Field/UniqueIdentifier} worked
So even though it’s nowhere in the dropdown lists to select as piped text, it does exist and that’s the code