JessP.69202 (Customer) asked a question.
I'm trying to create a workflow that will take a user's DocuSign ID from that app and then put it in a field in the user profile within Salesforce. The problem I'm running into is the Update User Salesforce card only takes User ID as an input and that you can't use the email address of the user (which would be so much easier to do and would love to see that change on this card). I was able to use the Search User card, but the output is a list of objects and I can't drag and drop the user ID into the Salesforce Update User card. I tried using Pluck, but it just creates another list of objects. I also tried using the application: User ID from the event card (when user is assigned Salesforce app in Okta) as the documentation said that this output was the unique user ID the application assigned to the user. When I ran the flow, everything worked up until the Salesforce card as the User ID from Okta didn't match the user ID in Salesforce. My questions are, where to get the Salesforce User ID as the only input into that Update User card, can the Salesforce connector cards inputs be updated to include searching for the user's email address in Salesforce, and if all else fails, what kind of helper flow or function can I use that will take an element from the object list, turn it into text and then use it as an input into the Salesforce card to update a user?
The cards Okta provides for third-party vendors utilize the third-party's public API endpoints and are designed for ease-of-use and repeatable functions and usually only contain common endpoints & Custom API Action can be leveraged for the uncommon ones. The cards that require specific inputs are constrained by the vendor as their endpoint requires those specific values for said specific actions.
In your instance you would need to leverage a "Search Users" card which allows you to search SFDC by email or username to obtain a user and said users ID. That resulting ID could then be passed into the update card along with the properties you wish to update.
In Salesforce Username is unique but email is not. Because of this with "Search Users" if email is selected it can return a list of objects (because that is the body salesforce returns with the request to their endpoint).
If you know for certain emails are always going to be unique in your implementation of Salesforce you can pass the resulting list from the "Search Users by Email" into an Object - Get card with a path of 0.User ID to obtain the ID of the user which could then be used later in the flow.
Hi Tim,
Thanks! It looks like it worked when I tested it! I'll verify it works when we get a new user. Thanks again for your help!