# Create or update a ticket from another system

> Create or update a ticket from another system: 1 companies fully do it, 19 with a limit, 21 carry the tag. Every listing in Customer support & helpdesk with the reason and a source.

- Canonical: https://www.anchorterminal.com/niches/support.create-ticket-from-system/
- Markdown: https://www.anchorterminal.com/niches/support.create-ticket-from-system/index.md (~1,700 tokens)
- Slim: https://www.anchorterminal.com/niches/support.create-ticket-from-system/index.min.md (~380 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/niches/support.create-ticket-from-system/index.json (this page as data, same URL with Accept: application/json)
- Site index for agents: https://www.anchorterminal.com/llms.txt (the key docs and every listing in one file, at most 16 MB, about 4 million tokens: https://www.anchorterminal.com/llms-full.txt)
- API: https://www.anchorterminal.com/api/v1/index.json
- MCP: https://www.anchorterminal.com/mcp (the whole catalogue as tools, no key)
- DNS: dig +short TXT <slug>.grade.anchorterminal.com (the grade as a DNS TXT record, for a sandbox with no HTTP where names still resolve; also top., best.<category>. and <a>.vs.<b>. under the zone, and the same under grade.letme.dev)
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)
- Updated: 2026-11-15

One company's docs show a full fit.

| Companies, full fit | With a limit | Carry the tag | Share of the category's work | First-hand accounts |
| --- | --- | --- | --- | --- |
| 1 | 19 | 21 | 7 | 4 |

## 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

The docs show it meets the test above, and nothing we read says otherwise.

- **Front API + MCP (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.

## Does the job, with a limit

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.

- **Chatwoot API (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.
- **Crisp API + MCP (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.
- **Dixa (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.
- **Drag (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.
- **FreeScout (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.
- **Freshdesk API + MCP (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.
- **Gladly (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.
- **Gorgias API + MCP (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.
- **Help Scout API + MCP (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.
- **HelpDesk (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.
- **Intercom API + MCP (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.
- **Kustomer (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.
- **LiveAgent (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.
- **Missive API + MCP (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.
- **Plain API + MCP (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.
- **Pylon API + MCP (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.
- **Zammad (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.
- **Zendesk Support API (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.
- **Zoho Desk (Zoho Corporation Private Limited)**: Create Ticket sets contact, subject and fields, but takes no idempotency key or external id, so a retry can duplicate.

- not this job: Chatway MCP (Poptin Ltd): No tool creates a conversation or ticket from outside data; conversations start from the visitor's chat widget.
- not this job: Landbot MCP server (Landbot): Landbot has no ticket object in the MCP server and no tool creates a conversation from outside data.

## 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

As data: https://www.anchorterminal.com/api/v1/use-cases/support.create-ticket-from-system.json, or the MCP tool get_use_case with id support.create-ticket-from-system. Draft, read 2026-11-12 from public docs and first-hand accounts, not yet reviewed by a person.

---

Query this catalogue directly over MCP: https://www.anchorterminal.com/mcp (Streamable HTTP, no key). How: https://www.anchorterminal.com/agents/#mcp
