[LIMITATION] Workflow Builder does not support `Schema.slack.types.block`

[mcsescott]

If I am reading the documentation correctly, we can use blocks in a custom function when building a workflow step by using the type Schema.slack.types.blocks.

I can add that to my custom function in the input section with no issue, but it puts up a rich text block in my workflow step.

How can we specify the blocks to use/add to our custom workflow step? I would like to add custom blocks (labels, for instance) to my workflow step when it is being configured in Workflow Builder. I tried to add a block parameter, but received an error.

> Error: The provided manifest file does not validate against schema. Consult the additional errors field to locate specific issues (invalid_manifest)

Error Details:

1: Unexpected schema encountered for `slack#/types/blocks` type: invalid additional property: blocks - {"type":"additional_properties","got":"blocks"} (failed_constraint)
Source: /functions/my_function/input_parameters/blocky

[filmaj]

Unfortunately support for the generic blocks type as a step within workflow builder isn't great right now.

I will raise this with the workflow builder team in the hopes that we can get better rendering / UI support for that type prioritized.

[FallingReign]

Are there any updates on support for this? If not, what workaround would you suggest?

[filmaj]

@FallingReign unfortunately no update on this issue at this time as the company has no prioritized this functionality. I have raised this internally a few times, but please email feedback@slack.com to add your voice to this feature request.

[mcsescott]

Thanks @filmaj

This is a slightly different issue, though. #233 is about adding blocks into the modal of a custom function (custom step), and #301 is about outputting that type as a variable in subsequent steps.

[filmaj]

That's a good point @mcsescott , however for the purposes of tracking BOTH of these features, this one issue should be sufficient. Whether the custom function outputs or takes as inputs a blocks type, for workflow builder the result is the same: it does not support this type at all, so support is not there. My assumption is that if/when we land support for blocks in workflow builder, both inputs and outputs would be handled and resolved.

If I'm misunderstanding, please let me know. Ultimately, if you wish to re-open #301, feel free to do so - we can track both issues separately if you wish.

[omurilo]

have a news in support of Schema.types.blocks on custom functions inputs?