Integration · Automate and collaborate
Teamwork.com and Meteor AI agents
Connect Teamwork.com to a Met: search projects and tasks, log time, open Desk tickets and link them to the task with the official MCP.
How does Teamwork.com connect to Meteor?
With the Teamwork.com ready connector, your Met works on the Teamwork.com account the admin authorizes, with its permissions. It searches projects, tasks, messages and comments, lists a project's tasks and reads their comments, and logs time on a project or a task. In Teamwork Desk it searches tickets and customers, creates a new customer and links a task to a ticket. Creating and changing tasks, commenting, creating and changing tickets and replying to the customer start turned off, because the Teamwork server marks them as destructive actions.
What it automates
What a Meteor Met does with Teamwork.com
Turn a complaint into a ticket and a task
A customer reports a problem on WhatsApp. With those actions on, the Met opens the ticket in Desk, creates the task for the team and links them.
Answer how a job is going
When the customer asks, the Met finds their project, lists the open tasks and reads the latest comments to tell them how it is going.
Log time from the chat
Someone on the team writes to the Met how much they worked and on what. The Met logs the time on the right project or task.
Find an old ticket
The Met searches the customer's tickets by email or company and brings back the right one, with its status and priority.
22 tools
Everything your Met can ask Teamwork.com for
Each one is a real action in the connector. You can switch off the ones you would rather it never used.
| Tool | What it does |
|---|---|
twprojects_list_projects | Lists projects with filters by membership, progress, status or category. |
twprojects_get_project | Returns a project with its details. |
twprojects_search | Searches by keyword across projects, tasks, messages, comments and people. |
twprojects_list_tasklists | Lists the task lists of a project or of the whole site. |
twprojects_list_tasks | Lists tasks filtered by task list, project or the whole site. |
twprojects_get_task | Returns a task with its details. |
twprojects_create_task | Creates a task in a task list. Starts turned off. |
twprojects_update_task | Changes a task. Starts turned off. |
twprojects_complete_task | Marks a task as complete. Starts turned off. |
twprojects_list_comments | Lists the comments of a task, milestone, notebook, link or file. |
twprojects_create_comment | Comments on a task, milestone, notebook, file or link. Starts turned off. |
twprojects_list_timelogs | Lists the time logs of a project, a task or the whole site. |
twprojects_create_timelog | Logs time on a project or a task. |
twdesk_search_tickets | Searches Desk tickets by inbox, customer, company, tag, status, priority or type. |
twdesk_get_ticket | Returns a Desk ticket. |
twdesk_create_ticket | Creates a ticket in Desk and, if asked, sends the customer a copy. Starts turned off. |
twdesk_update_ticket | Changes a Desk ticket. Starts turned off. |
twdesk_reply_ticket | Replies to the customer on a ticket or leaves an internal note for the team. Starts turned off. |
twdesk_link_task_to_ticket | Links a projects task to a Desk ticket so the ticket shows that work. |
twdesk_list_customers | Lists Desk customers, filtered by company or email. |
twdesk_get_customer | Returns a Desk customer. |
twdesk_create_customer | Creates a customer in Desk with their name, email, company and phone. |
The limits
What the Teamwork.com integration does NOT do
We would rather say it here than have you find out during rollout.
-
It does not create tasks or tickets while those actions stay off. The Teamwork server marks them as destructive actions, and in Met they start turned off.
-
It does not delete projects, tasks or records. The Teamwork reference says no published server exposes the delete tools.
-
It does not see more than the connected account can see. Everything goes through that Teamwork.com account's permissions.
-
It does not ask you for confirmation in the chat before writing. The admin chooses which actions stay on.
-
It does not pay your Teamwork.com plan. Usage runs on your account and the products you subscribe to.
Before you start
What you need to connect Teamwork.com
- 1
A Teamwork.com account
Your team's Teamwork.com account, with Teamwork Desk if you will handle tickets. What the Met can see and do depends on that account's permissions.
- 2
Connect it in Met
In Met, open Connections → Teamwork.com → Connect. You sign in to Teamwork.com and approve the permissions it asks for.
- 3
Decide which actions stay on
The workspace admin chooses which actions stay on. Creating and changing tasks, commenting, creating and changing tickets and replying to tickets start turned off.
Frequently asked questions
Questions about Teamwork.com and Meteor
Because the Teamwork server marks it as a destructive action. The admin turns it on in Connections if they want the Met to create tasks.
Yes, if the admin turns on replying to tickets. That tool sends a reply to the customer or leaves an internal note only the team sees.
No. According to the Teamwork reference, published servers do not expose the delete tools.
You do, with your Teamwork.com account and plan. Met does not charge for the calls your Met makes to Teamwork.com.
Step by step
Automations that use Teamwork.com
Complete tasks, with the steps and the tools that run at each one.
Automate and collaborate
Other integrations in the same family
Want to see a Met running Teamwork.com?
We will show you with your own account connected, not with a canned demo.