K
Docs
API Reference→Pieces→Check Later
🔭

Check Later

clock.check_laterThe ClocktowerTime

Looks for a waiting ⏳ Do It Later by its tag. Found tells you when it's due — {{pending.left}} (like 2h 5m), {{pending.relative}} (a live Discord countdown) — and how many matched. Missing means nothing with that tag is waiting.

When to use this
  • →“Tags that start with it” counts every match — {{pending.count}} — and shows the soonest

On the canvas

This is what Check Later looks like when you place it on your flow. Each field below is something you configure in the inspector panel.

🔭
Check Later
clock.check_later
Time
tagrequired
e.g. remind:{{input.user.id}}
match
select…
asrequired
pending
found
missing

Config fields

FieldTypeReqWhat it does
tag
e.g. remind:{{input.user.id}}
textyesTag 🏷️
matchselect—Match 🔍
as
pending
textyesSave it as ✨

Sparks this piece adds

After this piece runs, these values are available as sparks in every node downstream.

{{pending.at}}numberWhen it's due, as a Unix time
{{pending.left}}stringTime left, like 2h 5m
{{pending.seconds}}numberSeconds left
{{pending.relative}}stringA live Discord countdown
{{pending.tag}}stringIts tag
{{pending.count}}numberHow many matched

Output ports

foundOne is waiting — {{pending.left}} says how long
missingNothing with that tag is waiting
📐

In TypeScript, this would be…

Not something you need to write — just a look at what Kitcord does for you.

TypeScript
const row = await db.get("SELECT due_at FROM later WHERE tag = ?", [`remind:${userId}`]);
if (row) {
  const left = row.due_at - Date.now(); // {{pending.left}} — Found ✓
} else {
  // Missing ∅
}