Your ActionBox Dashboard
Find waiting work, review context, and keep workspace operations moving from one authoritative console.
The ActionBox dashboard is the human-facing control plane for your workspace. It brings Actions, Sources, devices, notifications, callback delivery, and billing into one place while the API remains the source of truth for machine state.
Two surfaces, one state
Use a user session to operate the dashboard. Use a Source key from a trusted script, worker, or agent to create and update Actions. A Source key is not a replacement for a dashboard session.
Start with the path that matches your job
Start guided onboarding
Open a focused three-step walkthrough over Inbox and complete one real decision loop.
Review work
Open Inbox for live Actions, or History for resolved, cancelled, and expired records.
Connect software
Create a Source, copy its one-time credential, and keep the key with the process that runs it.
Coordinate people
Switch workspaces, manage members, and give each person the smallest useful role.
Watch delivery
Inspect signed callback attempts and retry failures from Webhook logs.
What each surface is for
Guided onboarding is not another dashboard section. Opening /setup launches a short walkthrough over Inbox, and Settings can reopen it later.
| Surface | Use it for | What it shows |
|---|---|---|
Inbox (/actions) | Decide, claim, assign, or snooze waiting work | Open live Actions, filtered by routing, priority, search, or Source |
History (/history) | Review what already happened | Terminal Actions: resolved, cancelled, and expired, with filters for status, Source, priority, and date |
Notifications (/notifications) | Triage attention signals | Published, user-scoped notifications and their unread state |
Sources (/sources) | Manage machine identities | Active and revoked Sources, safe key metadata, and one-time rotation flows |
Devices (/devices) | Review registered notification clients | Client label, last-seen time, status, and revocation controls |
Webhook logs (/webhooks) | Diagnose callback delivery | Delivery status, HTTP status, attempt history, and retry controls |
Monitors (/monitors; /watches remains available) | Monitor scheduled or long-running processes | Watch state, heartbeat history, and generated incident Actions |
API playground (/playground) | Build a request interactively | Action fields, typed interaction choices, context, and a reviewer preview |
Usage (/usage) | Review quota and workspace decision health | Current usage plus aggregate creation, resolution, timing, expiration, escalation, and outcome signals when enough retained data exists |
Settings (/settings) | Manage people and notification policy | Team roles, invitations, personal push preferences, and workspace escalation policy |
A reliable review loop
1. Select the right workspace
The workspace selector controls which members, Sources, Actions, and notifications the dashboard loads. If you belong to more than one workspace, switch before making a decision or changing a Source.
2. Triage the Inbox
Use Mine for Actions assigned to you, Unassigned for the shared queue, and All for the whole active workspace. Open the Action and read its description, typed interaction, context blocks, decision context, and current version before responding.
3. Make the decision from the current snapshot
Choose the typed response, option, or acknowledgement shown in the Action. The dashboard submits the Action version and fingerprint it displayed, so a material update made while you were reading fails closed and asks you to review the latest version.
4. Confirm what happened next
Use the Action timeline for the durable decision record. If the Action has a callback, use Webhook logs to inspect delivery; a successful human decision is not the same as successful execution, so software should report its execution outcome separately.
Notes and product feedback
Open and historical Action details include immutable workspace notes. Owners, admins, and approvers can add a note of up to 2,000 characters; viewers can read existing notes but cannot submit one. Notes are for durable review context, not secrets, credentials, or large logs.
When the authenticated dashboard is connected, Give feedback in the sidebar accepts an idea, problem, or question for the ActionBox team. The form records the message with limited page and client context. It is unavailable in offline preview, and it does not attach screenshots, query parameters, Action IDs, Source IDs, tokens, or browser storage.
A notification is not a decision
Push and in-app notifications are attention signals. Opening or marking a notification read does not resolve its Action. Always inspect the current Action state before acting.
A few useful shortcuts
- Create a safe first request: use the Getting Started guide, then keep the returned Source key in the worker or CI secret store.
- Need more structured input? Use Interaction and decision types for boolean, choice, text, numeric, rating, or form responses.
- Need human input from an agent? Read MCP setup before connecting a Source-scoped runner, and enforce non-bypassable tool policy in the application or gateway that owns the side effect.
- Need a machine callback? Follow Webhooks and callbacks and verify the raw request body before parsing it.