POST /chat.scheduleMessage

Schedules a message to be sent to a channel.

Servers

https://slack.com/api

Request headers

Name	Type	Required	Description
`Content-Type`	String	Yes	The media type of the request body. Default value: "application/x-www-form-urlencoded"
`token`	String	No	Authentication token. Requires scope: `chat:write`

Request body fields

Name	Type	Required	Description
`parse`	String	No	Change how messages are treated. Defaults to `none`. See chat.postMessage.
`channel`	String	No	Channel, private group, or DM channel to send message to. Can be an encoded ID, or a name. See below for more details.
`reply_broadcast`	Boolean	No	Used in conjunction with `thread_ts` and indicates whether reply should be made visible to everyone in the channel or conversation. Defaults to `false`.
`text`	String	No	How this field works and whether it is required depends on other fields you use in your API call. See below for more detail.
`unfurl_links`	Boolean	No	Pass true to enable unfurling of primarily text-based content.
`as_user`	Boolean	No	Pass true to post the message as the authed user, instead of as a bot. Defaults to false. See chat.postMessage.
`attachments`	String	No	A JSON-based array of structured attachments, presented as a URL-encoded string.
`link_names`	Boolean	No	Find and link channel names and usernames.
`post_at`	String	No	Unix EPOCH timestamp of time in future to send the message.
`blocks`	String	No	A JSON-based array of structured blocks, presented as a URL-encoded string.
`thread_ts`	Number	No	Provide another message's `ts` value to make this message a reply. Avoid using a reply's `ts` value; use its parent instead.
`unfurl_media`	Boolean	No	Pass false to disable unfurling of media content.

How to start integrating

Add HTTP Task to your workflow definition.
Search for the API you want to integrate with and click on the name.
- This loads the API reference documentation and prepares the Http request settings.
Click Test request to test run your request to the API and see the API's response.