Integration

Timing
automation.

14 automated actions available through Cerebral OS. Connect Timing to any workflow, Cerebral, or Map — with full governance, audit trail, and dry-run safety on every execution.

14 actions · comms · governed execution

Execution trace
live
14
actions
100%
governed
<200ms
latency
14
Automated actions
6
Read operations
8
Write operations
2,800+
Compatible Maps
Actions

What you can do
with Timing.

Every action below is available as a verb in Cerebral OS — callable from a Cerebral, a Map, or the Runtime API. All executions are governed, audited, and dry-run safe.

Create Project
timing:create_project
Create a new project in Timing.
Write Medium risk
Create Time Entry
timing:create_time_entry
Create a new time entry, either completed or as a running timer.
Write Medium risk
Delete Project
timing:delete_project
Permanently delete a project and all associated time entries.
Write High risk
Delete Time Entry
timing:delete_time_entry
Permanently delete a time entry.
Write High risk
Get Project
timing:get_project
Fetch a single project by ID with details and settings.
Read Low risk
Get Running Timers
timing:get_running_timers
Get all currently running timers.
Read Low risk
Get Time Entry
timing:get_time_entry
Fetch a single time entry by ID with project and task details.
Read Low risk
Get Time Report
timing:get_time_report
Generate a time report for a specific date range with optional project filtering.
Read Low risk
List Projects
timing:list_projects
List all projects with optional filtering and pagination.
Read Low risk
List Time Entries
timing:list_time_entries
List time entries with optional filtering by project, date range, and pagination.
Read Low risk
Start Timer
timing:start_timer
Start a new running timer. This creates a time entry with no end date.
Write Medium risk
Stop Timer
timing:stop_timer
Stop a running timer by setting its end date.
Write Medium risk
Update Project
timing:update_project
Update an existing project's details.
Write Medium risk
Update Time Entry
timing:update_time_entry
Update an existing time entry's details.
Write Medium risk
How it works

Every Timing action
governed end-to-end.

Cerebral OS isn't a connector. It's the execution layer that sits in front of Timing — adding governance, dry-run safety, and a full audit trail to every operation.

Governance first
Every verb carries a risk classification. High-risk writes require explicit approval gates before they execute in production.
Dry-run safe
Simulate any Timing action before it touches production. See exactly what would happen before a single real call is made.
Immutable audit trail
Every Timing action is logged — what ran, what changed, who approved it, when it happened. Full history on every verb, forever.
Timing integration

14 actions.
Governed by default.

Connect Timing to any workflow in minutes. Dry-run every action before it touches production. Full audit trail on everything.

Connect Timing free Browse all integrations →