Event layer for agents.
Your users already have email, calendars, tickets, and half a dozen tools making noise. Watchline filters those streams and wakes your agent only when the event matches what the user asked for.
Matched watch
Urgent customer emails that need action today
One fresh event, not another polling run.
Signal gate
Let the event stream stay noisy. Wake the agent only at the line.
Timers make agents check the same empty inbox again and again. Watchline sits before the agent turn, so the expensive reasoning starts after an event has already passed the user's filter.
Cheaper proactive runs
Stop paying a general agent to ask, "anything new?" every minute. Deliver the matched event instead.
Setup inside the agent
The agent can register the watch during conversation. Watchline asks for missing details or app auth only when it needs them.
OpenClaw pull delivery
The OpenClaw plugin adds watch tools and pulls matched events into the local workspace.
How it works
A watch turns user intent into delivery.
Register intent
Your agent or app sends what the user wants to hear about. Watchline asks for concrete details if the request is too vague.
Connect sources
Watchline returns app connection links when a user needs to authorize an event source.
Deliver matches
Matched events go to a signed webhook or a pull channel for local runtimes like OpenClaw.
Hosted MCP
Give agents tools to create, continue, list, pause, resume, and delete watches before you build a custom setup screen.
Webhook delivery
Push signed matched events into a hosted agent harness you already run.
OpenClaw plugin
Install a first-party plugin that adds watch tools and pull delivery to a local OpenClaw workspace.
Developer shape
One call starts the setup. If the request is missing a detail or an app connection, Watchline says so in the response.
await watchline.watches.create({
channel_id: "ch_123",
user_id: "user_123",
intent: "urgent customer emails that need action today"
});Is Watchline an agent framework?
No. Watchline is the event layer around the agent. Your agent stays in OpenClaw, Cursor, a custom harness, or your own backend.
Do agents create watches directly?
They can. The hosted MCP server and OpenClaw plugin expose watch tools so an agent can register a future event intent during conversation.
Do I need webhooks?
Use webhooks for hosted agent backends. Use pull delivery when the agent runs locally and should not expose a public URL.