dusk botqueue a slack message for later
write it on friday. let slack deliver it when the monday shift starts. a bot can queue a channel message, direct message or thread reply for a future time.
give the destination, wording, time and time zone. once queued, slack posts it later without another yes, so review the note before scheduling.
schedule message, in plain words
your working day need not become someone else’s notification. slack accepts future messages up to 120 days ahead. give your local time zone; the bot handles the conversion. delivery must still be in the future when it queues.
the connected account must belong to the destination channel. for a thread, link the original message. layout attachments mean formatting here; document uploads need another action.
a routine to copy
paste this into a chat with your bot
every friday at 14:40, prepare this note for #larkvale-studio: "please put monday’s equipment requests in the booking list".
- show the text and channel here
- propose delivery next monday at 08:45 europe/london
- wait for my agreement before scheduling
after queueing, report the confirmed delivery time here. if the result is unclear, look for the queued note before trying again. never queue a second copy blindly.- when
- fridays at 14:40; monday delivery follows your review
- needs
- slack connected with read and write; membership in #larkvale-studio
what comes back looks like this (an example)
larkvale studio reminder
channel: #larkvale-studio
delivery: monday, 08:45 europe/london
preview ready: the booking-list reminder will enter the queue after your agreement.good jobs for it
- respect a later shift. queue a reminder for when colleagues start.
- prepare workshop instructions. schedule the reviewed text in the session thread.
- time an office closure notice. write it during your working day for delivery later.
before it runs
dusk bot counts Schedule message as a change: it alters something in Slack, and the sending setting does not cover it. a bot you allow only to read can never call it.
the permissions Slack asks for to run it: chat:write.
how to start
- allow scheduling deliberately. connect slack with read and write for this bot.
- name the destination. give the channel and local time zone. link the parent message for a thread reply.
- require a pause. say "wait for my agreement before scheduling"; send approval does not cover queueing.
- open the queued note. confirm its delivery time before setting a weekly reminder.
limits worth knowing
- past times fail. so do dates beyond 120 days ahead.
- private channels still need membership. a name does not grant access.
- link previews may still appear. avoid links whose preview could reveal private details.
the details it works from
| input | required | what it is |
|---|---|---|
text | no | This sends raw text only, use markdown_text field for formatting. |
parse | no | Message text treatment: `full` for special formatting, `none` otherwise (default). |
channel | no | Channel, private group, or DM channel ID (e.g., C1234567890) or name (e.g., #general) to send the message to. |
post_at | no | Unix EPOCH timestamp (integer seconds since 1970-01-01 00:00:00 UTC) for the future message send time. |
thread_ts | no | Timestamp of the parent message for the scheduled message to be a thread reply. |
attachments | no | This is Slack's legacy 'secondary attachments' field for adding rich formatting elements like colored sidebars, structured fields, and author info. |
from composio's catalog for Slack (action SLACK_SCHEDULE_MESSAGE, read 12 november 20264). your bot fills these in from what you tell it.
try it in 2 minutes
- choose one channel you belong to
- write a short note and tomorrow’s local delivery time
- ask the bot to preview it without queueing
- read the text, channel and time zone before allowing it
before the note enters the queue
- the destination is the right channel or thread
- the text is ready for other people to read
- the local time and time zone are explicit
- the bot will look for a queued note after an unclear result before retrying
mistakes people make
trusting "ask every time" for scheduled notes
add a wait-for-agreement instruction. scheduling does not use send approval.
saying "9 tomorrow" across time zones
state the time zone and compare it with the confirmed delivery time.
questions
will send approval stop it from scheduling?
no, scheduling counts as a write. tell the bot to wait for your agreement before it queues anything.
can it attach a document to the scheduled note?
not through this action. it schedules message content and layout. uploading a file takes a separate action.
sources
read next
an end-of-day digest of the slack channels you chooseread the decisions, then follow the thread.
a slack assistant that finds the decision in the threadcatch up without losing the thread.
claude code from telegram, discord or slackthree different reasons to connect a chat.
let a bot acknowledge a slack message with a reactionan acknowledgement with an agreed meaning.
turn a request into a slack remindera reminder with a clear recipient.
put a new row in the slack list you choseone request, placed in its list.
drafted with ai help from the dusk bot docs and the sources listed on this page, then checked against them. if something here is wrong or out of date, write to [email protected].