dusk bot
integrationsclickup

dusk botintegrations

a clickup bot that catches the timer still running

catch the timer you left running before its hours reach a client invoice. a clickup bot can read your time entries, separate active timers from finished work and flag tasks missing a client code.

by the dusk bot team · checked · how we made this

ask for the task id beside each exception. you can fix the entry where the work happened.

pixel art: a lime pixel bot and a cyan pixel bot beside a tile saying ClickUp and an alarm clock and a calendar, on a sandy path in front of snowy hills and green fields, one saying "is that timer running"

what a bot can do in ClickUp

start from the view or list that defines the job. your delivery view and a task's home list can contain different work. time entries belong to a workspace and a date range. give the bot those boundaries before asking for a total.

actiondusk bot treats it aswhat you would use it for
Get time entries within a date rangereadread your own entries for the billing week
Get running time entryreadsee whether the timer still runs on an entry you expected to finish
Get view tasksreadread the tasks visible under the delivery view's filters
Get taskreadopen one task to see its details
Get accessible custom fieldsreadidentify the field the team uses for its client code
Get tasksreadreview open tasks whose home is the intake list
Get task s time in statusreadfind time spent in review when the workspace supports it

composio, the connection service behind dusk bot's apps, lists 165 ClickUp actions (version 20261116_00, read 20 november 20263). dusk bot treats 65 as reads, 9 as sends and 91 as changes.

only actions starting with a read word (get, list, search) count as reads, so a read-only bot can't call the rest. a send reaches people or moves money, like create chat message, and waits for your Allow unless you set a daily amount.

connect ClickUp

  1. open Connected apps in the sidebar.
  2. pick ClickUp and sign in on ClickUp's own page, so your password goes to them and never to a bot.
  3. choose which bots may use it, and whether each may only read or may also change things. your bookkeeper doesn't need your ClickUp.
  4. ask in plain words. reading and drafting happen freely; sending asks you first.

give the bot your workspace id and the delivery view id. add the home list for intake and the exact name of your client code field. allow these reads. try asking about one entry you recognize so you can confirm the date range and whose time it reads.

routines to copy

use the same week boundaries as billing. tell the bot which day starts your week, which time zone to use and what your review status means. these jobs return exceptions in chat for the person who can resolve them.

friday timesheet close

each friday at 5, read my clickup time entries for this billing week. total finished entries by task. put entries with a negative duration on a separate running timer line. leave them out of totals. give me task ids for corrections and leave the timers alone.

fridays at 17:00 · finished time by task and any timer still running

missing client codes

each morning at 9, read open tasks whose home is my intake list. use the client code field from that list's field definitions. bring me tasks with no value. show the task id and title. if the field itself is missing, tell me instead of flagging every task.

daily at 09:00 · uncoded briefs for the intake lead

review queue aging

each tuesday at 3, read every page of my delivery view. for tasks currently in review, look up time in that status. list tasks with more than two days in review, longest first. flag unavailable durations. don't use the task creation date as a substitute.

tuesdays at 15:00 · review tasks to discuss with their recorded time in status

what it asks you first

a timesheet review can finish without stopping a timer. restrict the bot to reading entries and tasks. stopping time or filling in a client code changes clickup. if you enable either write, add “ask me before you change anything” to that job.

what it cannot do

  • get every task visible in a view by reading one home list. the list action returns tasks whose home is that list. use the view action when the view defines the workload.
  • read time in status everywhere. the workspace needs the total time in status clickapp enabled. otherwise leave the duration unknown.
  • decide what you can bill from a timer. a finished entry shows recorded time. the client agreement decides whether the time belongs on the invoice.

make the exception easy to fix

put the task id beside the suspect hours. a busy designer can log time against two tasks with nearly identical names. if you already know which timer needs stopping, open it directly. the bot helps when the mistake could sit anywhere in the week's entries.

what it looks like

an example before a studio closes its timesheets.

before

helena has a finished layout entry and an active timer on packaging revisions. both tasks belong to the same client.

after the bot

layout: 45 minutes finished.
packaging revisions: timer running, excluded. open this entry before totaling the client's hours.

an illustration with made-up names and numbers.

questions

why did the bot leave a negative duration out of my total?

that value marks an active timer. inspect the running entry and decide when the work ended. subtracting its duration would distort the total.

will the delivery review respect my view filters?

yes, when it reads the view itself. give it the view id and ask it to continue to the last page. name the status you consider review.

sources

  1. dusk bot docs: connected apps
  2. dusk bot docs: routines
  3. composio, ClickUp toolkit (catalog version 20261116_00), checked 20 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].