The check that runs
whether or not anyone asks.
A chat assistant answers when someone types. Droblet Agent runs when the clock or an event says so: every Monday at 07:00, check inbound shipments for a missing certificate of origin; when a new case arrives, check its documents agree. It reports what it found, and if it keeps failing it switches itself off and tells you.
Cron
Or interval schedules
Events
Triggered runs on new cases and extractions
5
Consecutive failures before a trigger disables itself
Proactive, not reactive
Most of the work that goes wrong in a customs or documents team goes wrong quietly. A certificate that never arrived. A packing list whose weight does not match the invoice. A declaration drafted on Friday and never approved. Nobody asked about it, so nobody found out until the shipment was held.
Droblet Agent is the part of the platform that asks on your behalf. A trigger is a task, a schedule and an owner. When it fires, an agent session runs the task against your live data, using the same tools and the same permissions you have, and writes a report: what it checked, what it found, what it could not do. Reports accumulate, so the Monday check also tells you whether the problem it found last week is still open.
What it does
Scheduled runs
Cron or interval schedules. A missed window (the server was down) is scheduled forward, not replayed, so a restart does not fire a week of checks at once.
Triggered runs
Fire on an event: a new document case, an extraction completing, a declaration changing state.
Same tools, same limits
An agent run uses the same tools the MCP server exposes, as the owner of the trigger. It cannot see or do more than they can, and it cannot file a declaration.
Reports you can read
Every run records what it checked, what it found and how long it took. Failures are reports too, with the reason.
Self-disabling
Five consecutive failures disable the trigger and flag it. A broken check that silently keeps running is worse than one that stops and says so.
Managed from the app or MCP
Create and review schedules in Droblet, or from Claude with schedule_check, list_schedules and list_schedule_runs.
Checks our clients run
Missing documents
Every morning: list inbound shipments arriving in the next five days whose case has no certificate of origin or no packing list.
Documents that disagree
On every new case: compare the invoice, packing list and transport document and flag weights, quantities or parties that differ.
Drafts waiting
Each afternoon: declarations drafted more than a day ago and not yet approved, by owner.
Common questions
No. It can draft and check them and tell you they are waiting. Filing needs a person to approve in Droblet.
The failure is recorded with its reason and the next run is scheduled as normal. After five consecutive failures the trigger disables itself and is flagged for a person to look at.
Into Droblet, against the trigger. From there they can be delivered like any other output: webhook, email, or read from Claude with list_schedule_runs.
Set up your first Monday check
Tell us the question you ask every week. We will have it running before the demo ends.