Getting Started
Create a Source, send your first typed Action, and resume safely after a human decision.
1. Install and configure the CLI
curl -fsSL https://actionbox.cloud/install.sh | sh
actionbox configureKeep Source credentials in trusted servers, workers, CI secrets, or your local credential store. Never place them in browser code.
2. Ask and wait
actionbox ask "Deploy v2.18 to production?" \
--option approve="Approve & Deploy" \
--option reject="Reject & Abort" \
--timeout 30m \
--waitThe command creates an Action and blocks on the server-authoritative state until it resolves or the local wait reaches its timeout. A local timeout leaves the server-side Action open.
3. Review the Action
Open the ActionBox inbox, inspect the proposed operation and context, then choose an option. Treat notifications as alerts; the Action API remains authoritative.
4. Branch on the result
Use --json when software needs the full structured result. For direct integrations, choose the Python SDK, TypeScript SDK, or REST API.
Timeouts are not decisions
If a waiting client times out, do not assume rejection. Read the Action state or define an explicit server-side expiration outcome.