Niches · Customer support & helpdesk
Create or update a ticket from another system
One company's docs show a full fit.
What counts as done
One ticket exists per source event after the call, with requester and fields set, no auto-reply sent unless wanted, and a retry does not create a second ticket.
How agents ask for it: open a ticket for this bug report
, log this chat as a ticket
, create a ticket from the form submission
, import these historical conversations
Does the job 1
The docs show it meets the test above, and nothing we read says otherwise.
| Listing | Why |
|---|---|
| Front API + MCP BB FrontApp, Inc. | POST /inboxes/{id}/imported_messages takes external_id (Front won't import two messages with the same one), sender, tags and assignee, and importing sends nothing to the customer. source |
Does the job, with a limit 19
It does the job, but something in the docs or a user's account will get in an agent's way. The limit is named in each row.
| Listing | Why |
|---|---|
| Chatwoot API D Chatwoot Inc. | Create New Conversation takes a contact source_id and an initial message, but no idempotency key or external id lookup is documented, so a retried create can duplicate. source |
| Crisp API + MCP D Crisp IM SAS | Create A New Conversation then a message works, and a message fingerprint avoids duplicate messages, but a retried conversation create has no idempotency key. source |
| Dixa D Dixa ApS | POST /v1/conversations and /conversations/import create conversations, and inbound messages take a client externalId, but the docs don't say a repeated externalId is refused. source |
| Drag E DragApp.com Ltd | POST /v2/card and MCP create_card make a card in a column, but no idempotency key or external id is documented. source |
| FreeScout F FreeScout | Create Conversation with imported true sends no email or auto-reply, but there is no idempotency key; only a timed-out call is documented as safe to retry. source |
| Freshdesk API + MCP D Freshworks Inc. | Create a Ticket takes requester and fields, but has no idempotency key; unique_external_id identifies contacts, not tickets. acc-17's free account was deleted and its widget broke. source |
| Gladly C Gladly Software, Inc. | Conversation items accept a client id and return 409 if it is in use, which prevents duplicates, but items created this way are not part of a conversation and are non-routable. source |
| Gorgias API + MCP C Gorgias Inc. | create_ticket logs a customer message and sends nothing by default, but message external_id is 'not used by Gorgias', so it is no idempotency key; a retry duplicates unless the agent lists by external_id first. source |
| Help Scout API + MCP B Help Scout PBC | Create Conversation and threads accept imported true so no email or notification goes out, but no idempotency key or external id is documented, so a retried create duplicates. source |
| HelpDesk D Text, Inc. | POST /v1/importedTickets imports without sending, and tickets carry an externalID, but the docs don't say a repeated externalID is refused and no idempotency key exists. source |
| Intercom API + MCP BB Intercom, Inc. (with Intercom R&D Unlimited Company in Ireland) | POST /tickets takes a ticket type, contact by external_id and attributes, but the request has no idempotency key or external id for the ticket, so a retry can duplicate. source |
| Kustomer D Kustomer, LLC | Conversations and messages can be fetched by external id, so a retry can check first, but create takes no idempotency key and the check is not atomic. source |
| LiveAgent D Quality Unit, s. r. o. | Tickets can be created over the REST API, but no idempotency key or external id lookup was found, so a retry can duplicate. source |
| Missive API + MCP C Heliom Inc. | Create a message makes incoming messages in a custom channel and Create a post can start a conversation, but no idempotency key is documented, so a retry can duplicate. source |
| Plain API + MCP B Not Just Tickets Ltd | createThread takes a customer and threads can carry an externalId with a threadByExternalId lookup, but the id is unique per customer only and the docs don't say a duplicate create is refused; importThread skips autoresponders. source |
| Pylon API + MCP C Pylon Labs, Inc. | POST /issues takes requester, account, priority, tags and fields, but no idempotency key or external id is in the request, so a retry can duplicate. source |
| Zammad E Zammad GmbH | POST /api/v1/tickets takes customer, group and first article, and X-On-Behalf-Of acts for another user, but no idempotency key is documented, so a retry can duplicate. source |
| Zendesk Support API B Zendesk, Inc. | Tickets carry an external_id you can list by, but it is not enforced unique and create takes no idempotency key, so the agent must look up before creating; acc-05 and acc-06 describe the integration as costly. source |
| Zoho Desk B Zoho Corporation Private Limited | Create Ticket sets contact, subject and fields, but takes no idempotency key or external id, so a retry can duplicate. source |
Doesn't do this job 2
Listings in the category that do something else, with the reason.
| Listing | Why |
|---|---|
| Chatway MCP C Poptin Ltd | No tool creates a conversation or ticket from outside data; conversations start from the visitor's chat widget. source |
| Landbot MCP server E Landbot | Landbot has no ticket object in the MCP server and no tool creates a conversation from outside data. source |
What stops agents finishing
- no idempotency key so a retried create duplicates
- creating a historical conversation emails the customer unless an import flag is set
- widget or API removed when a free account is closed
Around it
Before: forms.submit, monitoring.alert, agent-harnesses.tool-call. After: support.triage-and-route.
Where this comes from
Weight 7 of 100 in Customer support & helpdesk: 4 of 42 accounts (acc-05, 06, 07, 17); the oldest integration job and the one people describe abandoning
The same as data: /api/v1/use-cases/support.create-ticket-from-system.json, or the MCP tool get_use_case with id support.create-ticket-from-system. Other jobs in this category: /api/v1/niches?category=support.
For companies
Do agents find, use and choose your tools?
An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.