Crypto markets run continuously, which makes automated price content both easier and riskier than most other data formats: easier because there's always fresh data, riskier because "always fresh" without a real filter means an account that posts constantly about nothing in particular.
Two legitimate formats, pick one deliberately
Scheduled snapshot — a fixed daily or weekly post regardless of movement ("here's where things stand"), calm and predictable. Threshold alert — posts only when a move crosses a real bar, reactive and higher-signal. Both are valid; the mistake is drifting into a hybrid where a "snapshot" workflow's tight polling interval effectively makes it fire like an alert, or an "alert" workflow's threshold is set so loose it fires on noise.
The node chain for a threshold alert
Trigger — a timer, polling tight enough to catch a real move promptly (crypto's continuous movement means this can reasonably be tighter than a stock-market equivalent — see Trigger timing recipes).
HTTP Request — a price data source, ideally returning both current price and recent history for a chart.
Code node — compute the percentage move since your last check or a fixed window (see transform #3, computing a delta).
If node — the real gate: only continue when the computed move exceeds a genuine threshold. This is the single node keeping the workflow from posting on every check.
Apply Template — bind the current price, the computed change, and (if the template includes one) a price-history chart into your design — see binding charts and tables into posts.
Post — publish.
Picking a threshold that actually filters
A threshold too loose (say, any 1% move) fires constantly given crypto's normal volatility — that's not a filter, it's a schedule wearing a filter's clothes. A genuinely useful threshold is calibrated to what your specific audience would consider notable for the specific asset, which varies — a 1% move in a major, stable asset means something different than the same percentage in a smaller, more volatile one. Watch what the workflow actually produces for a week and adjust from there, the same tuning process as any If node filter.
Why a chart earns its place here specifically
Crypto's audience is unusually comfortable reading price charts compared to most content audiences — a candlestick or line chart bound to real price history often communicates a move better than a text percentage alone, especially for volatility or trend shape a single number can't convey. This is one of the clearer cases where the extra element-binding step (versus a plain text placeholder) is worth the setup.
The honest risk this format carries
Financial content, even simple price recaps, carries more scrutiny than most formats — accuracy of the number and the timestamp matters more here than in almost any other automated content type, since a stale or wrong price is a factual claim, not just an awkward post. Keep review in the loop longer than you might for a lower-stakes format (see the pre-launch checklist) before trusting this one fully to a timer.