Skip to main content
Glama

Server Details

The Teamwork.com official MCP server helps teams efficiently manage client projects with AI.

Status
Healthy
Last Tested
Transport
Streamable HTTP
URL
Repository
Teamwork/mcp
GitHub Stars
17
Server Listing
Teamwork

See and control every tool call

Log every tool call with full inputs and outputs
Control which tools are enabled per connector
Manage credentials once, use from any MCP client
Monitor uptime and get alerted when servers go down

Tool Definition Quality

Score is being calculated. Check back soon.

Available Tools

121 tools
twdesk-create_companyInspect

Create a new company in Teamwork Desk by specifying its name, domains, and other attributes. Useful for onboarding new organizations, customizing Desk for business relationships, or adapting support processes.

ParametersJSON Schema
NameRequiredDescriptionDefault
kindNoThe kind of the company.
nameYesThe name of the company.
noteNoThe note for the company.
detailsNoThe details of the company.
domainsNoThe domains for the company.
websiteNoThe website of the company.
industryNoThe industry of the company.
permissionNoThe permission level of the company.
descriptionNoThe description of the company.
twdesk-create_customerInspect

Create a new customer in Teamwork Desk by specifying their name, contact details, and other attributes. Useful for onboarding new clients, customizing Desk for business relationships, or adapting support processes.

ParametersJSON Schema
NameRequiredDescriptionDefault
emailNoThe email of the customer.
notesNoThe notes of the customer.
phoneNoThe phone number of the customer.
mobileNoThe mobile number of the customer.
addressNoThe address of the customer.
jobTitleNoThe job title of the customer.
lastNameNoThe last name of the customer.
extraDataNoThe extra data of the customer.
firstNameNoThe first name of the customer.
facebookURLNoThe Facebook URL of the customer.
linkedinURLNoThe LinkedIn URL of the customer.
organizationNoThe organization of the customer.
twitterHandleNoThe Twitter handle of the customer.
twdesk-create_fileInspect

Upload a new file to Teamwork Desk, enabling attachment to tickets, articles, or other resources.

ParametersJSON Schema
NameRequiredDescriptionDefault
dataYesThe content of the file as a base64-encoded string.
nameYesThe name of the file.
mimeTypeYesThe MIME type of the file.
dispositionNoThe disposition of the file.
twdesk-create_messageInspect

Send a reply message to a ticket in Teamwork Desk by specifying the ticket ID and message body. Useful for automating ticket responses, integrating external communication systems, or customizing support workflows.

ParametersJSON Schema
NameRequiredDescriptionDefault
ccNoAn array of email addresses to CC on message reply.
bccNoAn array of email addresses to BCC on message reply.
bodyYesThe body of the message.
ticketIDYesThe ID of the ticket that the message will be sent to.
twdesk-create_priorityInspect

Create a new priority in Teamwork Desk by specifying its name and color. Useful for customizing ticket workflows, introducing new escalation levels, or adapting Desk to evolving support processes.

ParametersJSON Schema
NameRequiredDescriptionDefault
nameYesThe name of the priority.
colorNoThe color of the priority.
twdesk-create_statusInspect

Create a new status in Teamwork Desk by specifying its name, color, and display order. Useful for customizing ticket workflows, introducing new resolution states, or adapting Desk to evolving support processes.

ParametersJSON Schema
NameRequiredDescriptionDefault
nameYesThe name of the status.
colorNoThe color of the status.
displayOrderNoThe display order of the status.
twdesk-create_tagInspect

Create a new tag in Teamwork Desk by specifying its name and color. Useful for customizing ticket workflows, introducing new categories, or adapting Desk to evolving support processes.

ParametersJSON Schema
NameRequiredDescriptionDefault
nameYesThe name of the tag.
colorNoThe color of the tag.
twdesk-create_ticketInspect

Create a new ticket in Teamwork Desk by specifying subject, description, priority, and status. "Useful for automating ticket creation, integrating external systems, or customizing support workflows.

ParametersJSON Schema
NameRequiredDescriptionDefault
ccNoAn array of email addresses to CC on ticket creation.
bccNoAn array of email addresses to BCC on ticket creation.
bodyYesThe body of the ticket.
tagsNo An array of tag IDs to associate with the ticket. Tag IDs can be found by using the 'twdesk-list_tags' tool.
filesNo An array of file IDs to attach to the ticket. Use the 'twdesk-create_file' tool to upload files.
typeIdNo The type ID of the ticket. Use the 'twdesk-list_types' tool to find valid IDs.
agentIdNo The agent ID that the ticket should be assigned to. Use the 'twdesk-list_agents' tool to find valid IDs.
inboxIdYes The inbox ID of the ticket. Use the 'twdesk-list_inboxes' tool to find valid IDs.
subjectYesThe subject of the ticket.
statusIdNo The status of the ticket. Use the 'twdesk-list_statuses' tool to find valid IDs.
customerIdNo The customer ID of the ticket. Use the 'twdesk-list_customers' tool to find valid IDs.
priorityIdNo The priority of the ticket. Use the 'twdesk-list_priorities' tool to find valid IDs.
customerEmailNo The email address of the customer. This is used to identify the customer in the system. Either the customerId or customerEmail is required to create a ticket. If email is provided we will either find or create the customer.
notifyCustomerNoSet to true if the the customer should be sent a copy of the ticket.
twdesk-create_typeInspect

Create a new ticket type in Teamwork Desk by specifying its name, display order, and future inbox settings. Useful for customizing ticket workflows, introducing new categories, or adapting Desk to evolving support processes.

ParametersJSON Schema
NameRequiredDescriptionDefault
nameYesThe name of the type.
displayOrderNoThe display order of the type.
enabledForFutureInboxesNoWhether the type is enabled for future inboxes.
twdesk-get_company
Read-only
Inspect

Retrieve detailed information about a specific company in Teamwork Desk by its ID. Useful for auditing company records, troubleshooting ticket associations, or integrating Desk company data into automation workflows.

ParametersJSON Schema
NameRequiredDescriptionDefault
idYesThe ID of the company to retrieve.
twdesk-get_customer
Read-only
Inspect

Retrieve detailed information about a specific customer in Teamwork Desk by their ID. Useful for auditing customer records, troubleshooting ticket associations, or integrating Desk customer data into automation workflows.

ParametersJSON Schema
NameRequiredDescriptionDefault
idYesThe ID of the customer to retrieve.
twdesk-get_inbox
Read-only
Inspect

Retrieve detailed information about a specific inbox in Teamwork Desk by its ID

ParametersJSON Schema
NameRequiredDescriptionDefault
idYesThe ID of the inbox to retrieve.
twdesk-get_priority
Read-only
Inspect

Retrieve detailed information about a specific priority in Teamwork Desk by its ID. Useful for inspecting priority attributes, troubleshooting ticket routing, or integrating Desk priority data into automation workflows.

ParametersJSON Schema
NameRequiredDescriptionDefault
idYesThe ID of the priority to retrieve.
twdesk-get_status
Read-only
Inspect

Retrieve detailed information about a specific status in Teamwork Desk by its ID. Useful for auditing status usage, troubleshooting ticket workflows, or integrating Desk status data into automation workflows.

ParametersJSON Schema
NameRequiredDescriptionDefault
idYesThe ID of the status to retrieve.
twdesk-get_tag
Read-only
Inspect

Retrieve detailed information about a specific tag in Teamwork Desk by its ID. Useful for auditing tag usage, troubleshooting ticket categorization, or integrating Desk tag data into automation workflows.

ParametersJSON Schema
NameRequiredDescriptionDefault
idYesThe ID of the tag to retrieve.
twdesk-get_ticket
Read-only
Inspect

Retrieve detailed information about a specific ticket in Teamwork Desk by its ID. Useful for auditing ticket records, troubleshooting support workflows, or integrating Desk ticket data into automation and reporting systems.

ParametersJSON Schema
NameRequiredDescriptionDefault
idYesThe ID of the ticket to retrieve.
twdesk-get_type
Read-only
Inspect

Retrieve detailed information about a specific ticket type in Teamwork Desk by its ID. Useful for auditing type usage, troubleshooting ticket categorization, or integrating Desk type data into automation workflows.

ParametersJSON Schema
NameRequiredDescriptionDefault
idYesThe ID of the type to retrieve.
twdesk-get_user
Read-only
Inspect

Retrieve detailed information about a specific user in Teamwork Desk by their ID. Useful for auditing user records, troubleshooting ticket assignments, or integrating Desk user data into automation workflows.

ParametersJSON Schema
NameRequiredDescriptionDefault
idYesThe ID of the user to retrieve.
twdesk-list_companies
Read-only
Inspect

List all companies in Teamwork Desk, with optional filters for name, domains, and kind. Enables users to audit, analyze, or synchronize company configurations for ticket management, reporting, or integration scenarios.

ParametersJSON Schema
NameRequiredDescriptionDefault
kindNoThe kind of the company to filter by.
nameNoThe name of the company to filter by.
pageNoThe page number to retrieve.
domainsNoThe domains of the company to filter by.
orderByNoThe field to order the results by.
pageSizeNoThe number of results to retrieve per page.
orderDirectionNoThe direction to order the results by (asc, desc).
twdesk-list_customers
Read-only
Inspect

List all customers in Teamwork Desk, with optional filters for company, email, and other attributes. Enables users to audit, analyze, or synchronize customer configurations for ticket management, reporting, or integration scenarios.

ParametersJSON Schema
NameRequiredDescriptionDefault
pageNoThe page number to retrieve.
emailsNoThe emails of the customers to filter by.
orderByNoThe field to order the results by.
pageSizeNoThe number of results to retrieve per page.
companyIDsNoThe IDs of the companies to filter by.
companyNamesNoThe names of the companies to filter by.
orderDirectionNoThe direction to order the results by (asc, desc).
twdesk-list_inboxes
Read-only
Inspect

List all inboxes in Teamwork Desk, with optional filters for name and email.

ParametersJSON Schema
NameRequiredDescriptionDefault
nameNoThe name of the inbox to filter by.
pageNoThe page number to retrieve.
emailNoThe email of the inbox to filter by.
orderByNoThe field to order the results by.
pageSizeNoThe number of results to retrieve per page.
orderDirectionNoThe direction to order the results by (asc, desc).
twdesk-list_priorities
Read-only
Inspect

List all available priorities in Teamwork Desk, with optional filters for name and color. Enables users to audit, analyze, or synchronize priority configurations for ticket management, reporting, or integration scenarios.

ParametersJSON Schema
NameRequiredDescriptionDefault
nameNoThe name of the priority to filter by.
pageNoThe page number to retrieve.
colorNoThe color of the priority to filter by.
orderByNoThe field to order the results by.
pageSizeNoThe number of results to retrieve per page.
orderDirectionNoThe direction to order the results by (asc, desc).
twdesk-list_statuses
Read-only
Inspect

List all statuses in Teamwork Desk, with optional filters for name, color, and code. Enables users to audit, analyze, or synchronize status configurations for ticket management, reporting, or integration scenarios.

ParametersJSON Schema
NameRequiredDescriptionDefault
codeNoThe code of the status to filter by.
nameNoThe name of the status to filter by.
pageNoThe page number to retrieve.
colorNoThe color of the status to filter by.
orderByNoThe field to order the results by.
pageSizeNoThe number of results to retrieve per page.
orderDirectionNoThe direction to order the results by (asc, desc).
twdesk-list_tags
Read-only
Inspect

List all tags in Teamwork Desk, with optional filters for name, color, and inbox association. Enables users to audit, analyze, or synchronize tag configurations for ticket management, reporting, or integration scenarios.

ParametersJSON Schema
NameRequiredDescriptionDefault
nameNoThe name of the tag to filter by.
pageNoThe page number to retrieve.
colorNoThe color of the tag to filter by.
orderByNoThe field to order the results by.
inboxIDsNoThe IDs of the inboxes to filter by.
pageSizeNoThe number of results to retrieve per page.
orderDirectionNoThe direction to order the results by (asc, desc).
twdesk-list_tickets
Read-only
Inspect

List all tickets in Teamwork Desk, with extensive filters for inbox, customer, company, tag, status, priority, SLA, user, and more. Enables users to audit, analyze, or synchronize ticket data for support management, reporting, or integration scenarios.

ParametersJSON Schema
NameRequiredDescriptionDefault
pageNoThe page number to retrieve.
sharedNo Find tickets shared with me outside of inboxes I have access to
slaIDsNo The IDs of the SLAs to filter by. SLA IDs can be found by using the 'twdesk-list_slas' tool.
tagIDsNo The IDs of the tags to filter by. Tag IDs can be found by using the 'twdesk-list_tags' tool.
orderByNoThe field to order the results by.
taskIDsNo The IDs of the tasks to filter by. Task IDs can be found by using the 'twprojects-list_tasks' tool.
userIDsNo The IDs of the users to filter by. User IDs can be found by using the 'twdesk-list_users' tool.
inboxIDsNo The IDs of the inboxes to filter by. Inbox IDs can be found by using the 'twdesk-list_inboxes' tool.
pageSizeNoThe number of results to retrieve per page.
statusIDsNo The IDs of the statuses to filter by. Status IDs can be found by using the 'twdesk-list_statuses' tool.
companyIDsNo The IDs of the companies to filter by. Company IDs can be found by using the 'twdesk-list_companies' tool.
customerIDsNo The IDs of the customers to filter by. Customer IDs can be found by using the 'twdesk-list_customers' tool.
priorityIDsNo The IDs of the priorities to filter by. Priority IDs can be found by using the 'twdesk-list_priorities' tool.
projectsIDsNo The IDs of the projects to filter by. Project IDs can be found by using the 'twprojects-list_projects' tool.
slaBreachedNo Find tickets where the SLA has been breached
orderDirectionNoThe direction to order the results by (asc, desc).
twdesk-list_types
Read-only
Inspect

List all ticket types in Teamwork Desk, with optional filters for name and inbox association. Enables users to audit, analyze, or synchronize type configurations for ticket management, reporting, or integration scenarios.

ParametersJSON Schema
NameRequiredDescriptionDefault
nameNoThe name of the type to filter by.
pageNoThe page number to retrieve.
orderByNoThe field to order the results by.
inboxIDsNoThe inbox IDs of the type to filter by.
pageSizeNoThe number of results to retrieve per page.
orderDirectionNoThe direction to order the results by (asc, desc).
twdesk-list_users
Read-only
Inspect

List all users in Teamwork Desk, with optional filters for name, email, inbox, and part-time status. Enables users to audit, analyze, or synchronize user configurations for support management, reporting, or integration scenarios.

ParametersJSON Schema
NameRequiredDescriptionDefault
pageNoThe page number to retrieve.
emailNoThe email addresses of the users to filter by.
orderByNoThe field to order the results by.
inboxIDsNoThe IDs of the inboxes to filter by.
lastNameNoThe last names of the users to filter by.
pageSizeNoThe number of results to retrieve per page.
firstNameNoThe first names of the users to filter by.
isPartTimeNoWhether to include part-time users in the results.
orderDirectionNoThe direction to order the results by (asc, desc).
twdesk-search_tickets
Read-only
Inspect

Search tickets in Teamwork Desk using various filters including inbox, customer, company, tag, status, priority, SLA, user, and more. This tool enables users to perform targeted searches for tickets, facilitating efficient support management, reporting, and integration with other systems.

ParametersJSON Schema
NameRequiredDescriptionDefault
pageNoThe page number to retrieve.
searchYes The search term to use for finding tickets. This can be part of the subject, body, or other ticket fields.
sharedNo Find tickets shared with me outside of inboxes I have access to
tagIDsNo The IDs of the tags to filter by. Tag IDs can be found by using the 'twdesk-list_tags' tool.
orderByNoThe field to order the results by.
userIDsNo The IDs of the users to filter by. User IDs can be found by using the 'twdesk-list_users' tool.
inboxIDsNo The IDs of the inboxes to filter by. Inbox IDs can be found by using the 'twdesk-list_inboxes' tool.
pageSizeNoThe number of results to retrieve per page.
statusIDsNo The IDs of the statuses to filter by. Status IDs can be found by using the 'twdesk-list_statuses' tool.
companyIDsNo The IDs of the companies to filter by. Company IDs can be found by using the 'twdesk-list_companies' tool.
customerIDsNo The IDs of the customers to filter by. Customer IDs can be found by using the 'twdesk-list_customers' tool.
priorityIDsNo The IDs of the priorities to filter by. Priority IDs can be found by using the 'twdesk-list_priorities' tool.
slaBreachedNo Find tickets where the SLA has been breached
orderDirectionNoThe direction to order the results by (asc, desc).
twdesk-update_companyInspect

Update an existing company in Teamwork Desk by ID, allowing changes to its name, domains, and other attributes. Supports evolving business relationships, rebranding, or correcting company records for improved ticket handling.

ParametersJSON Schema
NameRequiredDescriptionDefault
idYesThe ID of the company to update.
kindNoThe new kind of the company.
nameNoThe new name of the company.
noteNoThe new note for the company.
detailsNoThe new details of the company.
domainsNoThe new domains for the company.
websiteNoThe new website of the company.
industryNoThe new industry of the company.
permissionNoThe new permission level of the company.
descriptionNoThe new description of the company.
twdesk-update_customerInspect

Update an existing customer in Teamwork Desk by ID, allowing changes to their name, contact details, and other attributes. Supports evolving business relationships, correcting customer records, or improving ticket handling.

ParametersJSON Schema
NameRequiredDescriptionDefault
idYesThe ID of the customer to update.
emailNoThe new email of the customer.
notesNoThe new notes of the customer.
phoneNoThe new phone number of the customer.
mobileNoThe new mobile number of the customer.
addressNoThe new address of the customer.
jobTitleNoThe new job title of the customer.
lastNameNoThe new last name of the customer.
extraDataNoThe new extra data of the customer.
firstNameNoThe new first name of the customer.
facebookURLNoThe new Facebook URL of the customer.
linkedinURLNoThe new LinkedIn URL of the customer.
organizationNoThe new organization of the customer.
twitterHandleNoThe new Twitter handle of the customer.
twdesk-update_priorityInspect

Update an existing priority in Teamwork Desk by ID, allowing changes to its name and color. Supports evolving support policies, rebranding, or correcting priority attributes for improved ticket handling.

ParametersJSON Schema
NameRequiredDescriptionDefault
idYesThe ID of the priority to update.
nameNoThe new name of the priority.
colorNoThe color of the priority.
twdesk-update_statusInspect

Update an existing status in Teamwork Desk by ID, allowing changes to its name, color, and display order. Supports evolving support policies, rebranding, or correcting status attributes for improved ticket handling.

ParametersJSON Schema
NameRequiredDescriptionDefault
idYesThe ID of the status to update.
nameNoThe new name of the status.
colorNoThe color of the status.
displayOrderNoThe display order of the status.
twdesk-update_tagInspect

Update an existing tag in Teamwork Desk by ID, allowing changes to its name and color. Supports evolving support policies, rebranding, or correcting tag attributes for improved ticket handling.

ParametersJSON Schema
NameRequiredDescriptionDefault
idYesThe ID of the tag to update.
nameNoThe new name of the tag.
colorNoThe color of the tag.
twdesk-update_ticketInspect

Update an existing ticket in Teamwork Desk by ID, allowing changes to its attributes. Supports evolving support processes, correcting ticket records, or integrating with automation systems for improved ticket handling.

ParametersJSON Schema
NameRequiredDescriptionDefault
ccNoAn array of email addresses to CC on ticket update.
idYesThe ID of the ticket to update.
bccNoAn array of email addresses to BCC on ticket update.
bodyNoThe body of the ticket.
typeIdNo The type ID of the ticket. Use the 'twdesk-list_types' tool to find valid IDs.
agentIdNo The agent ID that the ticket should be assigned to. Use the 'twdesk-list_agents' tool to find valid IDs.
subjectNoThe subject of the ticket.
statusIdNo The status of the ticket. Use the 'twdesk-list_statuses' tool to find valid IDs.
priorityIdNo The priority of the ticket. Use the 'twdesk-list_priorities' tool to find valid IDs.
twdesk-update_typeInspect

Update an existing ticket type in Teamwork Desk by ID, allowing changes to its name, display order, and future inbox settings. Supports evolving support policies, rebranding, or correcting type attributes for improved ticket handling.

ParametersJSON Schema
NameRequiredDescriptionDefault
idYesThe ID of the type to update.
nameNoThe new name of the type.
displayOrderNoThe display order of the type.
enabledForFutureInboxesNoWhether the type is enabled for future inboxes.
twprojects-add_project_memberInspect

Add a user to a project in Teamwork.com. In the context of Teamwork.com, a project member is a user who is assigned to a specific project. Project members can have different roles and permissions within the project, allowing them to collaborate on tasks, view project details, and contribute to the project's success. Managing project members effectively is crucial for ensuring that the right people are involved in the right tasks, and it helps maintain accountability and clarity throughout the project's lifecycle.

ParametersJSON Schema
NameRequiredDescriptionDefault
user_idsNoA list of user IDs to add to the project.
project_idYesThe ID of the project to add the member to.
twprojects-complete_timerInspect

Complete an existing timer in Teamwork.com. Timer is a built-in tool that allows users to accurately track the time they spend working on specific tasks, projects, or client work. Instead of manually recording hours, users can start, pause, and stop timers directly within the platform or through the desktop and mobile apps, ensuring precise time logs without interrupting their workflow. Once recorded, these entries are automatically linked to the relevant task or project, making it easier to monitor productivity, manage billable hours, and generate detailed reports for both internal tracking and client invoicing.

ParametersJSON Schema
NameRequiredDescriptionDefault
idYesThe ID of the timer to complete.
twprojects-create_commentInspect

Create a new comment in Teamwork.com. In the Teamwork.com context, a comment is a way for users to communicate and collaborate directly within tasks, milestones, files, or other project items. Comments allow team members to provide updates, ask questions, give feedback, or share relevant information in a centralized and contextual manner. They support rich text formatting, file attachments, and @mentions to notify specific users or teams, helping keep discussions organized and easily accessible within the project. Comments are visible to all users with access to the item, promoting transparency and keeping everyone aligned.

ParametersJSON Schema
NameRequiredDescriptionDefault
bodyYesThe content of the comment. The content can be added as text or HTML.
objectYesThe object to create the comment for. It can be a tasks, milestones, files or notebooks.
content_typeNoThe content type of the comment. It can be either 'TEXT' or 'HTML'.
twprojects-create_companyInspect

Create a new company in Teamwork.com. In the context of Teamwork.com, a company represents an organization or business entity that can be associated with users, projects, and tasks within the platform, and it is often referred to as a “client.” It serves as a way to group related users and projects under a single organizational umbrella, making it easier to manage permissions, assign responsibilities, and organize work. Companies (or clients) are frequently used to distinguish between internal teams and external collaborators, enabling teams to work efficiently while maintaining clear boundaries around ownership, visibility, and access levels across different projects.

ParametersJSON Schema
NameRequiredDescriptionDefault
faxNoThe fax number of the company.
zipNoThe ZIP or postal code of the company.
cityNoThe city of the company.
nameYesThe name of the company.
phoneNoThe phone number of the company.
stateNoThe state of the company.
profileNoA profile description for the company.
tag_idsNoA list of tag IDs to associate with the company.
websiteNoThe website of the company.
email_oneNoThe primary email address of the company.
email_twoNoThe secondary email address of the company.
manager_idNoThe ID of the user who manages the company.
address_oneNoThe first line of the address of the company.
address_twoNoThe second line of the address of the company.
email_threeNoThe tertiary email address of the company.
industry_idNoThe ID of the industry the company belongs to.
country_codeNoThe country code of the company, e.g., 'US' for the United States.
twprojects-create_jobroleInspect

Create a new job role in Teamwork.com. Job role defines a user's primary function or position within the organization, such as developer, designer, project manager, or account manager. It provides high-level context about what a person is generally responsible for, helping teams understand who does what across projects and departments. Job roles are commonly used in resource planning, capacity forecasting, and reporting, allowing managers to group work by role, plan future demand more accurately, and ensure the right mix of roles is available to deliver projects efficiently.

ParametersJSON Schema
NameRequiredDescriptionDefault
nameYesThe name of the job role.
twprojects-create_milestoneInspect

Create a new milestone in Teamwork.com. In the context of Teamwork.com, a milestone represents a significant point or goal within a project that marks the completion of a major phase or a key deliverable. It acts as a high-level indicator of progress, helping teams track whether work is advancing according to plan. Milestones are typically used to coordinate efforts across different tasks and task lists, providing a clear deadline or objective that multiple team members or departments can align around. They don't contain individual tasks themselves but serve as checkpoints to ensure the project is moving in the right direction.

ParametersJSON Schema
NameRequiredDescriptionDefault
nameYesThe name of the milestone.
tag_idsNoA list of tag IDs to associate with the milestone.
due_dateYesThe due date of the milestone in the format YYYYMMDD. This date will be used in all tasks without a due date related to this milestone.
assigneesYesAn object containing assignees for the milestone. MUST contain at least one of: user_ids, company_ids or team_ids with non-empty arrays.
project_idYesThe ID of the project to create the milestone in.
descriptionNoA description of the milestone.
tasklist_idsNoA list of tasklist IDs to associate with the milestone.
twprojects-create_notebookInspect

Create a new notebook in Teamwork.com. Notebook is a space where teams can create, share, and organize written content in a structured way. It’s commonly used for documenting processes, storing meeting notes, capturing research, or drafting ideas that need to be revisited and refined over time. Unlike quick messages or task comments, notebooks provide a more permanent and organized format that can be easily searched and referenced, helping teams maintain a centralized source of knowledge and ensuring important information remains accessible to everyone who needs it.

ParametersJSON Schema
NameRequiredDescriptionDefault
nameYesThe name of the notebook.
typeYesThe type of the notebook. Valid values are 'MARKDOWN' and 'HTML'.
tag_idsNoA list of tag IDs to associate with the notebook.
contentsYesThe contents of the notebook.
project_idYesThe ID of the project to create the notebook in.
descriptionNoA description of the notebook.
twprojects-create_projectInspect

Create a new project in Teamwork.com. The project feature in Teamwork.com serves as the central workspace for organizing and managing a specific piece of work or initiative. Each project provides a dedicated area where teams can plan tasks, assign responsibilities, set deadlines, and track progress toward shared goals. Projects include tools for communication, file sharing, milestones, and time tracking, allowing teams to stay aligned and informed throughout the entire lifecycle of the work. Whether it's a product launch, client engagement, or internal initiative, projects in Teamwork.com help teams structure their efforts, collaborate more effectively, and deliver results with greater visibility and accountability.

ParametersJSON Schema
NameRequiredDescriptionDefault
nameYesThe name of the project.
end_atNoThe end date of the project in the format YYYYMMDD.
tag_idsNoA list of tag IDs to associate with the project.
owned_idNoThe ID of the user who owns the project.
start_atNoThe start date of the project in the format YYYYMMDD.
company_idNoThe ID of the company associated with the project.
category_idNoThe ID of the category to which the project belongs.
descriptionNoThe description of the project.
twprojects-create_project_categoryInspect

Create a new project category in Teamwork.com. The project category is a way to group and label related projects so teams can organize their work more clearly across the platform. By assigning a category, you create a higher-level structure that makes it easier to filter, report on, and navigate multiple projects, ensuring that departments, workflows, or strategic areas remain neatly aligned and easier to manage.

ParametersJSON Schema
NameRequiredDescriptionDefault
nameYesThe name of the project category.
colorNoThe color of the project category in hex format (e.g., #FF5733).
parent_idNoThe ID of the parent project category, if any. This allows for nested categories.
twprojects-create_project_templateInspect

Create a new project template in Teamwork.com. The project template is a reusable project structure designed to standardize workflows and streamline project setup. It typically includes predefined tasks, task lists, milestones, and timelines that reflect a repeatable process, allowing teams to quickly spin up new projects with consistent organization, clear responsibilities, and efficient execution from the start.

ParametersJSON Schema
NameRequiredDescriptionDefault
nameYesThe name of the project template.
end_atNoThe end date of the project template in the format YYYYMMDD.
tag_idsNoA list of tag IDs to associate with the project template.
owned_idNoThe ID of the user who owns the project template.
start_atNoThe start date of the project template in the format YYYYMMDD.
company_idNoThe ID of the company associated with the project template.
category_idNoThe ID of the category to which the project template belongs.
descriptionNoThe description of the project template.
twprojects-create_skillInspect

Create a new skill in Teamwork.com. Skill represents a specific capability, area of expertise, or proficiency that can be assigned to users to describe what they are good at or qualified to work on. Skills help teams understand the strengths available across the organization and make it easier to match the right skills to the right work when planning projects, assigning tasks, or managing resources. By associating skills with users and leveraging them in planning and reporting, Teamwork enables more effective workload distribution, better project outcomes, and clearer visibility into whether the team has the capabilities needed to deliver upcoming work.

ParametersJSON Schema
NameRequiredDescriptionDefault
nameYesThe name of the skill.
user_idsNoThe user IDs associated with the skill.
twprojects-create_tagInspect

Create a new tag in Teamwork.com. In the context of Teamwork.com, a tag is a customizable label that can be applied to various items such as tasks, projects, milestones, messages, and more, to help categorize and organize work efficiently. Tags provide a flexible way to filter, search, and group related items across the platform, making it easier for teams to manage complex workflows, highlight priorities, or track themes and statuses. Since tags are user-defined, they adapt to each team’s specific needs and can be color-coded for better visual clarity.

ParametersJSON Schema
NameRequiredDescriptionDefault
nameYesThe name of the tag. It must have less than 50 characters.
project_idNoThe ID of the project to associate the tag with. This is for project-scoped tags.
twprojects-create_taskInspect

Create a new task in Teamwork.com. In Teamwork.com, a task represents an individual unit of work assigned to one or more team members within a project. Each task can include details such as a title, description, priority, estimated time, assignees, and due date, along with the ability to attach files, leave comments, track time, and set dependencies on other tasks. Tasks are organized within task lists, helping structure and sequence work logically. They serve as the building blocks of project management in Teamwork, allowing teams to collaborate, monitor progress, and ensure accountability throughout the project's lifecycle.

ParametersJSON Schema
NameRequiredDescriptionDefault
nameYesThe name of the task.
tag_idsNoA list of tag IDs to assign to the task.
due_dateNoThe due date of the task in ISO 8601 format (YYYY-MM-DD). When this is not provided, it will fallback to the milestone due date if a milestone is set.
priorityNoThe priority of the task. Possible values are: low, medium, high.
progressNoThe progress of the task, as a percentage (0-100). Only whole numbers are allowed.
assigneesNoAn object containing assignees for the task.
start_dateNoThe start date of the task in ISO 8601 format (YYYY-MM-DD).
descriptionNoThe description of the task.
tasklist_idYesThe ID of the tasklist. If you only have the project's name, use the twprojects-list_projects method with the search_term parameter to find the project ID, and then the twprojects-list_tasklists method with the project_id to choose the tasklist ID. If you know the tasklist's name, you may also use the search_term parameter with the twprojects-list_tasklists method to find the tasklist ID.
predecessorsNoList of task dependencies that must be completed before this task can start, defining its position in the project workflow and ensuring proper sequencing of work.
parent_task_idNoThe ID of the parent task if creating a subtask.
estimated_minutesNoThe estimated time to complete the task in minutes.
twprojects-create_tasklistInspect

Create a new tasklist in Teamwork.com. In the context of Teamwork.com, a task list is a way to group related tasks within a project, helping teams organize their work into meaningful sections such as phases, categories, or deliverables. Each task list belongs to a specific project and can include multiple tasks that are typically aligned with a common goal. Task lists can be associated with milestones, and they support privacy settings that control who can view or interact with the tasks they contain. This structure helps teams manage progress, assign responsibilities, and maintain clarity across complex projects.

ParametersJSON Schema
NameRequiredDescriptionDefault
nameYesThe name of the tasklist.
project_idYesThe ID of the project to create the tasklist in.
descriptionNoThe description of the tasklist.
milestone_idNoThe ID of the milestone to associate with the tasklist.
twprojects-create_teamInspect

Create a new team in Teamwork.com. In the context of Teamwork.com, a team is a group of users who are organized together to collaborate more efficiently on projects and tasks. Teams help structure work by grouping individuals with similar roles, responsibilities, or departmental functions, making it easier to assign work, track progress, and manage communication. By using teams, organizations can streamline project planning and ensure the right people are involved in the right parts of a project, enhancing clarity and accountability across the platform.

ParametersJSON Schema
NameRequiredDescriptionDefault
nameYesThe name of the team.
handleNoThe handle of the team. It is a unique identifier for the team. It must not have spaces or special characters.
user_idsNoA list of user IDs to add to the team.
company_idNoThe ID of the company. This is used to create a team scoped for a specific company.
project_idNoThe ID of the project. This is used to create a team scoped for a specific project.
descriptionNoThe description of the team.
parent_team_idNoThe ID of the parent team. This is used to create a hierarchy of teams.
twprojects-create_timelogInspect

Create a new timelog in Teamwork.com. Timelog refers to a recorded entry that tracks the amount of time a person has spent working on a specific task, project, or piece of work. These entries typically include details such as the duration of time worked, the date and time it was logged, who logged it, and any optional notes describing what was done during that period. Timelogs are essential for understanding how time is being allocated across projects, enabling teams to manage resources more effectively, invoice clients accurately, and assess productivity. They can be created manually or with timers, and are often used for reporting and billing purposes.

ParametersJSON Schema
NameRequiredDescriptionDefault
dateYesThe date of the timelog in the format YYYY-MM-DD.
timeYesThe time of the timelog in the format HH:MM:SS.
hoursYesThe number of hours spent on the timelog. Must be a positive integer.
is_utcNoIf true, the time is in UTC. Defaults to false.
minutesYesThe number of minutes spent on the timelog. Must be a positive integer less than 60, otherwise the hours attribute should be incremented.
tag_idsNoA list of tag IDs to associate with the timelog.
task_idNoThe ID of the task to associate the timelog with. Either project_id or task_id must be provided, but not both.
user_idNoThe ID of the user to associate the timelog with. Defaults to the authenticated user if not provided.
billableNoIf true, the timelog is billable. Defaults to false.
project_idNoThe ID of the project to associate the timelog with. Either project_id or task_id must be provided, but not both.
descriptionNoA description of the timelog.
twprojects-create_timerInspect

Create a new timer in Teamwork.com. Timer is a built-in tool that allows users to accurately track the time they spend working on specific tasks, projects, or client work. Instead of manually recording hours, users can start, pause, and stop timers directly within the platform or through the desktop and mobile apps, ensuring precise time logs without interrupting their workflow. Once recorded, these entries are automatically linked to the relevant task or project, making it easier to monitor productivity, manage billable hours, and generate detailed reports for both internal tracking and client invoicing.

ParametersJSON Schema
NameRequiredDescriptionDefault
runningNoIf true, the timer will start running immediately.
secondsNoThe number of seconds to set the timer for.
task_idNoThe ID of the task to associate the timer with.
billableNoIf true, the timer is billable. Defaults to false.
project_idYesThe ID of the project to associate the timer with.
descriptionNoA description of the timer.
stop_running_timersNoIf true, any other running timers will be stopped when this timer is created.
twprojects-create_userInspect

Create a new user in Teamwork.com. A user is an individual who has access to one or more projects within a Teamwork site, typically as a team member, collaborator, or administrator. Users can be assigned tasks, participate in discussions, log time, share files, and interact with other members depending on their permission levels. Each user has a unique profile that defines their role, visibility, and access to features and project data. Users can belong to clients/companies or teams within the system, and their permissions can be customized to control what actions they can perform or what information they can see.

ParametersJSON Schema
NameRequiredDescriptionDefault
typeNoThe type of user, such as 'account', 'collaborator', or 'contact'.
adminNoIndicates whether the user is an administrator.
emailYesThe email address of the user.
titleNoThe job title of the user, such as 'Project Manager' or 'Senior Software Developer'.
last_nameYesThe last name of the user.
company_idNoThe ID of the client/company to which the user belongs.
first_nameYesThe first name of the user.
twprojects-get_comment
Read-only
Inspect

Get an existing comment in Teamwork.com. In the Teamwork.com context, a comment is a way for users to communicate and collaborate directly within tasks, milestones, files, or other project items. Comments allow team members to provide updates, ask questions, give feedback, or share relevant information in a centralized and contextual manner. They support rich text formatting, file attachments, and @mentions to notify specific users or teams, helping keep discussions organized and easily accessible within the project. Comments are visible to all users with access to the item, promoting transparency and keeping everyone aligned.

ParametersJSON Schema
NameRequiredDescriptionDefault
idYesThe ID of the comment to get.

Output Schema

ParametersJSON Schema
NameRequiredDescription
commentsYes
twprojects-get_company
Read-only
Inspect

Get an existing company in Teamwork.com. In the context of Teamwork.com, a company represents an organization or business entity that can be associated with users, projects, and tasks within the platform, and it is often referred to as a “client.” It serves as a way to group related users and projects under a single organizational umbrella, making it easier to manage permissions, assign responsibilities, and organize work. Companies (or clients) are frequently used to distinguish between internal teams and external collaborators, enabling teams to work efficiently while maintaining clear boundaries around ownership, visibility, and access levels across different projects.

ParametersJSON Schema
NameRequiredDescriptionDefault
idYesThe ID of the company to get.

Output Schema

ParametersJSON Schema
NameRequiredDescription
companyYes
twprojects-get_jobrole
Read-only
Inspect

Get an existing job role in Teamwork.com. Job role defines a user's primary function or position within the organization, such as developer, designer, project manager, or account manager. It provides high-level context about what a person is generally responsible for, helping teams understand who does what across projects and departments. Job roles are commonly used in resource planning, capacity forecasting, and reporting, allowing managers to group work by role, plan future demand more accurately, and ensure the right mix of roles is available to deliver projects efficiently.

ParametersJSON Schema
NameRequiredDescriptionDefault
idYesThe ID of the job role to get.

Output Schema

ParametersJSON Schema
NameRequiredDescription
jobRoleYes
twprojects-get_milestone
Read-only
Inspect

Get an existing milestone in Teamwork.com. In the context of Teamwork.com, a milestone represents a significant point or goal within a project that marks the completion of a major phase or a key deliverable. It acts as a high-level indicator of progress, helping teams track whether work is advancing according to plan. Milestones are typically used to coordinate efforts across different tasks and task lists, providing a clear deadline or objective that multiple team members or departments can align around. They don't contain individual tasks themselves but serve as checkpoints to ensure the project is moving in the right direction.

ParametersJSON Schema
NameRequiredDescriptionDefault
idYesThe ID of the milestone to get.

Output Schema

ParametersJSON Schema
NameRequiredDescription
milestoneYes
twprojects-get_notebook
Read-only
Inspect

Get an existing notebook in Teamwork.com. Notebook is a space where teams can create, share, and organize written content in a structured way. It’s commonly used for documenting processes, storing meeting notes, capturing research, or drafting ideas that need to be revisited and refined over time. Unlike quick messages or task comments, notebooks provide a more permanent and organized format that can be easily searched and referenced, helping teams maintain a centralized source of knowledge and ensuring important information remains accessible to everyone who needs it.

ParametersJSON Schema
NameRequiredDescriptionDefault
idYesThe ID of the notebook to get.

Output Schema

ParametersJSON Schema
NameRequiredDescription
notebookYes
twprojects-get_project
Read-only
Inspect

Get an existing project in Teamwork.com. The project feature in Teamwork.com serves as the central workspace for organizing and managing a specific piece of work or initiative. Each project provides a dedicated area where teams can plan tasks, assign responsibilities, set deadlines, and track progress toward shared goals. Projects include tools for communication, file sharing, milestones, and time tracking, allowing teams to stay aligned and informed throughout the entire lifecycle of the work. Whether it's a product launch, client engagement, or internal initiative, projects in Teamwork.com help teams structure their efforts, collaborate more effectively, and deliver results with greater visibility and accountability.

ParametersJSON Schema
NameRequiredDescriptionDefault
idYesThe ID of the project to get.

Output Schema

ParametersJSON Schema
NameRequiredDescription
projectYes
twprojects-get_project_category
Read-only
Inspect

Get an existing project category in Teamwork.com. The project category is a way to group and label related projects so teams can organize their work more clearly across the platform. By assigning a category, you create a higher-level structure that makes it easier to filter, report on, and navigate multiple projects, ensuring that departments, workflows, or strategic areas remain neatly aligned and easier to manage.

ParametersJSON Schema
NameRequiredDescriptionDefault
idYesThe ID of the project category to get.

Output Schema

ParametersJSON Schema
NameRequiredDescription
projectCategoryYes
twprojects-get_skill
Read-only
Inspect

Get an existing skill in Teamwork.com. Skill represents a specific capability, area of expertise, or proficiency that can be assigned to users to describe what they are good at or qualified to work on. Skills help teams understand the strengths available across the organization and make it easier to match the right skills to the right work when planning projects, assigning tasks, or managing resources. By associating skills with users and leveraging them in planning and reporting, Teamwork enables more effective workload distribution, better project outcomes, and clearer visibility into whether the team has the capabilities needed to deliver upcoming work.

ParametersJSON Schema
NameRequiredDescriptionDefault
idYesThe ID of the skill to get.

Output Schema

ParametersJSON Schema
NameRequiredDescription
skillYes
twprojects-get_tag
Read-only
Inspect

Get an existing tag in Teamwork.com. In the context of Teamwork.com, a tag is a customizable label that can be applied to various items such as tasks, projects, milestones, messages, and more, to help categorize and organize work efficiently. Tags provide a flexible way to filter, search, and group related items across the platform, making it easier for teams to manage complex workflows, highlight priorities, or track themes and statuses. Since tags are user-defined, they adapt to each team’s specific needs and can be color-coded for better visual clarity.

ParametersJSON Schema
NameRequiredDescriptionDefault
idYesThe ID of the tag to get.

Output Schema

ParametersJSON Schema
NameRequiredDescription
tagYes
twprojects-get_task
Read-only
Inspect

Get an existing task in Teamwork.com. In Teamwork.com, a task represents an individual unit of work assigned to one or more team members within a project. Each task can include details such as a title, description, priority, estimated time, assignees, and due date, along with the ability to attach files, leave comments, track time, and set dependencies on other tasks. Tasks are organized within task lists, helping structure and sequence work logically. They serve as the building blocks of project management in Teamwork, allowing teams to collaborate, monitor progress, and ensure accountability throughout the project's lifecycle.

ParametersJSON Schema
NameRequiredDescriptionDefault
idYesThe ID of the task to get.

Output Schema

ParametersJSON Schema
NameRequiredDescription
taskYes
twprojects-get_tasklist
Read-only
Inspect

Get an existing tasklist in Teamwork.com. In the context of Teamwork.com, a task list is a way to group related tasks within a project, helping teams organize their work into meaningful sections such as phases, categories, or deliverables. Each task list belongs to a specific project and can include multiple tasks that are typically aligned with a common goal. Task lists can be associated with milestones, and they support privacy settings that control who can view or interact with the tasks they contain. This structure helps teams manage progress, assign responsibilities, and maintain clarity across complex projects.

ParametersJSON Schema
NameRequiredDescriptionDefault
idYesThe ID of the tasklist to get.

Output Schema

ParametersJSON Schema
NameRequiredDescription
tasklistYes
twprojects-get_team
Read-only
Inspect

Get an existing team in Teamwork.com. In the context of Teamwork.com, a team is a group of users who are organized together to collaborate more efficiently on projects and tasks. Teams help structure work by grouping individuals with similar roles, responsibilities, or departmental functions, making it easier to assign work, track progress, and manage communication. By using teams, organizations can streamline project planning and ensure the right people are involved in the right parts of a project, enhancing clarity and accountability across the platform.

ParametersJSON Schema
NameRequiredDescriptionDefault
idYesThe ID of the team to get.

Output Schema

ParametersJSON Schema
NameRequiredDescription
teamYes
twprojects-get_timelog
Read-only
Inspect

Get an existing timelog in Teamwork.com. Timelog refers to a recorded entry that tracks the amount of time a person has spent working on a specific task, project, or piece of work. These entries typically include details such as the duration of time worked, the date and time it was logged, who logged it, and any optional notes describing what was done during that period. Timelogs are essential for understanding how time is being allocated across projects, enabling teams to manage resources more effectively, invoice clients accurately, and assess productivity. They can be created manually or with timers, and are often used for reporting and billing purposes.

ParametersJSON Schema
NameRequiredDescriptionDefault
idYesThe ID of the timelog to get.

Output Schema

ParametersJSON Schema
NameRequiredDescription
timelogYes
twprojects-get_timer
Read-only
Inspect

Get an existing timer in Teamwork.com. Timer is a built-in tool that allows users to accurately track the time they spend working on specific tasks, projects, or client work. Instead of manually recording hours, users can start, pause, and stop timers directly within the platform or through the desktop and mobile apps, ensuring precise time logs without interrupting their workflow. Once recorded, these entries are automatically linked to the relevant task or project, making it easier to monitor productivity, manage billable hours, and generate detailed reports for both internal tracking and client invoicing.

ParametersJSON Schema
NameRequiredDescriptionDefault
idYesThe ID of the timer to get.

Output Schema

ParametersJSON Schema
NameRequiredDescription
timerYes
twprojects-get_user
Read-only
Inspect

Get an existing user in Teamwork.com. A user is an individual who has access to one or more projects within a Teamwork site, typically as a team member, collaborator, or administrator. Users can be assigned tasks, participate in discussions, log time, share files, and interact with other members depending on their permission levels. Each user has a unique profile that defines their role, visibility, and access to features and project data. Users can belong to clients/companies or teams within the system, and their permissions can be customized to control what actions they can perform or what information they can see.

ParametersJSON Schema
NameRequiredDescriptionDefault
idYesThe ID of the user to get.

Output Schema

ParametersJSON Schema
NameRequiredDescription
personYes
twprojects-get_user_me
Read-only
Inspect

Get the logged user in Teamwork.com. A user is an individual who has access to one or more projects within a Teamwork site, typically as a team member, collaborator, or administrator. Users can be assigned tasks, participate in discussions, log time, share files, and interact with other members depending on their permission levels. Each user has a unique profile that defines their role, visibility, and access to features and project data. Users can belong to clients/companies or teams within the system, and their permissions can be customized to control what actions they can perform or what information they can see.

ParametersJSON Schema
NameRequiredDescriptionDefault

No parameters

Output Schema

ParametersJSON Schema
NameRequiredDescription
personYes
twprojects-list_activities
Read-only
Inspect

List activities in Teamwork.com. Activity is a record of actions and updates that occur across your projects, tasks, and communications, giving you a clear view of what’s happening within your workspace. Activities capture changes such as task completions, activities added, files uploaded, or milestones updated, and present them in a chronological feed so teams can stay aligned without needing to check each individual project or task. This stream of information helps improve transparency, ensures accountability, and keeps everyone aware of progress and decisions as they happen.

ParametersJSON Schema
NameRequiredDescriptionDefault
pageNoPage number for pagination of results.
end_dateNoEnd date to filter activities. The date format follows RFC3339 - YYYY-MM-DDTHH:MM:SSZ.
page_sizeNoNumber of results per page for pagination.
start_dateNoStart date to filter activities. The date format follows RFC3339 - YYYY-MM-DDTHH:MM:SSZ.
log_item_typesNoFilter activities by item types.

Output Schema

ParametersJSON Schema
NameRequiredDescription
metaYes
activitiesYes
twprojects-list_activities_by_project
Read-only
Inspect

List activities in Teamwork.com by project. Activity is a record of actions and updates that occur across your projects, tasks, and communications, giving you a clear view of what’s happening within your workspace. Activities capture changes such as task completions, activities added, files uploaded, or milestones updated, and present them in a chronological feed so teams can stay aligned without needing to check each individual project or task. This stream of information helps improve transparency, ensures accountability, and keeps everyone aware of progress and decisions as they happen.

ParametersJSON Schema
NameRequiredDescriptionDefault
pageNoPage number for pagination of results.
end_dateNoEnd date to filter activities. The date format follows RFC3339 - YYYY-MM-DDTHH:MM:SSZ.
page_sizeNoNumber of results per page for pagination.
project_idNoThe ID of the project to retrieve activities from.
start_dateNoStart date to filter activities. The date format follows RFC3339 - YYYY-MM-DDTHH:MM:SSZ.
log_item_typesNoFilter activities by item types.

Output Schema

ParametersJSON Schema
NameRequiredDescription
metaYes
activitiesYes
twprojects-list_comments
Read-only
Inspect

List comments in Teamwork.com. In the Teamwork.com context, a comment is a way for users to communicate and collaborate directly within tasks, milestones, files, or other project items. Comments allow team members to provide updates, ask questions, give feedback, or share relevant information in a centralized and contextual manner. They support rich text formatting, file attachments, and @mentions to notify specific users or teams, helping keep discussions organized and easily accessible within the project. Comments are visible to all users with access to the item, promoting transparency and keeping everyone aligned.

ParametersJSON Schema
NameRequiredDescriptionDefault
pageNoPage number for pagination of results.
page_sizeNoNumber of results per page for pagination.
search_termNoA search term to filter comments by name.
updated_afterNoFilter comments updated after this date and time. The date format follows RFC3339 - YYYY-MM-DDTHH:MM:SSZ. By default it will only return comments updated on the last 3 months.

Output Schema

ParametersJSON Schema
NameRequiredDescription
metaYes
commentsYes
twprojects-list_comments_by_file_version
Read-only
Inspect

List comments in Teamwork.com by file version. In the Teamwork.com context, a comment is a way for users to communicate and collaborate directly within tasks, milestones, files, or other project items. Comments allow team members to provide updates, ask questions, give feedback, or share relevant information in a centralized and contextual manner. They support rich text formatting, file attachments, and @mentions to notify specific users or teams, helping keep discussions organized and easily accessible within the project. Comments are visible to all users with access to the item, promoting transparency and keeping everyone aligned.

ParametersJSON Schema
NameRequiredDescriptionDefault
pageNoPage number for pagination of results.
page_sizeNoNumber of results per page for pagination.
search_termNoA search term to filter comments by name.
updated_afterNoFilter comments updated after this date and time. The date format follows RFC3339 - YYYY-MM-DDTHH:MM:SSZ. By default it will only return comments updated on the last 3 months.
file_version_idYesThe ID of the file version to retrieve comments for. Each file can have multiple versions, and comments can be associated with specific versions.

Output Schema

ParametersJSON Schema
NameRequiredDescription
metaYes
commentsYes
twprojects-list_comments_by_milestone
Read-only
Inspect

List comments in Teamwork.com by milestone. In the Teamwork.com context, a comment is a way for users to communicate and collaborate directly within tasks, milestones, files, or other project items. Comments allow team members to provide updates, ask questions, give feedback, or share relevant information in a centralized and contextual manner. They support rich text formatting, file attachments, and @mentions to notify specific users or teams, helping keep discussions organized and easily accessible within the project. Comments are visible to all users with access to the item, promoting transparency and keeping everyone aligned.

ParametersJSON Schema
NameRequiredDescriptionDefault
pageNoPage number for pagination of results.
page_sizeNoNumber of results per page for pagination.
search_termNoA search term to filter comments by name.
milestone_idYesThe ID of the milestone to retrieve comments for.
updated_afterNoFilter comments updated after this date and time. The date format follows RFC3339 - YYYY-MM-DDTHH:MM:SSZ. By default it will only return comments updated on the last 3 months.

Output Schema

ParametersJSON Schema
NameRequiredDescription
metaYes
commentsYes
twprojects-list_comments_by_notebook
Read-only
Inspect

List comments in Teamwork.com by notebook. In the Teamwork.com context, a comment is a way for users to communicate and collaborate directly within tasks, milestones, files, or other project items. Comments allow team members to provide updates, ask questions, give feedback, or share relevant information in a centralized and contextual manner. They support rich text formatting, file attachments, and @mentions to notify specific users or teams, helping keep discussions organized and easily accessible within the project. Comments are visible to all users with access to the item, promoting transparency and keeping everyone aligned.

ParametersJSON Schema
NameRequiredDescriptionDefault
pageNoPage number for pagination of results.
page_sizeNoNumber of results per page for pagination.
notebook_idYesThe ID of the notebook to retrieve comments for.
search_termNoA search term to filter comments by name.
updated_afterNoFilter comments updated after this date and time. The date format follows RFC3339 - YYYY-MM-DDTHH:MM:SSZ. By default it will only return comments updated on the last 3 months.

Output Schema

ParametersJSON Schema
NameRequiredDescription
metaYes
commentsYes
twprojects-list_comments_by_task
Read-only
Inspect

List comments in Teamwork.com by task. In the Teamwork.com context, a comment is a way for users to communicate and collaborate directly within tasks, milestones, files, or other project items. Comments allow team members to provide updates, ask questions, give feedback, or share relevant information in a centralized and contextual manner. They support rich text formatting, file attachments, and @mentions to notify specific users or teams, helping keep discussions organized and easily accessible within the project. Comments are visible to all users with access to the item, promoting transparency and keeping everyone aligned.

ParametersJSON Schema
NameRequiredDescriptionDefault
pageNoPage number for pagination of results.
task_idYesThe ID of the task to retrieve comments for.
page_sizeNoNumber of results per page for pagination.
search_termNoA search term to filter comments by name.
updated_afterNoFilter comments updated after this date and time. The date format follows RFC3339 - YYYY-MM-DDTHH:MM:SSZ. By default it will only return comments updated on the last 3 months.

Output Schema

ParametersJSON Schema
NameRequiredDescription
metaYes
commentsYes
twprojects-list_companies
Read-only
Inspect

List companies in Teamwork.com. In the context of Teamwork.com, a company represents an organization or business entity that can be associated with users, projects, and tasks within the platform, and it is often referred to as a “client.” It serves as a way to group related users and projects under a single organizational umbrella, making it easier to manage permissions, assign responsibilities, and organize work. Companies (or clients) are frequently used to distinguish between internal teams and external collaborators, enabling teams to work efficiently while maintaining clear boundaries around ownership, visibility, and access levels across different projects.

ParametersJSON Schema
NameRequiredDescriptionDefault
pageNoPage number for pagination of results.
tag_idsNoA list of tag IDs to filter companies by tags
page_sizeNoNumber of results per page for pagination.
search_termNoA search term to filter companies by name. Each word from the search term is used to match against the company name.
match_all_tagsNoIf true, the search will match companies that have all the specified tags. If false, the search will match companies that have any of the specified tags. Defaults to false.

Output Schema

ParametersJSON Schema
NameRequiredDescription
metaYes
companiesYes
twprojects-list_industries
Read-only
Inspect

List industries in Teamwork.com. Industry refers to the business sector or market category that a company belongs to, such as technology, healthcare, finance, or education. It helps provide context about the nature of a company's work and can be used to better organize and filter data across the platform. By associating companies and projects with specific industries, Teamwork.com allows teams to gain clearer insights, tailor communication, and segment information in ways that make it easier to manage relationships and understand the broader business landscape in which their clients and partners operate.

ParametersJSON Schema
NameRequiredDescriptionDefault

No parameters

Output Schema

ParametersJSON Schema
NameRequiredDescription
industriesYes
twprojects-list_jobroles
Read-only
Inspect

List job roles in Teamwork.com. Job role defines a user's primary function or position within the organization, such as developer, designer, project manager, or account manager. It provides high-level context about what a person is generally responsible for, helping teams understand who does what across projects and departments. Job roles are commonly used in resource planning, capacity forecasting, and reporting, allowing managers to group work by role, plan future demand more accurately, and ensure the right mix of roles is available to deliver projects efficiently.

ParametersJSON Schema
NameRequiredDescriptionDefault
pageNoPage number for pagination of results.
page_sizeNoNumber of results per page for pagination.
search_termNoA search term to filter job roles by name, or assigned users. The job role will be selected if each word of the term matches the name, or assigned user first or last name, not requiring that the word matches are in the same field.

Output Schema

ParametersJSON Schema
NameRequiredDescription
metaYes
jobRolesYes
twprojects-list_milestones
Read-only
Inspect

List milestones in Teamwork.com. In the context of Teamwork.com, a milestone represents a significant point or goal within a project that marks the completion of a major phase or a key deliverable. It acts as a high-level indicator of progress, helping teams track whether work is advancing according to plan. Milestones are typically used to coordinate efforts across different tasks and task lists, providing a clear deadline or objective that multiple team members or departments can align around. They don't contain individual tasks themselves but serve as checkpoints to ensure the project is moving in the right direction.

ParametersJSON Schema
NameRequiredDescriptionDefault
pageNoPage number for pagination of results.
tag_idsNoA list of tag IDs to filter milestones by tags
page_sizeNoNumber of results per page for pagination.
search_termNoA search term to filter milestones by name. Each word from the search term is used to match against the milestone name and description. The milestone will be selected if each word of the term matches the milestone name or description, not requiring that the word matches are in the same field.
match_all_tagsNoIf true, the search will match milestones that have all the specified tags. If false, the search will match milestones that have any of the specified tags. Defaults to false.

Output Schema

ParametersJSON Schema
NameRequiredDescription
metaYes
milestonesYes
twprojects-list_milestones_by_project
Read-only
Inspect

List milestones in Teamwork.com by project. In the context of Teamwork.com, a milestone represents a significant point or goal within a project that marks the completion of a major phase or a key deliverable. It acts as a high-level indicator of progress, helping teams track whether work is advancing according to plan. Milestones are typically used to coordinate efforts across different tasks and task lists, providing a clear deadline or objective that multiple team members or departments can align around. They don't contain individual tasks themselves but serve as checkpoints to ensure the project is moving in the right direction.

ParametersJSON Schema
NameRequiredDescriptionDefault
pageNoPage number for pagination of results.
tag_idsNoA list of tag IDs to filter milestones by tags
page_sizeNoNumber of results per page for pagination.
project_idYesThe ID of the project from which to retrieve milestones.
search_termNoA search term to filter milestones by name. Each word from the search term is used to match against the milestone name and description. The milestone will be selected if each word of the term matches the milestone name or description, not requiring that the word matches are in the same field.
match_all_tagsNoIf true, the search will match milestones that have all the specified tags. If false, the search will match milestones that have any of the specified tags. Defaults to false.

Output Schema

ParametersJSON Schema
NameRequiredDescription
metaYes
milestonesYes
twprojects-list_notebooks
Read-only
Inspect

List notebooks in Teamwork.com. Notebook is a space where teams can create, share, and organize written content in a structured way. It’s commonly used for documenting processes, storing meeting notes, capturing research, or drafting ideas that need to be revisited and refined over time. Unlike quick messages or task comments, notebooks provide a more permanent and organized format that can be easily searched and referenced, helping teams maintain a centralized source of knowledge and ensuring important information remains accessible to everyone who needs it.

ParametersJSON Schema
NameRequiredDescriptionDefault
pageNoPage number for pagination of results.
tag_idsNoA list of tag IDs to filter notebooks by tags
page_sizeNoNumber of results per page for pagination.
project_idsNoA list of project IDs to filter notebooks by projects
search_termNoA search term to filter notebooks by name or description. The notebook will be selected if each word of the term matches the notebook name or description, not requiring that the word matches are in the same field.
match_all_tagsNoIf true, the search will match notebooks that have all the specified tags. If false, the search will match notebooks that have any of the specified tags. Defaults to false.
include_contentsNoIf true, the contents of the notebook will be included in the response. Defaults to true.

Output Schema

ParametersJSON Schema
NameRequiredDescription
metaYes
notebooksYes
twprojects-list_project_budgets
Read-only
Inspect

List project budgets in Teamwork.com. In the context of Teamwork.com, a project budget defines the overall budget allocation for a project, including capacity and usage tracking over time. It can be scoped by status and project, enabling teams to monitor financial or effort limits, track consumption, and understand budget performance across active, upcoming, and completed budget periods.

ParametersJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum number of budgets to return.
cursorNoCursor for fetching the next page of results.
statusNoFilter budgets by status. Allowed values: upcoming, active, complete.
page_sizeNoNumber of budgets to return per page.
project_idsNoA list of project IDs to filter budgets by project.

Output Schema

ParametersJSON Schema
NameRequiredDescription
metaYes
budgetsYes
includedYes
twprojects-list_project_categories
Read-only
Inspect

List project categories in Teamwork.com. The project category is a way to group and label related projects so teams can organize their work more clearly across the platform. By assigning a category, you create a higher-level structure that makes it easier to filter, report on, and navigate multiple projects, ensuring that departments, workflows, or strategic areas remain neatly aligned and easier to manage.

ParametersJSON Schema
NameRequiredDescriptionDefault
pageNoPage number for pagination of results.
page_sizeNoNumber of results per page for pagination.
search_termNoA search term to filter project categories by name.

Output Schema

ParametersJSON Schema
NameRequiredDescription
metaYes
projectCategoriesYes
twprojects-list_projects
Read-only
Inspect

List projects in Teamwork.com. The project feature in Teamwork.com serves as the central workspace for organizing and managing a specific piece of work or initiative. Each project provides a dedicated area where teams can plan tasks, assign responsibilities, set deadlines, and track progress toward shared goals. Projects include tools for communication, file sharing, milestones, and time tracking, allowing teams to stay aligned and informed throughout the entire lifecycle of the work. Whether it's a product launch, client engagement, or internal initiative, projects in Teamwork.com help teams structure their efforts, collaborate more effectively, and deliver results with greater visibility and accountability.

ParametersJSON Schema
NameRequiredDescriptionDefault
pageNoPage number for pagination of results.
tag_idsNoA list of tag IDs to filter projects by tags.
page_sizeNoNumber of results per page for pagination.
search_termNoA search term to filter projects by name or description.
match_all_tagsNoIf true, the search will match projects that have all the specified tags. If false, the search will match projects that have any of the specified tags. Defaults to false.
project_category_idsNoA list of project category IDs to filter projects by categories.

Output Schema

ParametersJSON Schema
NameRequiredDescription
metaYes
projectsYes
twprojects-list_project_templates
Read-only
Inspect

List project templates in Teamwork.com. The project template is a reusable project structure designed to standardize workflows and streamline project setup. It typically includes predefined tasks, task lists, milestones, and timelines that reflect a repeatable process, allowing teams to quickly spin up new projects with consistent organization, clear responsibilities, and efficient execution from the start.

ParametersJSON Schema
NameRequiredDescriptionDefault
pageNoPage number for pagination of results.
tag_idsNoA list of tag IDs to filter project templates by tags.
page_sizeNoNumber of results per page for pagination.
search_termNoA search term to filter project templates by name or description.
match_all_tagsNoIf true, the search will match project templates that have all the specified tags. If false, the search will match project templates that have any of the specified tags. Defaults to false.
project_category_idsNoA list of project category IDs to filter project templates by categories.

Output Schema

ParametersJSON Schema
NameRequiredDescription
metaYes
projectsYes
twprojects-list_skills
Read-only
Inspect

List skills in Teamwork.com. Skill represents a specific capability, area of expertise, or proficiency that can be assigned to users to describe what they are good at or qualified to work on. Skills help teams understand the strengths available across the organization and make it easier to match the right skills to the right work when planning projects, assigning tasks, or managing resources. By associating skills with users and leveraging them in planning and reporting, Teamwork enables more effective workload distribution, better project outcomes, and clearer visibility into whether the team has the capabilities needed to deliver upcoming work.

ParametersJSON Schema
NameRequiredDescriptionDefault
pageNoPage number for pagination of results.
page_sizeNoNumber of results per page for pagination.
search_termNoA search term to filter skills by name, or assigned users. The skill will be selected if each word of the term matches the name, or assigned user first or last name, not requiring that the word matches are in the same field.

Output Schema

ParametersJSON Schema
NameRequiredDescription
metaYes
skillsYes
twprojects-list_tags
Read-only
Inspect

List tags in Teamwork.com. In the context of Teamwork.com, a tag is a customizable label that can be applied to various items such as tasks, projects, milestones, messages, and more, to help categorize and organize work efficiently. Tags provide a flexible way to filter, search, and group related items across the platform, making it easier for teams to manage complex workflows, highlight priorities, or track themes and statuses. Since tags are user-defined, they adapt to each team’s specific needs and can be color-coded for better visual clarity.

ParametersJSON Schema
NameRequiredDescriptionDefault
pageNoPage number for pagination of results.
item_typeNoThe type of item to filter tags by. Valid values are 'project', 'task', 'tasklist', 'milestone', 'message', 'timelog', 'notebook', 'file', 'company' and 'link'.
page_sizeNoNumber of results per page for pagination.
project_idsNoA list of project IDs to filter tags by projects
search_termNoA search term to filter tags by name. Each word from the search term is used to match against the tag name.

Output Schema

ParametersJSON Schema
NameRequiredDescription
metaYes
tagsYes
twprojects-list_tasklist_budgets
Read-only
Inspect

List tasklist budgets for a project budget in Teamwork.com. In the context of Teamwork.com, a tasklist budget is a budget allocation attached to a specific task list within a project budget. It tracks capacity (in time or money) assigned to and consumed by a task list, helping teams monitor spend and effort at a granular level within a broader project budget.

ParametersJSON Schema
NameRequiredDescriptionDefault
pageNoPage number for pagination of results.
page_sizeNoNumber of results per page for pagination.
project_budget_idYesThe ID of the project budget to list tasklist budgets for.

Output Schema

ParametersJSON Schema
NameRequiredDescription
metaYes
includedYes
tasklistBudgetsYes
twprojects-list_tasklists
Read-only
Inspect

List tasklists in Teamwork.com. In the context of Teamwork.com, a task list is a way to group related tasks within a project, helping teams organize their work into meaningful sections such as phases, categories, or deliverables. Each task list belongs to a specific project and can include multiple tasks that are typically aligned with a common goal. Task lists can be associated with milestones, and they support privacy settings that control who can view or interact with the tasks they contain. This structure helps teams manage progress, assign responsibilities, and maintain clarity across complex projects.

ParametersJSON Schema
NameRequiredDescriptionDefault
pageNoPage number for pagination of results.
page_sizeNoNumber of results per page for pagination.
search_termNoA search term to filter tasklists by name.

Output Schema

ParametersJSON Schema
NameRequiredDescription
metaYes
tasklistsYes
twprojects-list_tasklists_by_project
Read-only
Inspect

List tasklists in Teamwork.com by project. In the context of Teamwork.com, a task list is a way to group related tasks within a project, helping teams organize their work into meaningful sections such as phases, categories, or deliverables. Each task list belongs to a specific project and can include multiple tasks that are typically aligned with a common goal. Task lists can be associated with milestones, and they support privacy settings that control who can view or interact with the tasks they contain. This structure helps teams manage progress, assign responsibilities, and maintain clarity across complex projects.

ParametersJSON Schema
NameRequiredDescriptionDefault
pageNoPage number for pagination of results.
page_sizeNoNumber of results per page for pagination.
project_idYesThe ID of the project from which to retrieve tasklists.
search_termNoA search term to filter tasklists by name.

Output Schema

ParametersJSON Schema
NameRequiredDescription
metaYes
tasklistsYes
twprojects-list_tasks
Read-only
Inspect

List tasks in Teamwork.com. In Teamwork.com, a task represents an individual unit of work assigned to one or more team members within a project. Each task can include details such as a title, description, priority, estimated time, assignees, and due date, along with the ability to attach files, leave comments, track time, and set dependencies on other tasks. Tasks are organized within task lists, helping structure and sequence work logically. They serve as the building blocks of project management in Teamwork, allowing teams to collaborate, monitor progress, and ensure accountability throughout the project's lifecycle.

ParametersJSON Schema
NameRequiredDescriptionDefault
pageNoPage number for pagination of results.
tag_idsNoA list of tag IDs to filter tasks by tags
page_sizeNoNumber of results per page for pagination.
search_termNoA search term to filter tasks by name.
match_all_tagsNoIf true, the search will match tasks that have all the specified tags. If false, the search will match tasks that have any of the specified tags. Defaults to false.
assignee_user_idsNoA list of user IDs to filter tasks by assigned users

Output Schema

ParametersJSON Schema
NameRequiredDescription
metaYes
tasksYes
twprojects-list_tasks_by_project
Read-only
Inspect

List tasks in Teamwork.com by project. In Teamwork.com, a task represents an individual unit of work assigned to one or more team members within a project. Each task can include details such as a title, description, priority, estimated time, assignees, and due date, along with the ability to attach files, leave comments, track time, and set dependencies on other tasks. Tasks are organized within task lists, helping structure and sequence work logically. They serve as the building blocks of project management in Teamwork, allowing teams to collaborate, monitor progress, and ensure accountability throughout the project's lifecycle.

ParametersJSON Schema
NameRequiredDescriptionDefault
pageNoPage number for pagination of results.
tag_idsNoA list of tag IDs to filter tasks by tags
page_sizeNoNumber of results per page for pagination.
project_idYesThe ID of the project from which to retrieve tasks.
search_termNoA search term to filter tasks by name.
match_all_tagsNoIf true, the search will match tasks that have all the specified tags. If false, the search will match tasks that have any of the specified tags. Defaults to false.
assignee_user_idsNoA list of user IDs to filter tasks by assigned users

Output Schema

ParametersJSON Schema
NameRequiredDescription
metaYes
tasksYes
twprojects-list_tasks_by_tasklist
Read-only
Inspect

List tasks in Teamwork.com by tasklist. In Teamwork.com, a task represents an individual unit of work assigned to one or more team members within a project. Each task can include details such as a title, description, priority, estimated time, assignees, and due date, along with the ability to attach files, leave comments, track time, and set dependencies on other tasks. Tasks are organized within task lists, helping structure and sequence work logically. They serve as the building blocks of project management in Teamwork, allowing teams to collaborate, monitor progress, and ensure accountability throughout the project's lifecycle.

ParametersJSON Schema
NameRequiredDescriptionDefault
pageNoPage number for pagination of results.
tag_idsNoA list of tag IDs to filter tasks by tags
page_sizeNoNumber of results per page for pagination.
search_termNoA search term to filter tasks by name.
tasklist_idYesThe ID of the tasklist from which to retrieve tasks.
match_all_tagsNoIf true, the search will match tasks that have all the specified tags. If false, the search will match tasks that have any of the specified tags. Defaults to false.
assignee_user_idsNoA list of user IDs to filter tasks by assigned users

Output Schema

ParametersJSON Schema
NameRequiredDescription
metaYes
tasksYes
twprojects-list_teams
Read-only
Inspect

List teams in Teamwork.com. In the context of Teamwork.com, a team is a group of users who are organized together to collaborate more efficiently on projects and tasks. Teams help structure work by grouping individuals with similar roles, responsibilities, or departmental functions, making it easier to assign work, track progress, and manage communication. By using teams, organizations can streamline project planning and ensure the right people are involved in the right parts of a project, enhancing clarity and accountability across the platform.

ParametersJSON Schema
NameRequiredDescriptionDefault
pageNoPage number for pagination of results.
page_sizeNoNumber of results per page for pagination.
search_termNoA search term to filter teams by name or handle.

Output Schema

ParametersJSON Schema
NameRequiredDescription
teamsYes
twprojects-list_teams_by_company
Read-only
Inspect

List teams in Teamwork.com by client/company. In the context of Teamwork.com, a team is a group of users who are organized together to collaborate more efficiently on projects and tasks. Teams help structure work by grouping individuals with similar roles, responsibilities, or departmental functions, making it easier to assign work, track progress, and manage communication. By using teams, organizations can streamline project planning and ensure the right people are involved in the right parts of a project, enhancing clarity and accountability across the platform.

ParametersJSON Schema
NameRequiredDescriptionDefault
pageNoPage number for pagination of results.
page_sizeNoNumber of results per page for pagination.
company_idYesThe ID of the company from which to retrieve teams.
search_termNoA search term to filter teams by name or handle.

Output Schema

ParametersJSON Schema
NameRequiredDescription
teamsYes
twprojects-list_teams_by_project
Read-only
Inspect

List teams in Teamwork.com by project. In the context of Teamwork.com, a team is a group of users who are organized together to collaborate more efficiently on projects and tasks. Teams help structure work by grouping individuals with similar roles, responsibilities, or departmental functions, making it easier to assign work, track progress, and manage communication. By using teams, organizations can streamline project planning and ensure the right people are involved in the right parts of a project, enhancing clarity and accountability across the platform.

ParametersJSON Schema
NameRequiredDescriptionDefault
pageNoPage number for pagination of results.
page_sizeNoNumber of results per page for pagination.
project_idYesThe ID of the project from which to retrieve teams.
search_termNoA search term to filter teams by name or handle.

Output Schema

ParametersJSON Schema
NameRequiredDescription
teamsYes
twprojects-list_timelogs
Read-only
Inspect

List timelogs in Teamwork.com. Timelog refers to a recorded entry that tracks the amount of time a person has spent working on a specific task, project, or piece of work. These entries typically include details such as the duration of time worked, the date and time it was logged, who logged it, and any optional notes describing what was done during that period. Timelogs are essential for understanding how time is being allocated across projects, enabling teams to manage resources more effectively, invoice clients accurately, and assess productivity. They can be created manually or with timers, and are often used for reporting and billing purposes.

ParametersJSON Schema
NameRequiredDescriptionDefault
pageNoPage number for pagination of results.
tag_idsNoA list of tag IDs to filter timelogs by tags
end_dateNoEnd date to filter timelogs. The date format follows RFC3339 - YYYY-MM-DDTHH:MM:SSZ.
page_sizeNoNumber of results per page for pagination.
ticketIdsNoA list of desk ticket IDs to filter timelogs by associated desk tickets
start_dateNoStart date to filter timelogs. The date format follows RFC3339 - YYYY-MM-DDTHH:MM:SSZ.
match_all_tagsNoIf true, the search will match timelogs that have all the specified tags. If false, the search will match timelogs that have any of the specified tags. Defaults to false.
assigned_team_idsNoA list of team IDs to filter timelogs by assigned teams
assigned_user_idsNoA list of user IDs to filter timelogs by assigned users
assigned_company_idsNoA list of company IDs to filter timelogs by assigned companies

Output Schema

ParametersJSON Schema
NameRequiredDescription
metaYes
timelogsYes
twprojects-list_timelogs_by_project
Read-only
Inspect

List timelogs in Teamwork.com by project. Timelog refers to a recorded entry that tracks the amount of time a person has spent working on a specific task, project, or piece of work. These entries typically include details such as the duration of time worked, the date and time it was logged, who logged it, and any optional notes describing what was done during that period. Timelogs are essential for understanding how time is being allocated across projects, enabling teams to manage resources more effectively, invoice clients accurately, and assess productivity. They can be created manually or with timers, and are often used for reporting and billing purposes.

ParametersJSON Schema
NameRequiredDescriptionDefault
pageNoPage number for pagination of results.
tag_idsNoA list of tag IDs to filter timelogs by tags
end_dateNoEnd date to filter timelogs. The date format follows RFC3339 - YYYY-MM-DDTHH:MM:SSZ.
page_sizeNoNumber of results per page for pagination.
ticketIdsNoA list of desk ticket IDs to filter timelogs by associated desk tickets
project_idYesThe ID of the project from which to retrieve timelogs.
start_dateNoStart date to filter timelogs. The date format follows RFC3339 - YYYY-MM-DDTHH:MM:SSZ.
match_all_tagsNoIf true, the search will match timelogs that have all the specified tags. If false, the search will match timelogs that have any of the specified tags. Defaults to false.
assigned_team_idsNoA list of team IDs to filter timelogs by assigned teams
assigned_user_idsNoA list of user IDs to filter timelogs by assigned users
assigned_company_idsNoA list of company IDs to filter timelogs by assigned companies

Output Schema

ParametersJSON Schema
NameRequiredDescription
metaYes
timelogsYes
twprojects-list_timelogs_by_task
Read-only
Inspect

List timelogs in Teamwork.com by task. Timelog refers to a recorded entry that tracks the amount of time a person has spent working on a specific task, project, or piece of work. These entries typically include details such as the duration of time worked, the date and time it was logged, who logged it, and any optional notes describing what was done during that period. Timelogs are essential for understanding how time is being allocated across projects, enabling teams to manage resources more effectively, invoice clients accurately, and assess productivity. They can be created manually or with timers, and are often used for reporting and billing purposes.

ParametersJSON Schema
NameRequiredDescriptionDefault
pageNoPage number for pagination of results.
tag_idsNoA list of tag IDs to filter timelogs by tags
task_idYesThe ID of the task from which to retrieve timelogs.
end_dateNoEnd date to filter timelogs. The date format follows RFC3339 - YYYY-MM-DDTHH:MM:SSZ.
page_sizeNoNumber of results per page for pagination.
ticketIdsNoA list of desk ticket IDs to filter timelogs by associated desk tickets
start_dateNoStart date to filter timelogs. The date format follows RFC3339 - YYYY-MM-DDTHH:MM:SSZ.
match_all_tagsNoIf true, the search will match timelogs that have all the specified tags. If false, the search will match timelogs that have any of the specified tags. Defaults to false.
assigned_team_idsNoA list of team IDs to filter timelogs by assigned teams
assigned_user_idsNoA list of user IDs to filter timelogs by assigned users
assigned_company_idsNoA list of company IDs to filter timelogs by assigned companies

Output Schema

ParametersJSON Schema
NameRequiredDescription
metaYes
timelogsYes
twprojects-list_timers
Read-only
Inspect

List timers in Teamwork.com. Timer is a built-in tool that allows users to accurately track the time they spend working on specific tasks, projects, or client work. Instead of manually recording hours, users can start, pause, and stop timers directly within the platform or through the desktop and mobile apps, ensuring precise time logs without interrupting their workflow. Once recorded, these entries are automatically linked to the relevant task or project, making it easier to monitor productivity, manage billable hours, and generate detailed reports for both internal tracking and client invoicing.

ParametersJSON Schema
NameRequiredDescriptionDefault
pageNoPage number for pagination of results.
task_idNoThe ID of the task to filter timers by. Only timers associated with this task will be returned.
user_idNoThe ID of the user to filter timers by. Only timers associated with this user will be returned.
page_sizeNoNumber of results per page for pagination.
project_idNoThe ID of the project to filter timers by. Only timers associated with this project will be returned.
running_timers_onlyNoIf true, only running timers will be returned. Defaults to false, which returns all timers.

Output Schema

ParametersJSON Schema
NameRequiredDescription
metaYes
timersYes
twprojects-list_users
Read-only
Inspect

List users in Teamwork.com. A user is an individual who has access to one or more projects within a Teamwork site, typically as a team member, collaborator, or administrator. Users can be assigned tasks, participate in discussions, log time, share files, and interact with other members depending on their permission levels. Each user has a unique profile that defines their role, visibility, and access to features and project data. Users can belong to clients/companies or teams within the system, and their permissions can be customized to control what actions they can perform or what information they can see.

ParametersJSON Schema
NameRequiredDescriptionDefault
pageNoPage number for pagination of results.
typeNoType of user to filter by. The available options are account, collaborator or contact.
page_sizeNoNumber of results per page for pagination.
search_termNoA search term to filter users by first or last names, or e-mail. The user will be selected if each word of the term matches the first or last name, or e-mail, not requiring that the word matches are in the same field.

Output Schema

ParametersJSON Schema
NameRequiredDescription
metaYes
peopleYes
twprojects-list_users_by_project
Read-only
Inspect

List users in Teamwork.com by project. A user is an individual who has access to one or more projects within a Teamwork site, typically as a team member, collaborator, or administrator. Users can be assigned tasks, participate in discussions, log time, share files, and interact with other members depending on their permission levels. Each user has a unique profile that defines their role, visibility, and access to features and project data. Users can belong to clients/companies or teams within the system, and their permissions can be customized to control what actions they can perform or what information they can see.

ParametersJSON Schema
NameRequiredDescriptionDefault
pageNoPage number for pagination of results.
typeNoType of user to filter by. The available options are account, collaborator or contact.
page_sizeNoNumber of results per page for pagination.
project_idYesThe ID of the project from which to retrieve users.
search_termNoA search term to filter users by first or last names, or e-mail. The user will be selected if each word of the term matches the first or last name, or e-mail, not requiring that the word matches are in the same field.

Output Schema

ParametersJSON Schema
NameRequiredDescription
metaYes
peopleYes
twprojects-pause_timerInspect

Pause an existing timer in Teamwork.com. Timer is a built-in tool that allows users to accurately track the time they spend working on specific tasks, projects, or client work. Instead of manually recording hours, users can start, pause, and stop timers directly within the platform or through the desktop and mobile apps, ensuring precise time logs without interrupting their workflow. Once recorded, these entries are automatically linked to the relevant task or project, making it easier to monitor productivity, manage billable hours, and generate detailed reports for both internal tracking and client invoicing.

ParametersJSON Schema
NameRequiredDescriptionDefault
idYesThe ID of the timer to pause.
twprojects-resume_timerInspect

Resume an existing timer in Teamwork.com. Timer is a built-in tool that allows users to accurately track the time they spend working on specific tasks, projects, or client work. Instead of manually recording hours, users can start, pause, and stop timers directly within the platform or through the desktop and mobile apps, ensuring precise time logs without interrupting their workflow. Once recorded, these entries are automatically linked to the relevant task or project, making it easier to monitor productivity, manage billable hours, and generate detailed reports for both internal tracking and client invoicing.

ParametersJSON Schema
NameRequiredDescriptionDefault
idYesThe ID of the timer to resume.
twprojects-update_commentInspect

Update an existing comment in Teamwork.com. In the Teamwork.com context, a comment is a way for users to communicate and collaborate directly within tasks, milestones, files, or other project items. Comments allow team members to provide updates, ask questions, give feedback, or share relevant information in a centralized and contextual manner. They support rich text formatting, file attachments, and @mentions to notify specific users or teams, helping keep discussions organized and easily accessible within the project. Comments are visible to all users with access to the item, promoting transparency and keeping everyone aligned.

ParametersJSON Schema
NameRequiredDescriptionDefault
idYesThe ID of the comment to update.
bodyYesThe content of the comment. The content can be added as text or HTML.
content_typeNoThe content type of the comment. It can be either 'TEXT' or 'HTML'.
twprojects-update_companyInspect

Update an existing company in Teamwork.com. In the context of Teamwork.com, a company represents an organization or business entity that can be associated with users, projects, and tasks within the platform, and it is often referred to as a “client.” It serves as a way to group related users and projects under a single organizational umbrella, making it easier to manage permissions, assign responsibilities, and organize work. Companies (or clients) are frequently used to distinguish between internal teams and external collaborators, enabling teams to work efficiently while maintaining clear boundaries around ownership, visibility, and access levels across different projects.

ParametersJSON Schema
NameRequiredDescriptionDefault
idYesThe ID of the company to update.
faxNoThe fax number of the company.
zipNoThe ZIP or postal code of the company.
cityNoThe city of the company.
nameNoThe name of the company.
phoneNoThe phone number of the company.
stateNoThe state of the company.
profileNoA profile description for the company.
tag_idsNoA list of tag IDs to associate with the company.
websiteNoThe website of the company.
email_oneNoThe primary email address of the company.
email_twoNoThe secondary email address of the company.
manager_idNoThe ID of the user who manages the company.
address_oneNoThe first line of the address of the company.
address_twoNoThe second line of the address of the company.
email_threeNoThe tertiary email address of the company.
industry_idNoThe ID of the industry the company belongs to.
country_codeNoThe country code of the company, e.g., 'US' for the United States.
twprojects-update_jobroleInspect

Update an existing job role in Teamwork.com. Job role defines a user's primary function or position within the organization, such as developer, designer, project manager, or account manager. It provides high-level context about what a person is generally responsible for, helping teams understand who does what across projects and departments. Job roles are commonly used in resource planning, capacity forecasting, and reporting, allowing managers to group work by role, plan future demand more accurately, and ensure the right mix of roles is available to deliver projects efficiently.

ParametersJSON Schema
NameRequiredDescriptionDefault
idYesThe ID of the job role to update.
nameNoThe name of the job role.
twprojects-update_milestoneInspect

Update an existing milestone in Teamwork.com. In the context of Teamwork.com, a milestone represents a significant point or goal within a project that marks the completion of a major phase or a key deliverable. It acts as a high-level indicator of progress, helping teams track whether work is advancing according to plan. Milestones are typically used to coordinate efforts across different tasks and task lists, providing a clear deadline or objective that multiple team members or departments can align around. They don't contain individual tasks themselves but serve as checkpoints to ensure the project is moving in the right direction.

ParametersJSON Schema
NameRequiredDescriptionDefault
idYesThe ID of the milestone to update.
nameNoThe name of the milestone.
tag_idsNoA list of tag IDs to associate with the milestone.
due_dateNoThe due date of the milestone in the format YYYYMMDD. This date will be used in all tasks without a due date related to this milestone.
assigneesNoAn object containing assignees for the milestone.
descriptionNoA description of the milestone.
tasklist_idsNoA list of tasklist IDs to associate with the milestone.
twprojects-update_notebookInspect

Update an existing notebook in Teamwork.com. Notebook is a space where teams can create, share, and organize written content in a structured way. It’s commonly used for documenting processes, storing meeting notes, capturing research, or drafting ideas that need to be revisited and refined over time. Unlike quick messages or task comments, notebooks provide a more permanent and organized format that can be easily searched and referenced, helping teams maintain a centralized source of knowledge and ensuring important information remains accessible to everyone who needs it.

ParametersJSON Schema
NameRequiredDescriptionDefault
idYesThe ID of the notebook to update.
nameNoThe name of the notebook.
typeNoThe type of the notebook. Valid values are 'MARKDOWN' and 'HTML'.
tag_idsNoA list of tag IDs to associate with the notebook.
contentsNoThe contents of the notebook.
descriptionNoA description of the notebook.
twprojects-update_projectInspect

Update an existing project in Teamwork.com. The project feature in Teamwork.com serves as the central workspace for organizing and managing a specific piece of work or initiative. Each project provides a dedicated area where teams can plan tasks, assign responsibilities, set deadlines, and track progress toward shared goals. Projects include tools for communication, file sharing, milestones, and time tracking, allowing teams to stay aligned and informed throughout the entire lifecycle of the work. Whether it's a product launch, client engagement, or internal initiative, projects in Teamwork.com help teams structure their efforts, collaborate more effectively, and deliver results with greater visibility and accountability.

ParametersJSON Schema
NameRequiredDescriptionDefault
idYesThe ID of the project to update.
nameNoThe name of the project.
end_atNoThe end date of the project in the format YYYYMMDD.
statusNoThe status of the project. Allowed values: active or archived.
tag_idsNoA list of tag IDs to associate with the project.
owned_idNoThe ID of the user who owns the project.
start_atNoThe start date of the project in the format YYYYMMDD.
company_idNoThe ID of the company associated with the project.
category_idNoThe ID of the category to which the project belongs.
descriptionNoThe description of the project.
twprojects-update_project_categoryInspect

Update an existing project category in Teamwork.com. The project category is a way to group and label related projects so teams can organize their work more clearly across the platform. By assigning a category, you create a higher-level structure that makes it easier to filter, report on, and navigate multiple projects, ensuring that departments, workflows, or strategic areas remain neatly aligned and easier to manage.

ParametersJSON Schema
NameRequiredDescriptionDefault
idYesThe ID of the project category to update.
nameNoThe name of the project category.
colorNoThe color of the project category in hex format (e.g., #FF5733).
parent_idNoThe ID of the parent project category, if any. This allows for nested categories.
twprojects-update_skillInspect

Update an existing skill in Teamwork.com. Skill represents a specific capability, area of expertise, or proficiency that can be assigned to users to describe what they are good at or qualified to work on. Skills help teams understand the strengths available across the organization and make it easier to match the right skills to the right work when planning projects, assigning tasks, or managing resources. By associating skills with users and leveraging them in planning and reporting, Teamwork enables more effective workload distribution, better project outcomes, and clearer visibility into whether the team has the capabilities needed to deliver upcoming work.

ParametersJSON Schema
NameRequiredDescriptionDefault
idYesThe ID of the skill to update.
nameNoThe name of the skill.
user_idsNoThe user IDs associated with the skill.
twprojects-update_tagInspect

Update an existing tag in Teamwork.com. In the context of Teamwork.com, a tag is a customizable label that can be applied to various items such as tasks, projects, milestones, messages, and more, to help categorize and organize work efficiently. Tags provide a flexible way to filter, search, and group related items across the platform, making it easier for teams to manage complex workflows, highlight priorities, or track themes and statuses. Since tags are user-defined, they adapt to each team’s specific needs and can be color-coded for better visual clarity.

ParametersJSON Schema
NameRequiredDescriptionDefault
idYesThe ID of the tag to update.
nameNoThe name of the tag. It must have less than 50 characters.
project_idNoThe ID of the project to associate the tag with. This is for project-scoped tags.
twprojects-update_taskInspect

Update an existing task in Teamwork.com. In Teamwork.com, a task represents an individual unit of work assigned to one or more team members within a project. Each task can include details such as a title, description, priority, estimated time, assignees, and due date, along with the ability to attach files, leave comments, track time, and set dependencies on other tasks. Tasks are organized within task lists, helping structure and sequence work logically. They serve as the building blocks of project management in Teamwork, allowing teams to collaborate, monitor progress, and ensure accountability throughout the project's lifecycle.

ParametersJSON Schema
NameRequiredDescriptionDefault
idYesThe ID of the task to update.
nameNoThe name/title of the task.
tag_idsNoA list of tag IDs to assign to the task.
due_dateNoThe due date of the task in ISO 8601 format (YYYY-MM-DD). When this is not provided, it will fallback to the milestone due date if a milestone is set.
priorityNoThe priority of the task. Possible values are: low, medium, high.
progressNoThe progress of the task, as a percentage (0-100). Only whole numbers are allowed.
assigneesNoAn object containing assignees for the task.
start_dateNoThe start date of the task in ISO 8601 format (YYYY-MM-DD).
descriptionNoThe description of the task.
tasklist_idNoThe ID of the tasklist.
predecessorsNoList of task dependencies that must be completed before this task can start, defining its position in the project workflow and ensuring proper sequencing of work.
parent_task_idNoThe ID of the parent task if creating a subtask.
estimated_minutesNoThe estimated time to complete the task in minutes.
twprojects-update_tasklistInspect

Update an existing tasklist in Teamwork.com. In the context of Teamwork.com, a task list is a way to group related tasks within a project, helping teams organize their work into meaningful sections such as phases, categories, or deliverables. Each task list belongs to a specific project and can include multiple tasks that are typically aligned with a common goal. Task lists can be associated with milestones, and they support privacy settings that control who can view or interact with the tasks they contain. This structure helps teams manage progress, assign responsibilities, and maintain clarity across complex projects.

ParametersJSON Schema
NameRequiredDescriptionDefault
idYesThe ID of the tasklist to update.
nameNoThe name of the tasklist.
descriptionNoThe description of the tasklist.
milestone_idNoThe ID of the milestone to associate with the tasklist.
twprojects-update_teamInspect

Update an existing team in Teamwork.com. In the context of Teamwork.com, a team is a group of users who are organized together to collaborate more efficiently on projects and tasks. Teams help structure work by grouping individuals with similar roles, responsibilities, or departmental functions, making it easier to assign work, track progress, and manage communication. By using teams, organizations can streamline project planning and ensure the right people are involved in the right parts of a project, enhancing clarity and accountability across the platform.

ParametersJSON Schema
NameRequiredDescriptionDefault
idYesThe ID of the team to update.
nameNoThe name of the team.
handleNoThe handle of the team. It is a unique identifier for the team. It must not have spaces or special characters.
user_idsNoA list of user IDs to add to the team.
company_idNoThe ID of the company. This is used to create a team scoped for a specific company.
project_idNoThe ID of the project. This is used to create a team scoped for a specific project.
descriptionNoThe description of the team.
parent_team_idNoThe ID of the parent team. This is used to create a hierarchy of teams.
twprojects-update_timelogInspect

Update an existing timelog in Teamwork.com. Timelog refers to a recorded entry that tracks the amount of time a person has spent working on a specific task, project, or piece of work. These entries typically include details such as the duration of time worked, the date and time it was logged, who logged it, and any optional notes describing what was done during that period. Timelogs are essential for understanding how time is being allocated across projects, enabling teams to manage resources more effectively, invoice clients accurately, and assess productivity. They can be created manually or with timers, and are often used for reporting and billing purposes.

ParametersJSON Schema
NameRequiredDescriptionDefault
idYesThe ID of the timelog to update.
dateNoThe date of the timelog in the format YYYY-MM-DD.
timeNoThe time of the timelog in the format HH:MM:SS.
hoursNoThe number of hours spent on the timelog. Must be a positive integer.
is_utcNoIf true, the time is in UTC. Defaults to false.
minutesNoThe number of minutes spent on the timelog. Must be a positive integer less than 60, otherwise the hours attribute should be incremented.
tag_idsNoA list of tag IDs to associate with the timelog.
task_idNoThe ID of the task to associate the timelog with. Either project_id or task_id must be provided, but not both.
user_idNoThe ID of the user to associate the timelog with. Defaults to the authenticated user if not provided.
billableNoIf true, the timelog is billable. Defaults to false.
project_idNoThe ID of the project to associate the timelog with. Either project_id or task_id must be provided, but not both.
descriptionNoA description of the timelog.
twprojects-update_timerInspect

Update an existing timer in Teamwork.com. Timer is a built-in tool that allows users to accurately track the time they spend working on specific tasks, projects, or client work. Instead of manually recording hours, users can start, pause, and stop timers directly within the platform or through the desktop and mobile apps, ensuring precise time logs without interrupting their workflow. Once recorded, these entries are automatically linked to the relevant task or project, making it easier to monitor productivity, manage billable hours, and generate detailed reports for both internal tracking and client invoicing.

ParametersJSON Schema
NameRequiredDescriptionDefault
idYesThe ID of the timer to update.
runningNoIf true, the timer will start running immediately.
task_idNoThe ID of the task to associate the timer with.
billableNoIf true, the timer is billable.
project_idNoThe ID of the project to associate the timer with.
descriptionNoA description of the timer.
twprojects-update_userInspect

Update an existing user in Teamwork.com. A user is an individual who has access to one or more projects within a Teamwork site, typically as a team member, collaborator, or administrator. Users can be assigned tasks, participate in discussions, log time, share files, and interact with other members depending on their permission levels. Each user has a unique profile that defines their role, visibility, and access to features and project data. Users can belong to clients/companies or teams within the system, and their permissions can be customized to control what actions they can perform or what information they can see.

ParametersJSON Schema
NameRequiredDescriptionDefault
idYesThe ID of the user to update.
typeNoThe type of user, such as 'account', 'collaborator', or 'contact'.
adminNoIndicates whether the user is an administrator.
emailNoThe email address of the user.
titleNoThe job title of the user, such as 'Project Manager' or 'Senior Software Developer'.
last_nameNoThe last name of the user.
company_idNoThe ID of the client/company to which the user belongs.
first_nameNoThe first name of the user.
twprojects-users_workload
Read-only
Inspect

Get the workload of users in Teamwork.com. Workload is a visual representation of how tasks are distributed across team members, helping you understand who is overloaded, who has capacity, and how work is balanced within a project or across multiple projects. It takes into account assigned tasks, due dates, estimated time, and working hours to give managers and teams a clear picture of availability and resource allocation. By providing this insight, workload makes it easier to plan effectively, prevent burnout, and ensure that deadlines are met without placing too much pressure on any single person.

ParametersJSON Schema
NameRequiredDescriptionDefault
pageNoPage number for pagination of results.
end_dateYesThe end date of the workload period. The date must be in the format YYYY-MM-DD.
user_idsNoList of user IDs to filter the workload by.
page_sizeNoNumber of results per page for pagination.
start_dateYesThe start date of the workload period. The date must be in the format YYYY-MM-DD.
project_idsNoList of project IDs to filter the workload by.
user_team_idsNoList of users' team IDs to filter the workload by.
user_company_idsNoList of users' client/company IDs to filter the workload by.

Output Schema

ParametersJSON Schema
NameRequiredDescription
metaYes
includedYes
workloadYes

Verify Ownership

Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:

{
  "$schema": "https://glama.ai/mcp/schemas/connector.json",
  "maintainers": [
    {
      "email": "your-email@example.com"
    }
  ]
}

The email address must match the email associated with your Glama account. Once verified, the connector will appear as claimed by you.

Last verification attempt failed.

Failed to fetch .well-known/glama.json: HTTP 400

Sign in to verify ownership

Discussions

No comments yet. Be the first to start the discussion!

Try in Browser

Your Connectors

Sign in to create a connector for this server.