<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
0D54z0000AIeEaHCQVOkta Identity EngineWorkflowsAnswered2025-01-31T16:47:24.000Z2025-01-13T12:33:52.000Z2025-01-31T16:47:24.000Z
  • TimL.58332 (Workflows)

    @User17001485525627711781 (Customer)​  This would be expected behavior. The field you are trying to dynamically populate isn't an "Input" field it is part of options.

     

    If you want to dynamically construct sheets/worksheets you would need to leverage Custom API Action (CAPIA) and Googles sheet's documentation to build out the body payload structure.

    Expand Post
    Selected as Best
  • Mihai N. (Okta, Inc.)

    Hi @User17001485525627711781 (Customer)​ , Thank you for reaching out to the Okta Community! 

     

    Please check this article on how to use the Spreadsheet ID to see if it helps with your implementation. 

     

     

     

    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.

    Expand Post
  • MatthewH.10249 (State of Iowa)

    I was able to reproduce the issue you are having. I suggest you open an Okta Support case. It looks like you can hardcode a value but not pass text from another card. I even tried to pass a value form a compose card and that returns the same "Cannot drop here" message. I don't recall this being an issue but I've not found any old Workflows where I dynamically passed in a value so maybe it is functioning how it always has. If that is the case consider opening an "Ideas" feature request and add a comment to this post with a link to your "Ideas" post so others can up vote it. I will upvote it!

    Expand Post
  • TimL.58332 (Workflows)

    @User17001485525627711781 (Customer)​  This would be expected behavior. The field you are trying to dynamically populate isn't an "Input" field it is part of options.

     

    If you want to dynamically construct sheets/worksheets you would need to leverage Custom API Action (CAPIA) and Googles sheet's documentation to build out the body payload structure.

    Expand Post
    Selected as Best
This question is closed.
Loading
I cannot link spreadsheet id in okta workflow