Integrations

Keito integrations all write to the same workspace, permission model, client list, project list, task list, invoices, reports, and approvals. Use this page to choose the right integration and understand how data moves.

Each integration guide explains four things: what the integration does, how data moves, how to connect it, and how to disconnect or remove it.

Available Integrations

Integration	What it connects	Best for	Data direction
Xero	Xero accounting	Copying invoices, contacts, invoice numbers, and payment state	Keito to Xero, payments back to Keito
QuickBooks Online	QuickBooks Online accounting	Invoices, customers, payments, employee mappings, item mappings, and approved time activity	Keito to QuickBooks, payments back to Keito
Stripe Payments	Stripe Connect and Stripe Checkout	Letting clients pay open invoices online	Client to Stripe, payment state to Keito
Google Calendar	Google Calendar	Turning meetings and calendar blocks into time entries	Google Calendar to Keito
Outlook Calendar	Microsoft 365 Outlook Calendar	Turning meetings and calendar blocks into time entries	Outlook Calendar to Keito
Jira Cloud	Jira Cloud worklogs	Syncing linked Keito timer entries to native Jira worklogs	Keito to Jira
CharlieHR	CharlieHR leave	Syncing approved leave into Keito planning availability	CharlieHR to Keito
Keito CLI	Local terminal, scripts, CI, and custom agents	Explicit commands and JSON automation	Local machine to Keito
Agent Skill	Codex and Claude Code hooks	Repository-scoped local agent session tracking	Local agent session to Keito

Accounting And Payments

Xero and QuickBooks Online are accounting integrations. They copy invoice and accounting records between Keito and your accounting system. Only one accounting integration can be active at a time.

Stripe Payments is separate from accounting. It creates Stripe Checkout sessions for open invoices and records the payment in Keito when Stripe confirms the money has cleared. If you also use Xero or QuickBooks, the accounting integration can then keep the accounting record aligned.

Calendar, Worklogs, And Leave

Google Calendar and Outlook Calendar import events into Keito time entries. They are per-user connections because calendar accounts are personal. A user can connect either Google Calendar or Outlook Calendar, not both at the same time.

Jira Cloud syncs timer entries linked to Jira issue keys into Jira worklogs. The workspace connection is admin-managed, and each user connects their own Jira identity for correct worklog attribution.

CharlieHR syncs approved leave into Keito planning availability. It is designed for teams using Keito Planning, so project schedules reflect holidays, sick leave, and other configured leave types.

Developer And Agent Workflows

Use the Keito CLI when you want explicit terminal commands:

keito time start --project "Acme Website" --task "Development"
keito time stop --notes "Implemented OAuth flow"

Use the Agent Skill when Codex or Claude Code should log local coding sessions automatically. The skill uses the CLI under the hood, so authentication, permissions, project access, and API writes stay in one place.

keito auth login
keito skill install
cd ~/work/acme-project
# In Codex or Claude Code:
/track-time-keito

Data Boundaries

Each integration is scoped to the connected Keito workspace and the current user’s role. Admin-only integrations are configured in settings. Per-user integrations only access the data authorised by that user.

The CLI authenticates as the current Keito user or API key. It can only access the company, clients, projects, and tasks allowed by that credential.

The Agent Skill adds one repo-local file, .keito/config.yml, after you run the setup wizard in that repository. Each repository chooses its own company, client, project, and task. The hooks search upward from the active working directory and do not reuse another repository’s config.