ProductWhy LeadtimeClientsProjectsServiceTeamMoneyAgents
MoreOverviewIntegrationsSecurityCalculatorFracto Field
Who it’s forPricing
ResourcesBook: Projects that pay offSwitchingTutorialsRequirements managementHelp centreBlogAbout usContact
Sign in
Start free trialBook a call
A developer works on two screens: Leadtime with a client's tickets on the left, an automation workflow of connected steps on the right.

Leadtime talks to your tools.

Inbox, calendar feed and e-invoicing are built in. For your own tools there is an open API, MCP for Claude, Codex and Cursor, building blocks for n8n and Zapier, and Slack.

What you can connect

All integrations in one picture.

The short version of the list below. One click jumps to the matching row.

From day one

Day to day.

Email, calendars, invoices and the data from the old system.

Inbox

Google, Microsoft 365 or IMAP. Every email to your support address becomes a ticket, and replies go out from your own inbox.

Calendar

Subscribe to your personal Leadtime calendar as an ICS feed in Google Calendar, Outlook or Apple Calendar. Busy times from other calendars come in via ICS, without storing event titles.

E-invoicing

Every invoice goes out as a PDF with an embedded e-invoice (ZUGFeRD/Factur-X) or as XML (XRechnung). You choose the format when sending.

CSV import

Staff, organisations, contacts, projects, tickets and ticket history, up to 50 MB and 100,000 rows per file. Leadtime uses AI to suggest the column mapping.

Export

Dashboards export to Excel. After the contract ends, you can get your data in a common format for up to four weeks.

Photo: A developer leans back at his desk and looks at his screen, with a laptop and an orange notebook next to it.

Developer at an IT service provider

“Can we connect this to our own tools?”

Yes, here’s how

For your own integrations

For developers.

Projects, tasks, organisations, time, invoices and more are available through the API.

Public API

REST API with an OpenAPI description. You authenticate with an agent’s access token, which can also serve as a service account. The token has that agent’s role. Limits: 1,200 requests per minute per token and 3,000 per IP address.

MCP server

MCP is the standard through which AI assistants such as Claude, Codex or Cursor use tools. You sign the assistant in with your Leadtime account. It can then run the API actions and search the help centre. If Leadtime is already open in the browser, it works directly in that tab, without a connector of its own.

Plugins for Claude, Codex and Cursor

Ready-made skills for working in your workspace, setup and data import. Installation steps are in the help centre.

Incoming webhooks

An automation gets its own URL. Every POST to that URL starts the Leadtime Agent, with the request body as its context.

Coding agents on tasks

Cursor Cloud Agents and Claude Agents take on tasks from Leadtime. You connect your own agents via signed webhooks.

Let routine run itself

Automation.

Building blocks for n8n and Zapier, Slack, and automations run by the Leadtime Agent.

n8n

Community node with actions including invoices, tasks and project documentation. In n8n, install it under Settings, Community Nodes, using the package name n8n-nodes-leadtime. Sign-in uses an access token.

Zapier

Building blocks for Zapier, including invoices, tasks and project documentation. Sign-in uses an access token from Leadtime.

Slack

A message in a public channel starts an automation, optionally only for certain keywords. The Leadtime Agent posts results to channels or as direct messages and shows its progress live.

Automations

You write a prompt and choose who runs it: you or an agent. It starts on a schedule, when an organisation, project or task is created, on a Slack message or via a webhook.

Other tools

Automation tools without their own building blocks call the API with an access token.

Next step

Show us your
tools.

Tell us which systems you use. On a call we show live how Leadtime connects to them.