How to set up: industry news digest
- Step 1Fork the blueprint — Open this workflow and click Fork. The from-blueprint route copies the two-node chain (`rss-feed` → `notion-page-create`) into a private draft you own, snapshots it as version 1, and carries the `0 8 * * *` schedule across. Any signed-in account can fork it.
- Step 2Pair a runner — Both nodes are connector tools and run runner-only, so they execute on your paired runner — not in the browser and not on the JAD server. Pair a runner before you run, or the connector nodes have nowhere to execute.
- Step 3Set the feed URL — On the RSS node, set `url` to your feed. Optionally cap `limit` (default 50, max 500) and set `since` to an ISO date so only items newer than that timestamp come through — the cheapest way to avoid re-importing old posts.
- Step 4Store the Notion token and point the node at it — Create a Notion integration, share your target database with it, and store the secret on your runner as a credential. On the Notion node, set `databaseId` and set `credentialRef` to that credential's name (the blueprint default is `notion-prod`).
- Step 5Decide the page title and body — Set `title` on the Notion node, or leave it blank to fall back to the first line of the upstream text. Set `content` for the page body, or leave it to inherit the upstream item text. Notion finds the title-typed property in your database schema automatically.
- Step 6Confirm tier, then run or let cron fire — `notion-page-create` requires Pro, so the run pre-check gates the whole workflow at Pro. Once you're on Pro with a runner paired, run it manually to verify, then leave the daily cron to fire `0 8 * * *` every morning.
Frequently asked questions
How many nodes are actually in this workflow?+
Two: an RSS / Atom Feed node (`rss-feed`) and a Notion: Create Page node (`notion-page-create`), wired feed-output → Notion-input. That's the entire shipped blueprint. Anything more — multiple feeds, dedupe, retries — is something you add after forking.
Does it dedupe so I don't get the same article twice?+
Not on its own. The shipped blueprint has no Filter node and no Notion-query step, so each run creates pages for whatever items the feed returns. The practical dedupe is the RSS node's `since` filter (only items newer than an ISO timestamp). For true URL-based dedupe, add a Filter logic node on the canvas after forking.
Where is my Notion token stored?+
On your paired runner. The Notion node resolves it at run time via ctx.credentials[credentialRef]; the workflow graph saved on the server holds only the reference name (e.g. notion-prod), never the secret value.
What tier do I need?+
Pro to run. notion-page-create is a Pro tool, and the run pre-check applies the strictest minTier across the whole graph, so the workflow gates at Pro. The RSS node by itself is free-tier.
Is the daily schedule real, or just a label?+
Real. The blueprint sets `0 8 * * *`, which becomes the workflow's schedule_cron on fork. Cloudflare Cron Triggers call /api/orchestrator/cron/tick, which checks each scheduled workflow with isDueSince() and enqueues a run when it's due, then stamps last_fired_at.
Can I change the schedule?+
Yes — edit schedule_cron on your forked workflow to any standard cron expression. The tick route parses it with parseCron and fires accordingly. Hourly, weekday-only, twice-daily all work.
How do I fork it?+
Click Fork on this page. The from-blueprint route copies the two-node chain into a private draft you own, snapshots it as version 1, and records a `forked` audit event tagged with the blueprint slug. Any authenticated account can fork.
Why do I need a runner paired?+
Both nodes are connector-category tools, which run runner-only — they execute on your paired runner, not in the browser or on the JAD server. Without a paired runner the connector nodes have nowhere to run, so a queued run won't execute.
Can I pull from several feeds at once?+
The blueprint handles one URL. To cover 5–10 publications, fork and wrap the feed+Notion pair in a For-Each over a list of URLs — the runner executes iterations with bounded concurrency (configurable 1–32). The seed copy mentioned a Parallel node; that node isn't part of this blueprint and you'd build the fan-out yourself.
What happens if one feed is down?+
In the shipped two-node chain a non-2xx feed (rss_<status>) or a network failure (network_error) aborts the run, because there's no Try/Catch around the feed node. JAD does have a real Try/Catch logic node and per-node retry/skip error policies — add one on the canvas if you want a single bad feed to be non-fatal.
How does the page title get set?+
Set `title` on the Notion node, or leave it blank to use the first line of the upstream text. The node then GETs your database schema once to find the property whose type is 'title' and writes there, so you never hard-code which column is the title.
Where can I see what ran?+
Each fork writes a `forked` audit event and each run records a step trace (the runs trace endpoint). These are server-side records for history and attribution, not files written to your local machine — useful for confirming the 8am run actually fired and which node, if any, errored.