Newswire
Wires arrive as drafts, already sorted.
Connect your feeds. Reuters, TT, AP, anything else. Stories appear as Draft documents, classified by the AI categoriser on the way in.
Why
Newsroom triage is a tax on attention.
Dotvoid pays it for you. By the time an editor opens the queue, each item already has a desk, a category, and a working headline that can be rewritten in seconds. You're editing, not triaging.
The same workflow engine that drives a feature article drives a wire item. A “promote to homepage” transition fires the same role gates, confirm prompts, and signed webhooks regardless of origin. The wire feed isn't a sidecar product. It's the same product, with a different intake.
Pipeline
Feed in, draft out, workflow as usual.
Configure a feed and Dotvoid pulls on the cadence you set. Each item becomes a Draft document on the assigned desk. The AI categoriser writes to meta.category, meta.desk, and meta.tags using the same inputPath mechanism every other AI operation uses.
From there, the workflow takes over. Move the doc through your normal states; signed webhooks fan out to your downstream systems on the events you care about.
- ConnectURL, auth, polling interval - per feed.
- IntakeItems land as Draft documents on the right desk.
- CategoriseAI runs on arrival, before a human sees it.
- EditPick from the queue and run the normal workflow.
- Shipusable snapshots ride out on signed webhooks.
Categoriser
AI sorts wires. Editors edit them.
The categoriser is one AI operation among many. It runs on intake, writes to inputPath fields, and snapshots before it does. You can swap the model, tune the prompt, or run two categorisers in parallel and prefer the one with higher confidence. The whole thing is configurable in the same UI as every other AI operation.
Because the categoriser is just an AI operation, you can also disable it and route raw wires straight to a human triage desk. The choice is yours per feed, not per product tier.
Next step