Productivity · Integration
Teamwork
Add Teamwork to your product for your customers, and give your AI agents governed access to it.
Teamwork is project management aimed at teams who bill for their time, which is why the time entry sits alongside the task instead of in a separate tool. The hierarchy runs from a project to its task lists to the tasks in them, with milestones marking the dates that matter and time logged against individual tasks. That last part is what makes the integration worth having: your product can log time against the work it caused, then read back what a project actually consumed against what was estimated. Each customer runs their own site with their own custom fields, tags and task templates, so mapping is per tenant. fastn holds each site's credentials and keeps the field mapping as configuration.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let each customer connect their own Teamwork site, so projects and tasks move when the work in your product does.
Create a project from a template with its task lists already populated, whenever your product starts a piece of work.
Log time against a task from your product, so billable hours are captured where they were actually spent.
Read estimated against logged time per project, so your product can show where delivery is running over.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent reports which projects are over their estimated hours and which tasks account for it.
An agent creates or reassigns a task within scoped permissions, with the change recorded.
An agent summarises what moved on a project this week from its tasks and time entries.
Example prompt
Which projects have logged more hours than estimated this month, and which task lists are driving the overrun?
Set up Teamwork in 4 steps
- 01Enable the Teamwork connector in your fastn dashboard.
- 02Have each customer authorise their own Teamwork site so work is created under their credentials.
- 03Map the project, task list, task and time entry fields that site uses, including its custom fields and tags.
- 04Call it from your product and expose the same connection to your agents through the MCP gateway.
Why teams use the Teamwork integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a Teamwork integration without building it. Your customers connect their own Teamwork account inside your product and work their work items, assignees and due dates there, with no per-customer code on your side.
- Handle the part that actually costs time: every team configures its own fields, statuses and workflow stages. fastn owns the auth, token refresh, rate limits, pagination and breaking-change fixes, so a Teamwork update is not your on-call problem.
- One integration serves your product and your agents. The same governed Teamwork connection powers in-product features and gives AI agents scoped, audited access, so you keep work items in step with what happens in your product without wiring it twice.
Used by these teams
Compare with
Asana
ClickUp
monday.comOften used alongside
Tools the same teams tend to run next to Teamwork, across other categories.
Notion
Box
Docusign
AWS Simple Storage ServiceTeamwork integration FAQ
How do I add a Teamwork integration to my product?
Enable the Teamwork connector in your fastn dashboard, then let each customer authenticate their own Teamwork account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Teamwork client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own Teamwork account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Teamwork account and only ever sees their own work items, assignees and due dates. That per-tenant isolation is the point of an embedded integration: you support the long tail of customer setups without maintaining an integration per customer.
Can AI agents use this Teamwork integration?
Yes. The same connection is exposed to your agents through the fastn MCP gateway, with permissions scoped per tenant and every call audited. An agent reports which projects are over their estimated hours and which tasks account for it.
Who maintains the Teamwork integration?
fastn does. When Teamwork changes an endpoint, deprecates a field or alters its auth, the fix lands in the connector rather than in your backlog, and your customers' connections keep working.
Can my product create and update work in Teamwork automatically?
Yes. Items can be created, updated, assigned and transitioned from your product, and changes made in Teamwork can trigger your workflows in return.
Does it adapt to each team's own Teamwork setup?
Yes. However a team has configured Teamwork, whether that is custom fields, statuses and workflow stages or its own calendars and working hours, those are mapped per customer, so an unusual setup works without custom code from you.
What can I build with the Teamwork integration?
A common starting point: let each customer connect their own Teamwork site, so projects and tasks move when the work in your product does. Teams also use it for the other use cases listed above, and expose it to agents for governed reads and writes.
How much does the Teamwork integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Teamwork does not change your per-connector cost. You can start free with 3 connected accounts.
Add Teamwork to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.