SAllen MCSD on Thu, 21 Feb 2013 21:22:44

The User Profile Lookup has been removed as a data source in workflow 2013. See

Is there a way to look up a user's department by calling a web service? Are there any examples of looking a user's profile properties?


Ahmed Said Moussa on Sat, 06 Apr 2013 22:24:24

Hey Srallen

Unfortunately this actions has been removed from SP 2013 but as work around do the following steps:

- create new column on your list "UserDepartment"

- create SP 2010 workflow associated to the list and use lookup manager of a user action to return current user department, click fx and select from data source : User Profile and select the user department. add another action to set field return value into the "UserDepartment" column.

- create SP 2013 new workflow and add assign task process then use "UserDepartment" column value as current user department.

hope that you got the idea.

please mark as answered if it helps

RaquelPinto on Sat, 11 May 2013 22:21:35

You can also create a Custom WF activity is Visual Studio 2012, I found that very easy.

No need to code.

Sergej.S on Fri, 12 Jul 2013 16:48:12

I found that this REST API request should return user properties:


But when I use this in "Call HTTP Web Service" I get error "Unauthorized"

Is there way to get this worked?

Roman Šimeček on Thu, 05 Sep 2013 12:39:51

Hi Sergej,

I had the same problem with Unauthorized response. I solved it with adding empty Authorization field to the request headers of my Call HTTP Web Service activity

more info here:


Sergej.S on Mon, 09 Sep 2013 08:53:35

Hi, Roman

Yes, you're right. It's working :) Thank you!

But at first I added Authorization as "" (double quotes) as shown in the MS Article. And nothing worked. But if leave it exactly empty everything works as expected.

Jerry C Cote on Thu, 12 Dec 2013 15:39:54

It looks like you're all working on-prem.  I need to do this on a 2013 workflow in a multi-tenant cloud site.  Apps are not an option - I'm migrating MOSS sites straight across and rebuilding the workflows form scratch, and need user profile info.  The empty authorization header doesn't fix the problem in that case.  I'm able to get a successful call to _api/web/siteusers(@v) as many blogged examples show, but that provides a limited user profile view.  Making the same call to the people manager API - same request headers - is unauthorized.

Is there a proper formation of the Authorization header that will work on O365?

jj_the_Skeptic on Thu, 09 Jun 2016 19:17:47

The example on this page works in o365:

Note that you can't have the blank Authorization Header entry - if you a blank Authorization tag in the header, you will get the error "Access denied. you do not have permission to perform this action or access this resource"