sim is the command line for Sim. Sign in once, then run workflows, query tables,
move files, search knowledge bases, and read run logs from the terminal. Every
command has a --output json mode, so results pipe cleanly into jq, cron jobs,
CI pipelines, and any other tool you already use.
Install
npm install -g simpnpm add -g simbun add -g simRequires Node.js 20 or newer. Verify with sim --version.
To run it without installing, use npx sim <command>.
Using Sim as a library instead? See the TypeScript and Python SDKs, or the HTTP API.
Your first command
Sign in
sim loginThe terminal prints a pairing code and a URL. Approve it in the browser and pick a workspace. There is no loopback listener, so this works over SSH and in containers.
See Authentication for CI keys, multiple accounts, and self-hosted deployments.
Check what you are pointed at
sim whoamiThis prints the resolved endpoint, workspace, and output format — and where each one came from. It is the fastest way to explain a surprising result.
List your workflows
sim workflows listID NAME FOLDER DEPLOYED RUNS LAST RUN
3a9e21d8-5f47-4c0b-b2ea-91d7c6034ef8 Refund triage /Support yes 412 2026-08-15 14:02:11
b8c0d247-9e13-4a86-97f5-2ad4e1638c09 Weekly digest /Reporting no 18 2026-08-11 09:00:04Run one
sim workflows run 3a9e21d8-5f47-4c0b-b2ea-91d7c6034ef8 --input '{"ticketId":"T-4821"}'A workflow must be deployed before it can be run. Deploy from the editor, or
with sim workflows deploy <id>.
How commands are shaped
Every command reads the same way:
sim <resource> [sub-resource] <verb> [arguments] [options]sim workflows list
sim tables rows query tbl_9f3c1a05d4b7426e8c2f0917ab35de64 --limit 50
sim knowledge documents upload 4c1b7f60-2d55-4a3e-9c18-70b6ea2f9d31 ./handbook.pdfResource groups are plural, and each also accepts its singular spelling —
sim workflow get and sim workflows get are the same command. knowledge
also answers to kb.
Every command accepts --help, at any depth:
sim --help
sim tables --help
sim tables rows query --helpWhat you can do
| Group | What it covers |
|---|---|
workflows | Run, deploy, roll back, import, export, and organize workflows |
logs | Read run diagnostics, including the full trace tree |
tables | Query, insert, update, and import rows; manage columns and views |
files | Upload, download, share, and organize workspace files |
knowledge | Search knowledge bases and manage their documents and tags |
skills | Manage agent skills |
mcp-servers | Manage MCP server connections and their tools |
custom-tools | Manage custom tool definitions |
credentials | Connect, reconnect, and disconnect integration credentials |
secrets | Set and remove workspace secrets |
billing | Check plan status and credit usage |
audit-logs | Read organization audit logs |
workspaces | Inspect the active workspace and its members |
blocks | Browse the block catalog and read one block's configuration fields |
tools | Browse the tool catalog |
connector-types | Browse knowledge-base connector types and their config fields |
chat-deployments | List the hosted chats a workspace serves |
workflow-mcp-servers | Publish workflows as MCP tools for outside agents |
meta | Check what this API supports and which limits apply |
The command overview has the global options and the commands that take no resource; the complete reference documents every subcommand, argument, and flag on one page. Both are generated from the CLI itself.
Where to go next
- Authentication — signing in, API keys for CI, and multiple accounts
- Configuration — profiles, config files, environment variables, and precedence
- Output formats —
table,json,yaml, andtext, and when to use each - Scripting — piping, file inputs, exit codes, and automation recipes
- Troubleshooting — what each error means, and how to resolve it
- Command overview — global options, the command groups, and the commands that take no resource
- Complete reference — every command, argument, and flag on a single page