<iframe src="https://www.googletagmanager.com/ns.html?id=GTM-M74D8PB" height="0" width="0" style="display:none;visibility:hidden">
Loading
Skip to NavigationSkip to Main Content
0D5KZ000015aKha0AEOkta Identity EngineWorkflowsAnswered2025-07-08T17:47:01.000Z2025-07-08T08:58:35.000Z2025-07-08T17:47:01.000Z

JakeR.78774 (Customer) asked a question.

Trouble converting a list of numbers to text using pluck in Okta Workflows

I have a list of numbers and need to convert it back to text to write it back to the table so we can keep records for audit purposes.

The documentation around Pluck all show examples of things where a key exists.

Is there a different tact I should be taking instead of Pluck to convert this list of numbers back into text separated by commas?

 

I've plugged various things into "key" to no avail (0, [], ., root, etc.).

 

/help/servlet/rtaImage?refid=0EMKZ000000xF2a

/help/servlet/rtaImage?refid=0EMKZ000000xF2f

 

Any help is appreciated.

 

Have already explored these articles to no avail:

https://help.okta.com/wf/en-us/content/topics/workflows/function-reference/list/list_pluck.htm

 


  • Hi @JakeR.78774 (Customer)​ , Thank you for reaching out to the Okta Community! 

     

    As far as I've been able to gather info on the subject, "pluck" might not be a the way to go about this, right? "pluck" is used explicitly when using a "list of objects",but if I'm understanding this correctly, you are just using a list of numbers, so "list to text" should just be used as is.

     

    While this isn't my area of expertise, I ran it by some of my Workflows colleagues and they mentioned that when working with the Intersected List value, you'll need to locate the card earlier in your flow that produces this output. Change that card's output type to Text. Afterward, pass this output directly into the List to Text card. This is often the case when using cards like List Intersection.

    Here's an example using the List Intersection card. 

    Intersection 

     

     

    They also mentioned that you should not be using tables for audit purposes. 

    While Workflows has features for auditing, it's crucial to understand that these are not designed to be the primary or only source of truth for all auditing needs.

     

     

     

    If my answer helped, remember to mark it as best to increase its visibility for other members of the Okta Community who might have the same questions as you. 

     

    Hope my answer helps! 

     

    --

    Help others in the community by liking or hitting Select as Best if this response helped you.

    Collect them all. Learn a new skill and earn a new Okta Learning badge.

    Expand Post
    Selected as Best
  • Hi @JakeR.78774 (Customer)​ , Thank you for reaching out to the Okta Community! 

     

    As far as I've been able to gather info on the subject, "pluck" might not be a the way to go about this, right? "pluck" is used explicitly when using a "list of objects",but if I'm understanding this correctly, you are just using a list of numbers, so "list to text" should just be used as is.

     

    While this isn't my area of expertise, I ran it by some of my Workflows colleagues and they mentioned that when working with the Intersected List value, you'll need to locate the card earlier in your flow that produces this output. Change that card's output type to Text. Afterward, pass this output directly into the List to Text card. This is often the case when using cards like List Intersection.

    Here's an example using the List Intersection card. 

    Intersection 

     

     

    They also mentioned that you should not be using tables for audit purposes. 

    While Workflows has features for auditing, it's crucial to understand that these are not designed to be the primary or only source of truth for all auditing needs.

     

     

     

    If my answer helped, remember to mark it as best to increase its visibility for other members of the Okta Community who might have the same questions as you. 

     

    Hope my answer helps! 

     

    --

    Help others in the community by liking or hitting Select as Best if this response helped you.

    Collect them all. Learn a new skill and earn a new Okta Learning badge.

    Expand Post
    Selected as Best
    • JakeR.78774 (Customer)

      Changing the output type to text on the intersection card and removing the pluck worked!

      Thank you!

       

      Screenshot 

       

      And noting that the "audit" here was more of as a reference we can refer back to so we can have a before and after output handy for CYA purposes, not an official "audit" per se.

      Expand Post
This question is closed.
Loading
Trouble converting a list of numbers to text using pluck in Okta Workflows