Integration

Teamwork Desk integration

Teamwork Desk is a help desk for support teams. List, search, create, update and delete tickets, read and post replies, manage customers and companies, tags, canned responses, ticket reminders and time logs, read inboxes, users, statuses, priorities, sources, types, SLAs, triggers, templates, custom fields and happiness ratings, manage help docs articles and webhook endpoints. Site administration (inbox setup, users, permissions, SSO, imports, AI features), bulk and background routes, file downloads, related-record includes and ticket full-text search are not exposed. Authentication is a Desk API key (profile, API Keys) sent as a Bearer token, plus your site host: yourcompany.teamwork.com, yourcompany.eu.teamwork.com for EU-hosted sites, or your custom domain.

Connect Teamwork Desk How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in Teamwork Desk.Built from the 85 Teamwork Desk tools below, on the connection you add once.

What you can do with Teamwork Desk

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

Customer, 6 operations

create_customerCreate customerPOSTCreates a customer from a customer object (name, contact details, notes, social links), optionally linking a company or adding contacts (such as an email) through included.
delete_customerDelete customerDELETEDeletes a customer (restore_customer brings it back).
get_customerGet customerGETReturns one customer by id: name, organization, company, contact details, notes, social links and ticket count.
list_customersList customersGETLists customers, 50 per page, with a JSON filter and sorting.
search_customersSearch customersGETSearches customers by text, email domain, company, tags, standing (new, good, bad) or created and updated dates.
update_customerUpdate customerPATCHUpdates a customer: pass a customer object with only the fields to change; company links and contacts go through included.

Cannedresponse, 5 operations

create_canned_responseCreate canned responsePOSTCreates a canned response (a saved reply template) from a cannedresponse object.
delete_canned_responseDelete canned responseDELETEDeletes a canned response.
get_canned_responseGet canned responseGETReturns one canned response by id.
list_canned_responsesList canned responsesGETLists the canned responses (saved reply templates), 50 per page.
update_canned_responseUpdate canned responsePATCHUpdates a canned response: pass a cannedresponse object with the fields to change.

Company, 5 operations

create_companyCreate companyPOSTCreates a company with a name and optionally its email domains, website, industry, details, phone numbers, address and ticket permission for its customers.
delete_companyDelete companyDELETEDeletes a company.
get_companyGet companyGETReturns one company by id: name, domains, contact details, industry, permission and customer and ticket counts.
list_companiesList companiesGETLists companies (customer organizations), 50 per page, with a JSON filter and sorting.
update_companyUpdate companyPATCHUpdates a company: pass a company object with only the fields to change.

Helpdocarticle, 5 operations

create_help_doc_articleCreate help doc articlePOSTCreates a help docs article in a site from a helpdocarticle object (title, contents, status, categories).
delete_help_doc_articleDelete help doc articleDELETEDeletes a help docs article.
get_help_doc_articleGet help doc articleGETReturns one help docs article of a site by id.
list_help_doc_articlesList help doc articlesGETLists help docs articles, 50 per page, with filtering and sorting.
update_help_doc_articleUpdate help doc articlePATCHUpdates a help docs article: pass a helpdocarticle object with the fields to change.

Tag, 5 operations

create_tagCreate tagPOSTCreates a tag from a tag object (name and color).
delete_tagDelete tagDELETEDeletes a tag.
get_tagGet tagGETReturns one tag by id.
list_tagsList tagsGETLists the ticket tags, 50 per page, with filtering and sorting.
update_tagUpdate tagPATCHUpdates a tag: pass a tag object with the fields to change (name, color).

Ticket, 5 operations

create_ticketCreate ticketPOSTCreates a ticket with a subject and initial message for a customer (customer.id or customer.email) in an inbox, optionally with status, priority, type, source, tags, agent and CC/BCC. Attachments are not supported.
delete_ticketDelete ticketDELETEDeletes a ticket (moves it to the trash; restore_ticket brings it back).
get_ticketGet ticketGETReturns one ticket by id with its fields and its links to customer, inbox, status, priority, type, agent and tags.
list_ticketsList ticketsGETLists the tickets the current user can see, 50 per page (pageSize up to 100), with a JSON filter (for example on status, inbox, customer, agent or dates) and sorting.
update_ticketUpdate ticketPATCHUpdates a ticket: pass a ticket object with only the fields to change, such as status, priority, type, agent, inbox, tags or subject (relations as {id}).

Ticketreminder, 5 operations

create_ticket_reminderCreate ticket reminderPOSTCreates a reminder on a ticket for a user at a given time (notifyAt), with a name.
delete_ticket_reminderDelete ticket reminderDELETEDeletes a ticket reminder.
get_ticket_reminderGet ticket reminderGETReturns one ticket reminder by id.
list_ticket_remindersList ticket remindersGETLists ticket reminders, 50 per page.
update_ticket_reminderUpdate ticket reminderPATCHUpdates a ticket reminder: name or notifyAt.

Timelog, 5 operations

create_timelogCreate timelogPOSTLogs time on a ticket: seconds, date, description, billable flag, and the user (or assignToCurrentUser).
delete_timelogDelete timelogDELETEDeletes a time entry.
get_timelogGet timelogGETReturns one time entry by id.
list_timelogsList timelogsGETLists time entries logged on tickets, 50 per page, with filtering and sorting.
update_timelogUpdate timelogPATCHUpdates a time entry: seconds, date, description or billable flag.

Webhookendpoint, 5 operations

create_webhook_endpointCreate webhook endpointPOSTCreates a webhook endpoint from a webhookendpoint object: url, allEvents or events, inboxes or allInboxes, and contentType. Set allEvents true to receive every event type (deliveries name the event, for example ticket.created or customer.created).
delete_webhook_endpointDelete webhook endpointDELETEDeletes a webhook endpoint.
get_webhook_endpointGet webhook endpointGETReturns one webhook endpoint by id.
list_webhook_endpointsList webhook endpointsGETLists the webhook endpoints that receive Desk events.
update_webhook_endpointUpdate webhook endpointPATCHUpdates a webhook endpoint: url, events or allEvents, inboxes or allInboxes, contentType or state.

Customfield, 2 operations

get_custom_fieldGet custom fieldGETReturns one custom field by id.
list_custom_fieldsList custom fieldsGETLists the custom fields defined for tickets, customers or companies.

Customfieldoption, 2 operations

get_custom_field_optionGet custom field optionGETReturns one custom field option by id.
list_custom_field_optionsList custom field optionsGETLists the options of select-type custom fields.

Happinessrating, 2 operations

get_happiness_ratingGet happiness ratingGETReturns one happiness rating by id.
list_happiness_ratingsList happiness ratingsGETLists customer happiness (satisfaction) ratings left on tickets, 50 per page.

Helpdocscategory, 2 operations

get_help_doc_categoryGet help doc categoryGETReturns one help docs category by id.
list_help_doc_categoriesList help doc categoriesGETLists the help docs categories.

Helpdocssite, 2 operations

get_help_doc_siteGet help doc siteGETReturns one help docs site by id.
list_help_doc_sitesList help doc sitesGETLists the help docs (knowledge base) sites.

Inbox, 2 operations

get_inboxGet inboxGETReturns one inbox by id: name, email address, settings and auto-reply.
list_inboxesList inboxesGETLists the inboxes the current user can see, 50 per page, with filtering and sorting.

Message, 2 operations

list_ticket_messagesList ticket messagesGETLists the messages (threads) of a ticket: replies, notes and forwards, 50 per page.
reply_to_ticketReply to ticketPOSTPosts a reply on a ticket: message body, and optionally recipients (to, cc, bcc), a new ticket status and a send-from alias, or saves it as a draft or pins it. Attachments are not supported.

Restore, 2 operations

restore_customerRestore customerPATCHRestores a deleted customer.
restore_ticketRestore ticketPATCHRestores a deleted ticket from the trash.

Sla, 2 operations

get_slaGet slaGETReturns one SLA by id.
list_slasList slasGETLists the service level agreements (SLAs).

Ticketpriority, 2 operations

get_ticket_priorityGet ticket priorityGETReturns one ticket priority by id.
list_ticket_prioritiesList ticket prioritiesGETLists the ticket priorities with their id for create_ticket and update_ticket.

Ticketsource, 2 operations

get_ticket_sourceGet ticket sourceGETReturns one ticket source by id.
list_ticket_sourcesList ticket sourcesGETLists the ticket sources (such as email or phone) with their id.

Ticketstatuse, 2 operations

get_ticket_statusGet ticket statusGETReturns one ticket status by id.
list_ticket_statusesList ticket statusesGETLists the ticket statuses (such as active, waiting on customer, solved, closed), with their id for create_ticket and update_ticket.

Tickettemplate, 2 operations

get_ticket_templateGet ticket templateGETReturns one ticket template by id.
list_ticket_templatesList ticket templatesGETLists the ticket templates.

Tickettype, 2 operations

get_ticket_typeGet ticket typeGETReturns one ticket type by id.
list_ticket_typesList ticket typesGETLists the ticket types with their id for create_ticket and update_ticket.

Trigger, 2 operations

get_triggerGet triggerGETReturns one automation trigger by id.
list_triggersList triggersGETLists the automation triggers (rules applied to tickets).

User, 2 operations

get_userGet userGETReturns one user (agent) by id.
list_usersList usersGETLists the users (agents) of the Desk site, 50 per page; archived users are only returned with includeArchived=true.

Activity, 1 operation

list_ticket_activitiesList ticket activitiesGETLists ticket activity entries (the change history of tickets), with filtering and paging.

Checkapply, 1 operation

check_ticket_slasCheck ticket slasGETChecks whether any SLA applies to a ticket.

Count, 1 operation

count_inbox_ticketsCount inbox ticketsGETReturns ticket counts per inbox, by status.

Follower, 1 operation

remove_ticket_followerRemove ticket followerDELETERemoves a user from the followers of a ticket.

Helpdoc, 1 operation

search_help_doc_articlesSearch help doc articlesGETSearches help docs articles by full text (title, contents, keywords), optionally by site, category or status (Published, Draft, Unpublished).

Me, 1 operation

get_meGet meGETReturns the user the API key belongs to.

Merge, 1 operation

merge_tagsMerge tagsPUTMerges several tags into one: the tags given in tagIds are merged under the given name.

Use Teamwork Desk from Claude Code, Cursor or Codex

Connect Teamwork Desk in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its Teamwork Desk operations become tools the client can call, next to every other integration you connected.

Claude Code

claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"

Codex (~/.codex/config.toml)

[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"

Cursor, Claude Desktop and other JSON configs

{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect Teamwork Desk

Create your workspace
Sign up free. Nothing to install.
Connect Teamwork Desk once
Add your Teamwork Desk connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.
Describe the job in chat
The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.