ClientsOpportunities, quotes, product catalogue
ProjectsPlanning, tasks, sign-off
ServiceHelpdesk, tickets, retainers, assets
TeamPeople, absence, time
MoneyInvoices, e-invoicing, insights
AgentsLeadtime Agent, your own agents, automation
Product · Integrations
Leadtime talks to your tools.
Integrations: public API, MCP server, n8n, Zapier, webhooks and Slack. Plus inbox, calendar, e-invoicing and CSV import.
Day to day.
What every team needs from day one: 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.
For developers.
Projects, tasks, organisations, time, invoices and more are also available through the API.
Public API
REST API with an OpenAPI description. You authenticate with an access token that belongs to an agent (usable as a service account) and carries its 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. They connect via the Leadtime sign-in and can then run the API actions and search the help centre. If Leadtime is already open in the browser, they use its site tools there, without a connector of their own.
Plugins for Claude, Codex and Cursor
Ready-made skills for Claude, Codex and Cursor, for working in your workspace, setup and import. Install as described 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.
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. It signs in with an access token.
Zapier
Building blocks for Zapier, including invoices, tasks and project documentation. They sign in with an access token from Leadtime. The source code is on GitHub.
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.
What Leadtime doesn’t do, and what you do instead.
There is no direct export to accounting software. Invoices go out as e-invoices or XML; everything else via the API, n8n or Zapier.
There is no two-way sync. Leadtime provides your plan as a subscription and reads busy times from other calendars.
Connected securely.
Every agent has its own account, role and tokens. It cannot log in to the app, every change appears under its name in the history, and deactivating it locks its tokens and MCP sessions immediately.
Where Leadtime runs and who works with your data is on the security page. Security and privacy
Show us your tools.
In a call we go through what you want to connect and show how Leadtime fits in.