I may be incorrect, but it seems like you need to switch your yes and no statements on Step 5. I would try that to start. The reason is you are saying if the user exists in Docebo, you need to create it.

Hi @emily.mccarthy, 

Thank you so much for the response. In step 4 it checks if the the response from step 3 equals 0. If it is equal to 0 then that means they do not exist in Docebo and then should be created. I am fairly confident that section is correct because I worked with a Docebo employee for that part. However, recently my connect specialist hasn’t been responding so I figured turning to the community may be my best option. Have you done something similar in Connect before? I am open to reconfiguring the entire recipe if you know a better way to complete this process. I appreciate any and all help.

Hi @jpizano ,

Step 4 and 5 contradict each other. If the length of the items in step 3 is zero there is nothing to iterate and the statement at step 5 will never execute. (I think this may be the gist of @emily.mccarthy s response)

The only use I can see for step 5 is if more than one employee were delivered with each trigger of the recipe. It can occur that webhooks deliver payloads in batches rather than individually. In that case the For would iterate through all the items in step 1, not step 3, and steps 2 and 3 would be inside the loop. So, I don’t think that is the intention here. 

What you could try, if you are in test mode, is to move step 6 up above step 5, i.e. out of the loop, and then skip step 5 (or step 6 as it will be after this move). Then repeat one of the jobs in the job list and see what happens. 

Hi @pdevaney ,

Thank you for the clarification. I think I have a misunderstanding of the initial call. Yesterday I noticed that the trigger was only pulling one person even though I confirmed there should be 10 people pulled in from the trigger (10 new employees). Even if I run the code multiple times, it only pulls the same person. Would you be able to give me some clarity on how to change the code so the trigger pulls in everyone that it needs? I am open to starting everything over from scratch and approaching it a different way.

Hi @jpizano,

Ok, I’m flying a little blind here. You mention your Connect specialist. For this kind of detailed work it is almost certainly the case that if you can get your specialist to go on line and work through this it will be a lot quicker. With that said, a couple of questions:

1. Have you done the Connect training in the Docebo University?
2. You say that there should be 10 people pulled in. How did you confirm this?. Do you mean that you changed or added 10 employees in the source system? Or, do you have a job with 10 people in the payload. 

As I say, I would strongly suggest working through this with your Connect specialist but if you can give me a bit more information as per question 2 I’ll see what I can do.

@pdevaney 

1. Yes, I have completed the recommended courses in Docebo University.
2. We created 10 new profiles in our HRIS system for the 10 new hires that were onboarded. I confirmed the output for the tests and the trigger step is only outputting one person when it runs and if you re-run the script it will just pull the same person. 

I do have a Connect specialist because we are currently in week 6 of the onboarding phase but I was having trouble getting responses from my point person for the onboarding process and that is why I reached out here with the deadline approaching. They did get back to me with some examples that other Docebo users have created for the same use case that we are trying to achieve which helped a lot. Since UKG is not a prebuilt connector the process to pull people in is A LOT more complex than originally laid out in our blueprint guide. I appreciate all the help but I think I have a possible way forward now that I have those examples. I appreciate you and @emily.mccarthy for reaching out.