Schedule

Sources core.schedule Version 1.0.0

Starts the chain at fixed times. Is true on the candle that contains the scheduled time, for example for a daily briefing at 8:00. It fires when that candle closes, so with 1h candles exactly at 8:00.

Inputs and outputs

Only matching types connect: number series to number series (round pin), signal to signal (square), message to message (diamond).

Direction	Pin	Type	Note
Input	–	–	No inputs: the data comes straight from the source.
Output	Signal out	Signal (true/false)	–

Settings

The settings appear on the right under “Properties” once the node is selected on the board. Those marked “More” appear after clicking “More”.

Setting	Default	Allowed	Meaning
Hour hour	8	from 0 to 23, whole number	–
Minute minute · under “More”	0	from 0 to 59, whole number	–
Days days	daily (daily)	daily · Mon–Fri · Sat–Sun · Mondays · Tuesdays · Wednesdays · Thursdays · Fridays · Saturdays · Sundays	–
Time zone timezone · under “More”	Europe/Berlin	IANA time zone such as Europe/Berlin, at most 64 characters	IANA time zone such as Europe/Berlin. Daylight saving time is handled.

Example

A briefing on weekdays at 8:00: the schedule triggers, the message template inserts the current price.

On the board it reads: Mon–Fri at 8:00 AM

Chain as JSON

To try it, copy it and paste it in the editor under “Import”. Importing creates a new chain.

schedule.json

{
  "name": "Example: Schedule",
  "version": 1,
  "nodes": [
    { "id": "c1", "type": "core.candle", "position": { "x": 40, "y": 40 }, "settings": { "pair": "BTC/USDT", "timeframe": "1h" } },
    { "id": "m1", "type": "core.message", "position": { "x": 260, "y": 40 }, "settings": { "text": "Good morning! BTC is at {{a}}." } },
    { "id": "s1", "type": "core.schedule", "position": { "x": 40, "y": 170 }, "settings": { "hour": 8, "days": "weekdays" } },
    { "id": "t1", "type": "core.telegram", "position": { "x": 480, "y": 40 }, "settings": {} }
  ],
  "edges": [
    { "from": "c1.close", "to": "m1.a" },
    { "from": "s1.out", "to": "t1.in" },
    { "from": "m1.out", "to": "t1.message" }
  ]
}

Good to know

• Search also finds it under: cron, daily, time, briefing.

Technical details

• Type in the chain: core.schedule · Version 1.0.0 · Category key src
• How a node is built