Standing task cron (SCHED)
Set cron-style schedules and your workspace timezone on standing tasks in To do. SCHED tasks run on Digio’s cloud scheduler when your workspace is connected—your team always sees the next run in the queue.
Automation
Agent automation—not just app triggers
Digio combines scheduled standing tasks, spreadsheet auto-run, webhooks, and Agent API jobs with a coordinator-led workspace. Unlike Zapier, Make, or n8n alone, automations here run multi-step agent work you can review on the board, in To do, and in Backlog—not only pass JSON between SaaS apps.
Cron & SCHED
Webhooks & API
Human-in-the-loop
Ops squad · automation
Same job record in UI, API, and optional outbound POST.
Built in
Four automation layers in one dashboard
Use the layer that fits the job—or combine them. All paths update the same standing tasks, kanban columns, and agent chats your team already monitors.
Backlog auto-run
On the Backlog sheet: batch auto-run Ready rows on scheduler tick, field rules (when Status becomes Ready → run row), run queue with cancel/retry, and POST webhook when Status = Done.
Inbound & outbound webhooks
Slack, CRM, and custom HTTPS endpoints via agent skills—create or update standing tasks. Pair with integrations for scoped tool access.
Agent API & Public API
Trigger agent jobs from your product—Agent API streams runs into the same board and To do queue, with scheduling that keeps recurring work on time without manual checks.
Compare
Digio vs Zapier, Make, and n8n
Workflow builders excel at moving data between apps. Digio is built for coordinator-led agent operations—reasoning, tools, review, and recurring agent jobs. Many teams use both: Zapier/Make/n8n for simple triggers, Digio for the agent work that follows.
| Capability | Digio | Zapier | Make.com | n8n |
|---|---|---|---|---|
| Primary focus | Multi-agent ops workspace | SaaS app automation | Visual scenarios | Node workflows (self-host option) |
| LLM / agent reasoning | Core — hire specialists + coordinator | Add-on AI steps | Add-on AI modules | Community AI nodes |
| Task board & queue | Kanban, To do, Backlog sheet | No — zaps only | No — modules only | Custom — you build it |
| Cron / scheduled agent runs | SCHED tasks + server cron + sheet auto-run | Schedule zap (app actions) | Scenario scheduling | Cron trigger node |
| App connectors | Skills + webhooks + API (focused set) | Very large catalogue | Large catalogue | Huge + custom nodes |
| Human review on canvas | Konva board, chats, roles | Limited | Limited | You design approval gates |
| Self-host | Cloud workspace (dedicated boundary) | Cloud | Cloud | Yes (open source core) |
| Best paired with | Your product via Agent API | Quick app glue | Complex multi-app flows | Engineering-owned pipelines |
When Zapier is enough
Form submit → Slack message, or CRM stage change → email—short, deterministic steps with no agent judgment. Digio is not a replacement for thousands of connectors; it is where the agent brief, run, and review live afterward.
When Make fits better
Branching scenarios across many SaaS APIs with routers and filters—especially marketing ops glue. Digio adds specialist agents, streaming output, and a visible queue when steps need language models and tools.
When n8n fits better
Self-hosted, engineering-owned ETL-style workflows with full control of nodes and data residency. Digio targets teams that want a ready-made agent workspace with coordinator, kanban, and token billing—not building every approval UI from nodes.
When Digio is the right hub
Weekly research scans, support triage, content pipelines, or backlog-driven ops where agents must run, pause for humans, and leave audit trails on the board—not only move records between apps.
Getting started
How to create automations
Start with a recurring schedule for one agent task—then add Backlog rules or webhooks when your team is ready.
-
Schedule recurring agent tasks
In To do, add a standing task for an agent and open Schedule. Pick date, time, and your workspace timezone—or set daily, weekly, or monthly recurrence. For custom timing, use cron expressions (for example, every Monday at 9:00).
-
Enable cloud scheduling
Connect your workspace to the Agent API so Digio runs due SCHED tasks automatically—no need to keep a browser tab open. The same jobs appear on your kanban board and in To do.
-
Automate from Backlog
In Tables → Backlog, turn on Auto-run Ready rows, add rules when status changes, and optionally notify another system when a row is Done. Use Run visible Ready rows for one-off batches your team approves first.
-
Connect external triggers
Link Slack or your CRM through Integrations, or call the Agent API from your product. Zapier, Make, and n8n can hand off to Digio—agents do the work and your board stays current.
-
Start from a template
Copy a template with ready-made standing tasks (weekly scans, digests), then add schedules or webhooks. Your board, To do, and kanban stay aligned from day one.
Product detail
What runs automatically
Exact controls available in the Digio dashboard today.
SCHED standing tasks
Standing tasks per agent with a SCHED badge in To do and on the Waiting column; next-run times follow your workspace timezone and run on Digio’s scheduler when your workspace is connected.
Sheet auto-run rules
Cron rules: pick rows with Status = Ready on each tick (cap per rule). Field rules: run when you edit a cell to a matching value. Respects Blocked by dependencies and busy agents.
Done webhook
Send an HTTPS notification when a Backlog row reaches Done—Digio delivers it reliably through your connected workspace, with retries when needed.
Board ↔ sheet sync
Auto-sync Backlog → kanban every 8s; import Task board into Backlog; sync selection to board; auto-add new standing tasks to Backlog when enabled.
Agent API jobs
Start, stream, stop, and retry jobs; same status columns as manual Run; scheduler store sync for headless cron across dashboards.
Team guardrails
Editor vs guest roles on sheets; integration scopes; human approval paths on skills—automation scales without losing who triggered what.
Tips
Automation habits that work
Combine Digio with Zapier/Make/n8n for triggers, not for the whole agent brain.
-
Cloud scheduling first — connect your workspace so recurring SCHED tasks run even when no one has Digio open.
-
One webhook pilot — inbound create-task + outbound Done before chaining five zaps.
-
Backlog for batches — ops reviews Ready rows on the sheet before auto-run drains the queue.
-
Clone templates — playbooks ship standing tasks you can cron on day one.
Connected
Templates, tasks, tables, API
Automation is the glue across Digio product pages—not a separate product.
Templates
Related pages
Templates, compare, and integrations to extend your setup.
Automate agent work, not only app hops
Clone a playbook, attach cron to one standing task, and watch the board move—then add webhooks when you are ready.