Reply to Slack Command

slack/reply-to-command — Reply to the Slack slash command that started this workflow.

Where it appears

The Reply to Slack Command block lives in the Integrations group of the Workflow Builder.

Field	Type	Required	Default	Description
`text`	text (multi-line, supports references)	No	—	Reply text. Supports Slack mrkdwn. When you also send blocks, this is the notification and screen-reader fallback. Use literal text or <StepName.field>.
`responseType`	select	No	`ephemeral`	Who sees the reply. Slack posts in-channel replies as a normal message in the channel the command was run in. Options: `ephemeral`, `in_channel`.
`blocks`	code	No	—	Optional Block Kit blocks for a richer layout, as a JSON array (at most 50). Design them in Slack's Block Kit Builder.
`replaceOriginal`	toggle	No	`false`	Replace this workflow's previous reply to the command instead of adding a new message. Slack never replaces the user's own command.
`responseUrl`	text (supports references)	No	—	Leave blank to reply to the command that started this workflow. A response URL accepts at most 5 replies within 30 minutes of the command.

Inputs are the configurable fields above. The block produces these outputs:

Outputs

Reference an output downstream with <Reply To Slack Command.field>.

Name	Type	Description
`success`	boolean	Whether Slack accepted the reply
`responseType`	string	Visibility the reply was sent with

A minimal configuration for this block:

{
  "type": "slack/reply-to-command",
  "config": {
    "responseType": "ephemeral",
    "replaceOriginal": false
  }
}