Use cases

Five setups people actually run

Same four flows, wired differently. Each case below shows the sources it watches, what the flow does in order, and a real input with the post that came out of it.

Case 01Politics

Parliament coverage in five languages, no translator on call

Five parliamentary press rooms and two wires are watched continuously. When a vote lands, the item is rewritten to your house style and localised before your editor has finished reading it.

Flows used
ScrapingMultilangPost
01Watch7 official sources · RSS and press-room pages, polled every 40s
02FilterOnly items matching your bill list — no party press releases
03LocaliseES source → EN, DE, FR, PT with your political glossary locked
04QueueEditor approves once; all five channels publish in their own order
Inputcongreso.es · press room · 14:02

El Congreso aprueba la ley de vivienda con 178 votos a favor y 172 en contra.

@brief_enEN

Spain’s lower house passes the housing bill, 178–172. Rent caps in stressed areas take effect in January.

@brief_deDE

Spaniens Abgeordnetenhaus verabschiedet das Wohnungsgesetz mit 178 zu 172 Stimmen.

14:02 → 14:03 · 5 languages, 1 approval
Case 02Sports transfers

Transfer rumours, ranked by how many sources agree

Transfer news is a credibility problem, not a speed problem. Channelflow collects the same claim from every source you trust and only posts once enough of them agree.

Flows used
ScrapingMonitoringPost
01Collect14 sources — club sites, tier-1 reporters, league feeds
02ClusterThe same claim from different outlets is merged into one story
03ScoreConfidence rises with source tier and count, never with volume
04GateBelow your threshold it waits in the queue instead of publishing
Input4 sources agreed · 09:41

Medical scheduled for Thursday · fee reported €38m + €4m add-ons

@transferdeskEN

Confidence 4/5 — medical set for Thursday. Fee reported at €38m plus €4m in add-ons. Club has not confirmed.

2 rumours published, 11 held this week
Case 03Crypto

Listings, unlocks and exploits — before the group chats

Exchange announcement pages, governance forums and unlock calendars are read on a schedule. Price moves alone never trigger a post — a source does.

Flows used
ScrapingMonitoringPost
01WatchExchange announcements, forum proposals, token unlock calendars
02VerifyContract address and announcement URL must both be present
03FrameNumbers first: amount, chain, date. No adjectives, no price calls
04PostInstant to the alerts channel, digest at 18:00 to the main one
Inputexchange announcement · 07:12

USDC/ARB spot pair opens for trading 24 Sep, 08:00 UTC

@flow_alertsEN

New spot pair: USDC/ARB opens 24 Sep 08:00 UTC. Arbitrum One · announcement linked. Not financial advice.

Alerts channel: 6 min ahead of aggregators
Case 04Private blog

One long draft, a week of posts in your own voice

For a one-person channel. You paste the draft, Channelflow splits it into the parts your readers actually finish and keeps the voice you wrote the prompt for.

Flows used
PostMultilang
01PasteA 1 400-word draft, notes and links included
02RewriteYour prompt: second person, no em dashes, one idea per post
03SplitFour posts plus a pinned summary, sequenced across the week
04ReviewEvery post shown side by side with your original sentence
Inputdraft.md · 1 412 words

…the reason batching fails for small channels is that it hides the feedback loop you actually need…

@notesYou

Batching hides the feedback you need. If you post weekly you learn weekly. Three posts a week is not more work — it is more information.

1 draft → 4 posts + pinned summary
Case 05Claim monitoring

Every claim about one public figure, sorted by whether it checks out

Monitoring never publishes. You describe in plain words what to watch for and it reports back — here, everything said about a named politician, split into confirmed, single-source and contradicted.

Flows used
Monitoring
01Prompt“Anything attributed to Donald Trump about tariffs — flag if only one source”
02GatherWires, official transcripts and the outlets you listed
03CompareQuote matched against the transcript where one exists
04ReportDigest to you, never to a channel — Monitoring has no publish rights
Inputmonitoring digest · 6 items · 08:00

2 confirmed against transcript · 3 single-source · 1 contradicted by the transcript

you onlyDigest

Contradicted: the 40% figure does not appear in the 21 Sep transcript. Two outlets carry it, both citing each other.

0 posts published — reporting only

None of these is your setup?

Every case above is the same four flows with a different prompt and source list. Tell us what you watch and we will say which flows cover it — or that we do not.