Cloud Storage Object Watch with Claude Code
Judging a four in the morning partner drop means holding several things at once: this object's path, name and size, what the same prefix held on the four previous mornings, which parts have landed so far, and whether the manifest that closes the delivery has appeared. Claude Code gathers all of that before deciding anything, which is what stops a delivery still in progress being reported as a broken one.
Watch it work before it's live
Run a staged conversation — no account needed. The agent handles it for real while a simulated world answers its tool calls; nothing touches real accounts, and nothing is actually sent.
partners/nordfrakt/2026-08-12/deliveries_0004.parquet
412 MB, written 04:07 UTC by the partner service account. Parts 0001 to 0003 landed between 04:02 and 04:06 at 380 to 430 MB each. The same prefix on the four previous days held six parts and a _MANIFEST file. No manifest has appeared for today.
Set up in minutes
Using this template drops you into a guided setup. It asks exactly this, nothing else:
Connect Google Cloud Storage
One sign-in. The agent acts through your account, scoped to what this template uses.
Connect Slack
One sign-in. The agent acts through your account, scoped to what this template uses.
Bucket rules
What a correct delivery looks like in this bucket - the prefixes and naming shape you expect, who sends what and roughly when, how large a normal drop is, how many pieces a full one contains or which manifest closes it, and who to name in Slack when a delivery goes wrong.
Runs on Claude Code
Preselected for this page — connect your Claude Code account during setup, or switch to NoClick's built-in models with one click.
Watch it handle a test run
A staged conversation against a simulated world — then it’s live.
Why Claude Code for this agent
Four mornings of history first
412 MB is neither large nor small until you know the same path carried 380 to 430 MB on each of the last four nights. Late and small only exist relative to normal.
Partial is not broken
Part four of six at 04:07 is a drop in progress. Saying so, and naming which pieces are still absent, is a different message from announcing a failure.
Before you fork
The drop is due at four and lands at five. When do we hear?
When the object actually arrives, because the trigger is the write itself rather than a clock. A delivery that never lands at all produces no run, which is the honest limit of an event driven watch, so teams who need a missing drop announced add a scheduled check on the manifest alongside this one.
Run it with a different agent
Put Cloud Storage Object Watch to work on Claude Code
Free to start. Guided setup, a test run against staged conversations, and it's live.