The same handful of nodes — HTTP Request, an If check, a Custom Agent, Apply Template, Post — recombine into a surprising range of formats once you start varying the data source. Here are fifteen, each with the actual data, the node chain, and the template shape, so you can build any of them today rather than treat "live data automation" as an abstract idea.
1. Weekly price recap (finance/crypto)
Data: a week of price points for an asset. Chain: HTTP Request (price history) → Custom Agent (write the one-line take) → Apply Template (headline placeholder + candlestick element) → Post. See the full walkthrough.
2. Game-day score recap (sports)
Data: final score, key stats. Chain: HTTP Request (scores API, on a timer near game-end times) → If (game finished?) → Apply Template ({team_a}, {team_b}, {score} placeholders) → Post. The If check matters here — without it you'd post a "0-0, still playing" card.
3. Daily weather card
Data: forecast high/low, condition. Chain: HTTP Request (weather API, daily timer) → Apply Template ({high}, {low}, {condition} placeholders, an icon per condition swapped by a template variant) → Post. Good first automation — no If node needed, ships every day at the same time.
4. Price-drop alert (e-commerce)
Data: your own product feed or a tracked competitor's. Chain: HTTP Request (product API) → Code node (compute delta vs. last known price — see transform #3) → If (delta > threshold) → Apply Template ({product}, {was}, {now} placeholders) → Post.
5. New listing announcement (real estate)
Data: your own listings feed. Chain: HTTP Request (listings API) → If (status = "new") → Custom Agent (write a one-line hook for the property) → Apply Template (photo, {price}, {beds}, {hook}) → Post.
6. Currency exchange snapshot
Data: a currency pair's rate. Chain: HTTP Request (exchange rate API, daily) → Code node (format as currency — transform #5) → Apply Template ({rate}, {pair}) → Post. Useful for travel, import/export, or remittance-adjacent accounts.
7. "This week in [industry]" digest
Data: several stories from a news source, filtered. Chain: HTTP Request (news feed) → If (relevant + this week) → Custom Agent (summarize into 3 bullet points) → Apply Template (a multi-slide carousel, one bullet per slide) → Post. The richest format on this list — full walkthrough in how to create content automations.
8. Job market snapshot
Data: open roles matching a filter (your own hiring feed, or a public jobs API for a market report angle). Chain: HTTP Request → If (matches criteria) → Apply Template ({role}, {count}, {location}) → Post.
9. Countdown post (events, launches)
Data: a fixed target date, computed against today. Chain: Trigger (daily timer) → Code node (compute days-remaining) → If (still counting down) → Apply Template ({days_left}, {event_name}) → Post. Naturally self-terminating — add an If check for "days_left <= 0" and disconnect Post on that branch.
10. Box office / release-week numbers
Data: opening or weekly box office figures. Chain: HTTP Request (box office API) → Custom Agent (one-line take on the number) → Apply Template ({title}, {gross}, {take}) → Post.
11. Review score aggregate
Data: your product's rating across review platforms. Chain: HTTP Request (reviews API) → Code node (average across sources) → Apply Template ({avg_rating}, {review_count}) → Post. Pairs well with a monthly timer rather than daily — this number moves slowly.
12. Milestone announcement
Data: a running total (followers, users, downloads — whatever you track). Chain: HTTP Request (your own analytics endpoint) → If (crossed a round-number milestone) → Apply Template ({milestone}, {metric_name}) → Post. The If condition is what stops this from posting "47,213 followers" every single day.
13. Multi-source price + commentary post
Data: a price feed plus separately-generated commentary. Chain: two sources (HTTP Request + Custom Agent) feeding one Apply Template node — the merge-by-label pattern, not a linear chain. Full mechanics in joining multiple data sources.
14. Gas / commodity price ticker
Data: a regional average price. Chain: HTTP Request (pricing API, daily) → Code node (delta vs. last week) → Apply Template ({price}, {direction}, {pct}) → Post.
15. Poll or survey results digest
Data: results from your own running poll (a form backend, a survey tool's API). Chain: HTTP Request (poll results) → Custom Agent (pick the most notable finding) → Apply Template (table element for the full breakdown + a headline placeholder for the takeaway) → Post. See binding a table into a post for the table-element half of this.
The pattern underneath all fifteen
Every one of these is the same five-node shape, wearing different data: a source (HTTP Request or a merge of several), an optional filter (If), an optional AI step for anything that needs writing (Custom Agent), a template binding (Apply Template — text placeholders and/or a chart or table element), and Post. Once you've built one, the next fourteen are a matter of swapping the data source and the template — not learning a new pattern. Start with whichever idea on this list your audience already asks about, and the workflow for the next one will feel obvious rather than intimidating.