Finance & ops

What is waiting on you, and who is sitting on the rest.

#opspublic channel2 tool calls

Open approvals split into what is waiting on the person asking and what is waiting on somebody else, with the second list grouped by whose desk it is on and how long it has been there.

Try it now Deploy it yourself Access requests

opsthread

Mei3:05 PM

@attest_tag what's waiting on me and what's waiting on someone else?

attest_tagApp3:06 PM

clickup_search_tasks · list Approvals · status ≠ done · 10 tasks
run_js · assignee split, age in days · 3 mine, 7 theirs

Waiting on you (3)

Northwind PO — £24,000, 9 days. The oldest thing with your name on it.
Contractor renewal, 4 days. Security questionnaire sign-off, 1 day.

Waiting on someone else (7) — Dan has 4 (two over a fortnight), Priya 2, Sam 1. Say the word and I’ll draft each of them a nudge in the thread; nothing goes out on its own.

google/gemini-flash11k in410 out$0.0058Configure

Names, figures, repositories and customers are changed; token counts and cost are illustrative. The ask, and the shape of the answer, are as they were.

How the turn went

One list, split by whose move it is, and an offer that stops short of acting.

01
The split is the whole answer
A board of ten open items is not information. Two lists — mine, and everyone else’s, with a name on each line — is what the person asking actually wanted, and the ordering by age is what makes the first line the right one to do next.
02
The board is the channel's, not a person's
The project connection is attached to the channel with a token the channel shares, so everyone in it sees the same board. That is the opposite of the mail cases next door, and deliberately: a board is a shared record, a mailbox is not.
03
It offers the nudge; it does not send it
Posting seven nudges is seven writes, and doing them unasked is how a helpful tool becomes one people mute. The offer sits in the thread until somebody takes it.

What it needs

The setup, in the console.

Connection

The ClickUp preset attached to the channel, with the list the approvals live in. Linear, Jira and Asana answer the same ask from their own presets.

Credential

A ClickUp API token, sealed in the database. Reads run; creating or changing a task is a held write.

Writes policy

confirm. This turn made none — the nudges would each be one.

What it will not do

Enforced outside the model.

It cannot approve anything on your behalf. Reading who owes what is a read; the approval is a person's.
A task's description is quoted material. An instruction written into a ticket is reported, not followed.

Try it

Say it in a channel it is in.

The sentence as it was typed. It works in any channel the bot has been invited to that carries the connection above — no command syntax, no form, and follow-ups in the thread need no mention.

@attest_tag what's waiting on me and what's waiting on someone else?

clickup_search_tasks
run_js

The month-end chores, done before the meeting.

Bring the channel this would live in.

Sign up, connect the service above in one channel, and type this sentence yourself — or run the same binary on your own infrastructure.

Try it now Deploy it yourself

All solutions