Use this pattern for scheduled price checks, position health checks, funding rate alerts, or recurring research workflows.

Trading-oriented automations can combine schedules, market data, conditions, and alerts.

Pattern

text
cronjob trigger -> market data action -> if condition -> alert action
Scheduled market alert
runresultthreshold met Cron trigger RRULE schedule and live version Market data Token price, funding, position, or research action Threshold branch Compare price, ratio, or risk metric Alert action Slack, Telegram, email, webhook

Trigger

Use cronjob for recurring schedules. The trigger stores an RRULE string.

json
{ "type": "cronjob", "payload": { "rrule": "FREQ=HOURLY;INTERVAL=1" }, "children": ["fetch_price"]}

Fetch and Compare

json
{ "fetch_price": { "type": "coingecko-get-token-price", "payload": { "ids": "ethereum", "vsCurrencies": "usd" }, "children": ["check_threshold"] }, "check_threshold": { "type": "if", "payload": { "condition": { "$and": [ { "{{$nodes.fetch_price.result.ethereum.usd}}": { "$gte": 4000 } } ] } }, "children": ["send_alert"] }}

Alert

Use Slack, Telegram, email, or an outbound webhook. Keep the alert payload small and include the run ID or workflow link when your receiving system supports it.

Run manually with simulate: true while tuning threshold logic. Publish only after the condition branch behaves as expected.

Schedule triggers

Reference for one-time and recurring schedule triggers.

Learn More
Blockchain data actions

Market, portfolio, token, and analytics data actions.

Learn More
Monitoring

Inspect runs, failures, metrics, and activity streams.

Learn More
Ask a question... ⌘I