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.

Integration Availability

“Available” means the production integration can be connected when the workspace has the required plan, permissions, and provider configuration. “Limited preview” and “private beta” mean a Keito rollout flag and explicit workspace access are also required. Request-only placeholders in the app, such as Slack and GitHub, are not listed as integrations.

Integration	Status	Best for	Data direction
Xero	Available · Business	Invoices, contacts, invoice numbers, and payment state	Keito to Xero; payments back to Keito
QuickBooks Online	Available · Business	Invoices, customers, payments, employee and item mappings, and approved time	Keito to QuickBooks; payments back to Keito
Stripe Payments	Available · paid plans	Client payment of open invoices	Client to Stripe; payment state to Keito
Google Calendar	Available · Business	Importing meetings and calendar blocks	Google Calendar to Keito, only after the user selects an event
Outlook Calendar	Available · Business	Importing Microsoft 365 calendar events	Outlook Calendar to Keito, only after the user selects an event
Jira Cloud	Available · paid plans	Linked Keito time and Jira worklogs	Keito to Jira; identifiers and status back to Keito
CharlieHR	Available · Business with Planning	Approved leave and planning availability	CharlieHR to Keito
Harvest Import	Available	Migrating a Harvest workspace	Harvest to Keito
Airtable	Available · Business	Importing configured clients, projects, expenses, and receipts	Airtable to Keito
Asana	Available · Business	Starting timers and recording time from Asana tasks, plus project and people imports	Asana context to Keito only
Zendesk	Controlled preview	Timer and manual time capture from Zendesk Support tickets	Zendesk context to Keito
ClickUp	Design-partner beta	Limited native-time synchronisation	ClickUp to Keito and eligible Keito time to ClickUp
Keito CLI	Available · paid plans	Terminal, scripts, CI, and custom-agent automation	Authenticated local client and Keito exchange requested data
Agent Skill	Available · paid plans	Repository-scoped Codex and Claude Code session tracking	Local agent session metadata to Keito
Hosted MCP connector	Available · paid plans	Customer-controlled agent access to Keito tools	Keito returns authorised tool data to the connected customer-chosen agent
Grok Build Plugin	Available · paid plans	Timers, time entries, LLM usage, and time reviews from Grok Build	Keito returns authorised tool data to Grok Build when Grok calls a Keito tool

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.

Airtable provides configured one-way imports of clients, projects, expenses, and receipts for Business workspaces.

Asana lets Business workspaces start Keito timers and record time from Asana tasks using native App Components, with no browser extension. A Keito owner or administrator connects the workspace, and each team member connects their own Asana and Keito identities. Admins can also import Asana projects and people and turn on one-way project sync. Keito does not update Asana’s own time-tracking fields.

Limited Previews And Betas

Zendesk and ClickUp are not generally available. Keito enables them only for selected workspaces while their narrower workflows are validated. The status in the table is the public promise: the presence of implementation code or an app settings route does not make an integration generally available.

• Zendesk is a controlled preview for authorised ticket context, timer and manual time capture, ticket totals, and links to Keito timesheets.
• ClickUp is a create-only design-partner beta. ClickUp-originated entries remain read-only mirrors in Keito during the beta.

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.

Keito does not run a hosted LLM or choose a model for the customer. If you connect the hosted MCP server or another Keito interface to Claude or a different AI service, Keito returns authorised data only when that customer-chosen service invokes a Keito tool. The AI provider’s model, retention, privacy, and training settings are controlled by the customer’s account and agreement with that provider.

Keito does not use Customer Data to create, train, fine-tune, evaluate, or improve generalized or shared AI or machine-learning models. Google Calendar data and data derived from Google Calendar events are additionally excluded from Keito’s AI-agent and MCP integrations and are not sent to AI providers. See the Privacy Policy for the complete data-sharing terms.

See Also

• Xero - sync invoices and payments with Xero.
• QuickBooks Online - sync accounting and time activity with QBO.
• Stripe Payments - accept online invoice payments.
• Google Calendar - import calendar events as time entries.
• Outlook Calendar - import Microsoft 365 calendar events as time entries.
• Asana - track time from Asana tasks and import Asana projects and people.
• Asana Import & Project Sync - import Asana projects and people and keep imported projects in sync.
• Zendesk - controlled-preview installation and ticket time-tracking workflow.
• Jira Cloud - sync linked timer entries to Jira worklogs.
• CharlieHR - sync approved leave into planning availability.
• Harvest Import - migrate records from Harvest to Keito.
• Keito CLI - direct terminal setup.
• Agent Skill - automatic Codex and Claude Code session tracking.
• Hosted MCP connector - customer-controlled agent access to Keito tools.
• Grok Build Plugin - Keito MCP tools and a time-tracking skill for Grok Build.