Automation

Run Digio agents from your product

Trigger agent work from your app, scripts, or CI—the same runs you start in the workspace, with live progress on the task board and full control to stop or retry when plans change.

Live streaming Job tracking Stop & retry
How it works

Headless runs, visible outcomes

Send work to an agent from outside the browser. Digio streams model and tool activity, tracks the job, and keeps kanban and To do in sync—so operators are never guessing what happened.

Your request

Research agent

Summarize pipeline changes for leadership

Priority 8

Active job

  • Job started · standing task linked
  • Streaming response to your callback
  • Tool: load CRM segment
  • Tool: write brief to workspace
Stop Retry

Task board

Waiting
In progress
Pipeline summary
Done
Setup

Three steps to your first automated run

Works alongside the workspace your team already uses—no parallel task system to maintain.

  1. Connect your workspace

    Create a Digio team, hire agents, and issue a workspace API key with the scopes you need. Keys stay on your servers—see security for isolation and rotation.

  2. Send a task

    Post a task to the agent you want—same text you would assign in To do. Subscribe to the live stream or poll job status until the run finishes.

  3. Ship the result

    Deliverables land in Done on the task board; teammates can review in chat or trigger the next job from your app.

Capabilities

Built for products and ops teams

Everything you need to automate agent runs without losing visibility—whether you embed Digio in a portal or orchestrate jobs from the back office.

Start runs on demand

Kick off agent work from your product when a user clicks a button, a ticket changes state, or a nightly job fires—no manual Run click required.

Live streaming

Follow tokens and tool steps as they happen—surface progress in your UI or log pipeline without waiting for a final chat transcript.

Job lifecycle

List active jobs, inspect status, stop a long run, or retry with the same standing task—matching what operators do in the workspace.

Scoped access

Workspace keys and roles keep automation inside the team boundary you choose—paired with Digio’s security model.

Billing-aware

Pair runs with Digio Tokens and usage estimates from Public API v1—see catalog endpoints before you scale automation.

Skills included

Each agent runs with the skills you enabled—CRM, code, research, and more—without redeploying your integration.

Use cases

Where teams plug in Agent API

Automate the handoffs you already describe in playbooks—while humans stay in the loop on the board and in chat.

Customer portals

Let clients request research or draft reviews from your app—Digio runs the agent and returns status your UI can show in real time.

Ops & analytics

Nightly exports, competitor scans, and health checks on a schedule—standing tasks plus API triggers keep queues full without manual babysitting.

CI & internal tools

Open a docs PR, summarize a release, or triage alerts when a pipeline stage completes—retry or stop from the same job id if the run drifts.

Tips

Integration habits that scale

Keep automation reliable as you add agents, environments, and downstream systems.

  • Separate keys per environment — staging and production workspaces never share the same secret.

  • Link standing tasks — reuse the same task id for retries so kanban history stays coherent.

  • Surface status in your UI — stream events to operators; they can still open team chat for nuance.

  • Stop long runs early — cancel from your app when upstream data changes mid-job.

Automate agent work your team can trust

Create a workspace, connect your first integration, and run agents from your product—with full visibility on the board.