Ex 1.1 — Good Morning, Founder ☕
Goal: every morning at 9am, a digest of news from YOUR industry lands in Discord on its own. Mode: individual.
What you'll learn: scheduled triggers, calling an API, reading JSON, {{ }} expressions.
🐛 This workflow contains ONE bug — on purpose
You're going to start from a skeleton we prepared. It contains exactly one bug, in the "Format message" node. Finding and fixing it is part of the exercise. (Real workflows always arrive broken. Might as well learn that on day one.)
Step 0 — Open the skeleton
- The skeleton is already in your instance: on the Overview page, open the workflow Ex 1.1 — Good Morning, Founder. Don't import it again: you'd end up with a duplicate.
- You should see 4 nodes:
Schedule Trigger→Get News→Format message→Send a message. - Workflow missing or broken? Backup: download
good-morning-founder.json, then ⋯ menu (top right) → Import from file.

CP1 — The workflow runs
Click Execute workflow. Some nodes turn green, maybe not all — that's normal at this stage.
✅ Done when: at least the first 2 nodes are green. → CP1.
CP2 — Look at what the API sends back
- Open the Get News node. It calls the Hacker News search API:
https://hn.algolia.com/api/v1/search?query=fintech&tags=story - Look at the OUTPUT panel: it's JSON. Find the
hitslist — each item has atitle, aurl, somepoints. Boxes inside boxes. - Replace
fintechin the URL with a keyword from YOUR industry (in English, one word to start:skincare,edtech,logistics…). - Re-run the node.

✅ Done when: OUTPUT shows articles that (roughly) relate to your industry. → CP2.
Hint 1
OUTPUT empty, hits: []? Your keyword is too niche or not in English. Try broader, in English. You need results for the next step — doesn't matter if they're perfect.
CP3 — Find and fix the bug 🐛
- Open Format message. It builds the digest text with expressions:
☀️ Good morning! Here's your digest for {{ $now.format('dd/MM') }}: 1. {{ $json.hits[0].titel }} → {{ $json.hits[0].url }} 2. {{ $json.hits[1].title }} → {{ $json.hits[1].url }} 3. {{ $json.hits[2].title }} → {{ $json.hits[2].url }} - Run the workflow and look at the message produced. Something's off on one line.
- Fix it. (Reminder from the survival card, reflex #2: the previous node shows you the REAL field names.)
✅ Done when: all 3 lines of the message show real titles — no more undefined. → CP3.
Hint 1
Compare line 1 to lines 2 and 3. Character by character.
Hint 2
A field that doesn't exist does NOT throw a red error — it produces an empty string, nothing shows up. That's why this bug is nasty: everything's green, no weird word to spot, just a missing piece of the sentence.
Hint 3 (basically the answer)
The field is called title in the API's JSON. Line 1's expression asks for titel. The API can't guess what you meant.
CP4 — The digest lands in Discord
- Open the Send a message node (Discord): credential
Workshop Discord; server and channel are already set to your#sNN(nothing to pick); message = the output ofFormat message(already wired up), prefixed[1.1]so you can spot it in your channel. - Execute workflow → go check Discord.

✅ Done when: your digest, with YOUR industry news, is in your #sNN, starting with [1.1]. → CP4.
CP5 — Schedule it for tomorrow 9am
- Open Schedule Trigger → set: every day, 09:00.
- Top right of the canvas: flip the workflow to Active (toggle).
✅ Done when: the toggle is green / "Active". Tomorrow at 9:00am, your digest will arrive on its own — you just automated your news watch. → CP5, exercise done: check it off on the progress board. 🎉
Done early?
- Add the points of each article to the message (
{{ $json.hits[0].points }} pts) - Two keywords? Check the API docs:
query=skincare%20OR%20beauty