Project Management

Teamwork.com AI automation and integrations

The short answer

Teamwork.com has a REST API, with v3 for most new work, authenticated with OAuth 2.0 or an API key, plus webhooks. Zapier and Make have built-in Teamwork.com apps, and n8n connects through its HTTP Request node. Because it is built for client work, the best AI automations draft time entries, write client status reports and push billable time to accounting. Rate limits are 150 requests per minute on Grow and lower plans.

What you can automate with Teamwork.com

Time entry drafting

Draft time entries with clear descriptions from calendars, task activity and emails, for each person to confirm before they hit the timesheet.

Read the build guide
Client status reports

Summarize milestones, completed tasks, budget burn and open items per client project into a short report the account manager edits and sends.

Read the build guide
Billable time to accounting

Push approved billable time and expenses into QuickBooks Online or Xero as invoice lines with the right customer and service item.

Read the build guide
Email to task

Turn client emails into tasks in the right project and task list with an AI summary and a suggested assignee.

Read the build guide
Project status for the team

Post a weekly written update per project covering what moved, what is late and what is blocked.

Read the build guide
New client project setup

When a deal closes in the CRM, create the project from a template, add the team and schedule kickoff tasks.

What makes Teamwork.com a good fit for automation

Teamwork.com is built for teams that deliver client work: agencies, consultancies and professional services firms. Beyond projects, task lists and tasks, it tracks time, budgets, rates, invoices, milestones and resource capacity. That data is exactly what owners want reported and what accountants need, and the REST API exposes it. Webhooks fire on task, project, milestone, time and comment events. Zapier and Make both have Teamwork.com apps; n8n uses HTTP Request nodes against the account’s site URL.

The friction is versioning. Teamwork.com has a v1 API and a newer v3 API, and some objects or fields exist in only one. Plan endpoint by endpoint, and prefer v3 where it is available.

The AI layer

For client-service firms, time and communication are where the hours disappear. AI earns its keep there:

Billing amounts come from Teamwork.com’s rates and approved time, calculated in code. The model only writes descriptions and summaries.

Limits to plan around

  • 150 requests per minute on Grow and below, 300 on Scale, shared across the whole account. Syncs should filter by updated date rather than pulling everything.
  • Site-specific URLs. Store the site URL with each connection.
  • v1 and v3 differences in field names, pagination and response shapes.
  • Webhook verification. Use a webhook token or checksum to confirm events came from Teamwork.com.

How Lumeor typically connects it

We use a dedicated integration user, build a small set of n8n HTTP Request nodes for tasks, time entries and projects, and run time drafting and reporting on schedules. Approved billable time flows to accounting with the same validation we use for QuickBooks data entry, so invoices match what was approved in Teamwork.com.

Frequently asked questions

What are Teamwork.com's API rate limits?

The core API allows 150 requests per minute on Grow and lower plans and 300 per minute on Scale, counted across all users on the account. Responses include headers showing the limit, remaining requests and reset time. Teamwork Desk has its own separate limit.

Does n8n have a Teamwork.com node?

Not a built-in one. n8n connects through the HTTP Request node using the account's site URL and an OAuth 2.0 credential or API key, and a Webhook node receives Teamwork events. Zapier and Make both have built-in Teamwork.com apps.

Can AI fill in our timesheets?

It can draft them. A workflow can read calendars, task activity and emails, propose entries with descriptions, and ask each person to confirm or edit. Billable time should never be submitted without the person who did the work approving it.

Why use the v3 API instead of v1?

Teamwork.com builds new features on v3, which has more consistent responses and better filtering. Some older objects are still only in v1, so many integrations use both. Check the docs per endpoint.

Next steps