You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I tweaked this code, and instead of a single-user picker I need to use a multi-user picker, but can't figure out how...
I've been able to kind of have the multi user picker in the form, with the Schema.types.array but then in the post message instead tagging the users it just show @["U03J5Q2Q1QS","U05767DQVSR","U0310QRTYHK"]
any tip please? it would be appreciated
The text was updated successfully, but these errors were encountered:
Hey @NPimenta86 👋 This is an interesting question! Glad to know you're collecting an array of user IDs already, but formatting this for a message will require a bit of custom logic.
Mapping these user IDs within the workflow won't work since a workflow is a static set of steps with inputs mapped between steps using templates. Meaning logic can't exist here...
{
"id": "2",
"function_id": "slack#/functions/send_message",
"inputs": {
"channel_id": "{{steps.0.fields.kudo_channel}}",
"message": "*Hey \u003c@{{steps.0.fields.doer_of_good_deeds}}\u003e!* Someone wanted to share some kind words with you :otter:\n\u003e {{steps.0.fields.kudo_message}}\n\u003c{{steps.1.URL}}\u003e"
}
}
Instead, I'd approach this by formatting either a list of users or the entire message from a custom function - perhaps the FindGIFFunction handler.
This output formatted string could then be used as input to the following SendMessage step and should all work!
Hey all, sorry, this is not really a issue...
I tweaked this code, and instead of a single-user picker I need to use a multi-user picker, but can't figure out how...
I've been able to kind of have the multi user picker in the form, with the
Schema.types.array
but then in the post message instead tagging the users it just show@["U03J5Q2Q1QS","U05767DQVSR","U0310QRTYHK"]
any tip please? it would be appreciated
The text was updated successfully, but these errors were encountered: