Back to Blog
Guide

Slack Datepicker, Timepicker and Datetimepicker: Payloads and Time Zones

We posted Slack's datepicker, timepicker and datetimepicker in a message and a modal, picked values and logged every payload. The datetimepicker returns a Unix timestamp; the timepicker returns a bare HH:mm with no zone unless you set one.

Slack Green Team
October 4, 2026
October 4, 2026
3 min read
Share:
slack api
block kit

Slack has three Block Kit pickers. The datepicker sends a date as YYYY-MM-DD, the timepicker sends a time as HH:mm, and the datetimepicker sends a Unix timestamp in seconds. Only the timestamp is a fixed moment; the other two mean nothing until you know whose time zone they are in. We tested all three on 4 October 2026 with a throwaway app in a free-plan workspace, in a message and in a modal, from a Slack account set to Seoul time. A Socket Mode listener logged each payload.

The three pickers in a message

We posted one actions block with four elements: a datepicker, a timepicker, a timepicker with "timezone": "America/New_York" and a datetimepicker:

[
  {"type": "datepicker", "action_id": "p_date", "initial_date": "2026-10-05"},
  {"type": "timepicker", "action_id": "p_time", "initial_time": "09:30"},
  {"type": "timepicker", "action_id": "p_time_tz", "initial_time": "09:30", "timezone": "America/New_York"},
  {"type": "datetimepicker", "action_id": "p_dt", "initial_date_time": 1791190800}
]
The pickers in Slack's web app: a date field showing Tomorrow, a time field at 9:30 AM, a second time field at 9:30 AM labelled Time zone: Eastern Time (US and Canada), and a date and time pair showing Tomorrow, 6:00 PM, Time zone: Seoul

Slack wrote the initial date as "Tomorrow" because we posted on 4 October. The datetimepicker's 1791190800 is 09:00 UTC on 5 October, and Slack showed it as 6:00 PM with the label "Time zone: Seoul", the viewer's own zone. The timepicker with a timezone got a "Time zone: Eastern Time (US and Canada)" label; the plain timepicker got none.

What each pick sends

Each pick sent one block_actions payload. The actions entries we logged:

ElementWhat we pickedValue in the payload
datepickerOctober 12 in the calendar"selected_date": "2026-10-12"
timepicker2:00 PM from the list"selected_time": "14:00"
timepicker with timezonetyped 4:17 PM"selected_time": "16:17", "timezone": "America/New_York"
datetimepickertyped 8:45 PM"selected_date_time": 1791200700

Each entry also carried its initial_ value, so you can tell a changed field from an untouched one. The drop-down lists whole hours only, but typing any minute worked.

The datetimepicker value is 11:45 UTC, which is 8:45 PM in Seoul, so the timestamp already accounts for the person's zone. The plain timepicker's "14:00" has no zone in the payload at all. To turn it into a moment, look up the clicking user's tz with users.info (ours was Asia/Seoul, offset 32,400 seconds), or set timezone on the element so you decide the zone. Our Slack timezone converter shows the same hour across zones, and the Slack timestamp tool turns a datetimepicker value into Slack's date format.

Picks are not saved in the message. After we reloaded the page, every picker showed its initial value again. If the choice should stick, store it and chat.update the message with a new initial_ value, the same pattern our checkbox test needed.

Never appear "away" on Slack again

Cloud-based. No downloads. Works 24/7 even when your laptop is off.

Format errors, and two dates Slack accepted

These initial_ values failed with invalid_blocks:

What we sentError
"initial_date": "10/05/2026"input must be a valid: date
"initial_date": "2026-10-05T09:00:00Z"input must be a valid: date
"initial_time": "09:30:00", "9:30 AM" or "24:00"input must match regex pattern (24-hour HH:mm, 00:00 to 23:59)
"timezone": "UTC+9"invalid IANA timezone
"initial_date_time": "2026-10-05T09:00"must provide an integer
"initial_date_time": 1791190800000 (milliseconds)value should be a unix timestamp in seconds

Two values passed the API check and then rendered wrong:

Two datepickers in Slack: the first is empty and reads Select a date, the second shows 03/02/2026

"2026-10-5", without the leading zero, posted fine and showed an empty picker. "2026-02-30" posted fine and showed March 2. Always zero-pad, and check the date is real before you post. "timezone": "EST" was also accepted and labelled Eastern Time.

Pickers in a modal

We opened a modal from an app shortcut with the three pickers in input blocks. Pressing Save with the date fields empty showed "Please complete this required field." under each one, and the app received nothing; the check runs in Slack's client. After we filled them in:

A Slack modal titled sglab pickers with Date October 20th, 2026, Time 9:30 AM, and Date and time October 21st, 2026 at 7:05 AM, Time zone: Seoul

The view_submission payload held the values under view.state.values:

{
  "d":  {"date": {"type": "datepicker", "selected_date": "2026-10-20"}},
  "t":  {"time": {"type": "timepicker", "selected_time": "09:30"}},
  "dt": {"dt": {"type": "datetimepicker", "selected_date_time": 1792533900}}
}

1792533900 is 22:05 UTC on 20 October, the moment 7:05 AM on 21 October is in Seoul. Typed dates were accepted in MM/DD/YYYY form and shown as "October 20th, 2026". Opening the modal needs a fresh trigger_id; ours expired with expired_trigger_id 6.9 seconds after the click, as described on our expired trigger ID page.

Always Active

Stop Jiggling Your Mouse.

Join hundreds of remote workers who never worry about their Slack status. Set it up once, stay green forever.

Related Articles

Developers

Slack private_metadata: Pass Data to a Modal (Tested Limit)

private_metadata is a hidden string on a modal view that Slack hands back in view_submission. We tested it on 18 November 2026: a JSON blob came back unchanged, and the limit is 3,000 characters, counted as characters, not bytes.

Slack Green Team
Developers

Slack Attachment Color: good, warning, danger and Hex Values, Tested

The color field of a Slack message attachment draws the bar on the left. We posted good, warning, danger, hex with and without #, a color name and an attachment holding blocks on 13 November 2026, and recorded what Slack stored and showed.

Slack Green Team
Developers

Slack Overflow Menu in Block Kit: Limits, Payload and Confirm, Tested

A Block Kit overflow menu takes 1 to 5 options, plain_text labels up to 75 characters and values up to 150. We posted each limit, clicked options in Slack and recorded the block_actions payload, the url option and the confirm dialog on 13 November 2026.

Slack Green Team