Skip to content

odoo-work-cli clock in

NAME

odoo-work-cli-clock-in - Clock in (start attendance)

SYNOPSIS

odoo-work-cli clock in [--at TIME] [--json | --format FORMAT]

DESCRIPTION

Start an attendance record now, through the Odoo web session (the controller of the attendance systray). It needs the login password (ODOO_WEB_PASSWORD, or password in [op_secrets]) and, with two-factor authentication, the TOTP secret.

--at TIME uses an earlier time instead: HH:MM is today, "YYYY-MM-DD HH:MM" any day. A time more than one minute in the future is a validation error. --at writes hr.attendance over XML-RPC with the API key, which requires the Attendance Officer access right, with you set as your own attendance manager.

Clocking in while already clocked in is a conflict error.

OPTIONS

--at TIME

Clock in at an earlier TIME, HH:MM or "YYYY-MM-DD HH:MM", instead of now; requires attendance officer rights.

string; optional; default: now

GLOBAL OPTIONS

--format FORMAT

Output FORMAT: table, json or jsonl.

one of table, json, jsonl; optional; default: table

--json

Shorthand for --format json.

flag; optional

--backend BACKEND

BACKEND: odoo or fake (offline, made-up data; env ODOO_WORK_CLI_BACKEND).

string; optional; default: odoo; env: ODOO_WORK_CLI_BACKEND

--config FILE

Read only the config FILE (skip discovery).

string; optional

-h, --help
Print the help of the command and exit.

OUTPUT

Prints "Clocked in at HH:MM"; with --at "Clocked in at YYYY-MM-DD HH:MM (#ID)".

With --json the new, running attendance record.

Fields of attendance.schema.json:

id
integer
employee_id
integer or null
employee
string or null
check_in
string (RFC 3339 timestamp)
check_out
string (RFC 3339 timestamp) or null
running
boolean
worked_hours
number
worked_minutes
integer

ENVIRONMENT

ODOO_URL
Odoo server URL; overrides url from the config files.
ODOO_DATABASE
Odoo database name; overrides database.
ODOO_USERNAME
Odoo login, usually an e-mail address; overrides username.
ODOO_PASSWORD
Odoo API key, used for XML-RPC. Despite the name, not the login password.
ODOO_WEB_PASSWORD
Odoo login password, used for the web session of clock in and clock out.
ODOO_TOTP_SECRET
TOTP secret (base32 or otpauth:// URL) for accounts with two-factor authentication.
ODOO_OP_TIMEOUT
Timeout of the 1Password call that resolves [op_secrets], a Go duration; default 5s.
ODOO_WORK_CLI_NO_OP
If 1, true, yes or on, [op_secrets] is ignored and the 1Password CLI is never called.
ODOO_WORK_CLI_BACKEND
Backend, odoo (default) or fake; --backend overrides it.
ODOO_WORK_CLI_FAKE_STATE
State file of the fake backend; default odoo-work-cli-fake-state.json in the temporary directory.
XDG_CONFIG_HOME
Base directory of the global config file; default ~/.config.

FILES

~/.config/odoo-work-cli/config.toml
Global configuration ($XDG_CONFIG_HOME/odoo-work-cli/config.toml if XDG_CONFIG_HOME is set). Created by odoo-work-cli config install.
.odoo-work-cli.toml
Configuration of a directory tree. Every such file from the filesystem root down to the current directory is merged over the global file, the deepest last. --config FILE loads only FILE instead.
$TMPDIR/odoo-work-cli-fake-state.json
State of the fake backend (--backend fake); ODOO_WORK_CLI_FAKE_STATE sets another path. Delete it to start over with the seed data.

EXIT STATUS

0 on success, 1 on any error, including usage errors. With --json or --format json|jsonl the error is printed on standard output as one JSON object, {"error": {"kind": KIND, "message": TEXT}}, and nothing on standard error; otherwise as "Error: TEXT" on standard error, after usage errors followed by the usage.

Error kinds this command can fail with:

auth
Authentication failed: wrong API key or login password, TOTP rejected.
access_denied
Odoo's access rules forbid the operation, e.g. attendance writes without the Attendance Officer right.
validation
Invalid input: unknown flag, bad argument, malformed date, time or hours, a time in the future, an unknown project.
conflict
The request contradicts the current state, e.g. clock in while clocked in, or an overlapping attendance record.
network
Odoo cannot be reached: DNS, connection refused, timeout, TLS.
config
The local configuration is missing or invalid.
secrets_locked
1Password is locked or unreachable, so op:// references could not be resolved.
internal
Anything else: an unexpected Odoo response or a bug.

EXAMPLES

Back from lunch: close the morning, then clock in again, both afterwards:

$ odoo-work-cli clock out --at "2026-04-09 12:00"
Clocked out at 2026-04-09 12:00
Duration: 3:19 (3.32h)
$ odoo-work-cli clock in --at "2026-04-09 12:45"
Clocked in at 2026-04-09 12:45 (#5000)

SEE ALSO