Scripts

Manage and run your scripts

Name	Runtime	Timeout (s)	Actions
Loading…

Edit Script

Name

Timeout (sec)

Webhook slug (optional)

Trigger: /run <slug>. Lowercase, digits, -.

Accepts arguments (webhook-only — cannot be scheduled by cron)

Tag (optional)

Group in tabs. Lowercase letters and -.

Help text (optional)

Shown by /help in chat and in Telegram’s command menu. Without one the command is still listed, just undocumented.

Callback URL (optional)

Receives the script result after execution — once, for the final outcome (retries don't re-fire it).

Error retry

Retry count

0 = no retry. Max 10.

Retry interval (s)

Wait between attempts.

Retries on non-zero exit or timeout, on every run path (cron, webhook, trigger URL). The editor “Run” button above never retries.

Public trigger URL

Share this long URL with third-party services. It can be called directly without an authorization header.

Sandbox (bwrap isolation)Persist ($DELAYEDI_DATA)Network access

Max memory (MB) blank = unlimited

CPU budget (%) of timeout

Sandbox: read-only /usr, cleared env, own PID ns, ephemeral /tmp. Persist: durable $DELAYEDI_DATA dir survives runs.

Runtime

Any mise spec works. Floating aliases (latest,lts) are allowed but can drift to a version that isn't installed — prefer a pinned version for scheduled scripts.

Source

··

Script stdout must be valid JSON. It's fed to cron message templates as {$.key}.

Preview & Verify

Sample script output (JSON)

Reply template (optional — sent as WhatsApp reply when triggered via /run)

Left blank: replies with raw [stdout]/[stderr]. On script error / non-JSON output: falls back to raw so errors stay visible.

Rendered preview

Scripts

Result