put a new row in the slack list you chose

rescue the repair request before channel scroll buries it. a bot adds a slack list item with starting values, copies an existing row or creates a subtask.

by the dusk bot team · checked 12 november 2026 · how we made this

give the list link and columns to fill. ask for a row preview before creation: this counts as a write, so the sending setting won't pause it for you.

pixel art: a cyan pixel bot and a sky blue pixel bot beside the Slack mark on a white tile, a notebook and a big button, on a lilac hill in front of little green islands on a lake, one saying "new list row ready"

what it does

a list row keeps a request out of channel scroll. paste the list link and say what belongs in each column. the bot creates the row with those starting values. this action doesn't post a channel message.

for a subtask, name its parent row. for a copy, name the original and the values to replace. the connection handles slack's rich text for ordinary text values.

when you would use it

capture the repair request. add the facilities problem and the location you gave.
split a packing job. create a subtask beneath the existing event-preparation row.
reuse the setup structure. copy a checklist row and replace its title for the new session.

try it

paste this into a chat with your bot

every weekday at 15:25, read today's messages in the alderwick hall facilities-intake slack channel. use requests marked ready for list there.

compare them with the repairs list and skip requests already represented. show proposed rows here before adding anything. after i approve, create those rows and report which ones succeeded. stop on an uncertain match. leave unknown owners blank. never copy yesterday's requests or post a channel message.

when: weekdays at 15:25
needs: slack read and write; channel and list reads plus list creation; connect an account that can edit the list

what comes back looks like this (an example)

alderwick hall repairs preview
request: replace meeting room door sign
location: west corridor
owner: blank

row ready for review.

set it up

connect an account that can edit the list. give this bot slack read and write.
map one request. paste the list link, name the columns and ask for a row preview only.
leave gaps visible. say which fields may stay blank and which missing details should stop the job.
open one new row. read its cells before scheduling daily intake.

what it needs from you

input	required	what it is
`list_id`	yes	ID of the Slack List to add the item (row) to, e.g.
`initial_fields`	no	Initial cell values for the new row.
`parent_item_id`	no	ID of an existing item (row) to attach the new row to as a subtask.
`duplicated_item_id`	no	ID of an existing item (row) in this List to copy.

from composio's catalog for Slack (action SLACK_CREATE_SLACK_LIST_ITEM, read 12 november 2026⁴). your bot fills these in from what you tell it.

how dusk bot handles it

dusk bot counts Create Slack List item 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: lists:write.

where it stops

the account needs list access. channel membership alone doesn't promise it can edit this list.
values must fit their columns. dates belong in date columns. preview the mapping before creation.
duplicates still become rows. compare today's marked requests with existing entries before adding more.

try it in 2 minutes

paste the slack list link
describe one request and its column values
ask for a row preview without creation
confirm it, then read the saved cells

mistakes people make

inventing an owner to fill the row

leave ownership blank or ask. an empty cell beats assigning the wrong person.

copying a row with old values intact

name the values to replace. a new title alone can leave yesterday's details behind.

questions

can it add a subtask instead of a top-level row?

yes, name the parent row. the bot can attach the new entry beneath it.

does adding a list row count as sending a slack message?

it counts as a write. ask for a review in the routine itself; the sending setting does not pause list creation.

sources

dusk bot docs: files and apps
dusk bot docs: routines
dusk bot docs: a bot's computer
composio, Slack toolkit (catalog version 20261101_00), checked 12 november 2026

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].